[lkml]   [2011]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRE: [PATCH 02/10] Driver core: Add iommu_ops to bus_type

    > -----Original Message-----
    > From: Roedel, Joerg []
    > Sent: Monday, September 12, 2011 6:06 PM
    > To: Sethi Varun-B16395
    > Cc: Joerg Roedel; Greg KH;; Alex
    > Williamson; Ohad Ben-Cohen; David Woodhouse; David Brown;
    > Subject: Re: [PATCH 02/10] Driver core: Add iommu_ops to bus_type
    > 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.
    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?


     \ /
      Last update: 2011-09-15 14:49    [W:0.022 / U:153.548 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site