On Thu, Sep 15, 2011 at 08:45:35AM -0400, Sethi Varun-B16395 wrote: > > From: Roedel, Joerg [mailto:Joerg.Roedel@xxxxxxx] > > The details are up to Alex Williamson. One option is to register a > > notifier for the bus in the iommu_bus_init() function and react to its > > notifications. > > I think in the end we will have a number of additional call-backs in the > > iommu_ops which are called by the notifier (or from the driver-core > > directly) to handle actions like added or removed devices. All the > > infrastructure for that which is implemented in the iommu-drivers today > > will then be in the iommu-core code. > I am not sure If I understand this, but as per your earlier statement > iommu is a device on the bus and its initialization would happen when > bus is set up and devices are populated. So, when would device > notifier call an iommu call back? This is done in the iommu_bus_init() function. It will iterate over all devices that are already on the bus and do the iommu specific initialization on them. The devices added or removed later the notifier will do the job. Joerg -- AMD Operating System Research Center Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach General Managers: Alberto Bozzo, Andrew Bowd Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
