Re: [PATCH 02/10] Driver core: Add iommu_ops to bus_type

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 12, 2011 at 08:08:41AM -0400, Sethi Varun-B16395 wrote:
> > The IOMMUs are usually devices on the bus itself, so they are initialized
> > after the bus is set up and the devices on it are populated.  So the
> > function can not be called on bus initialization because the IOMMU is not
> > ready at this point.
> Well, at what point would the add_device_group (referring to patch set posted by Alex) call back be invoked?

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.

	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


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux