Thanks for the clarification Alexey. Kumar, We are using this new field (for PAMU) to store the iommu domain (for iommu API) information for a device.
Regards Varun > -----Original Message----- > From: Alexey Kardashevskiy [mailto:a...@ozlabs.ru] > Sent: Friday, March 01, 2013 6:55 AM > To: Kumar Gala > Cc: Sethi Varun-B16395; Benjamin Herrenschmidt; iommu@lists.linux- > foundation.org; linuxppc-dev@lists.ozlabs.org list; linux- > ker...@vger.kernel.org list; Wood Scott-B07421; Yoder Stuart-B08248; > Joerg Roedel; Paul Mackerras; David Gibson; Alex Williamson > Subject: Re: [PATCH 1/6 v8] iommu/fsl: Store iommu domain information > pointer in archdata. > > Hi! > > On POWERNV we use only the part of IOMMU API which handles devices and > groups. We do not use IOMMU domains as VFIO containers do everything we > need for VFIO and we do not implement iommu_ops as it is not very > relevant to our architecture (does not give dma window properties, etc). > > So your work does not overlap with my work :) > > > On 01/03/13 02:51, Kumar Gala wrote: > > > > On Feb 27, 2013, at 6:04 AM, Sethi Varun-B16395 wrote: > > > >> Hi Kumar,Ben, > >> I am implementing the Freescale PAMU (IOMMU) driver using the Linux > IOMMU API. In this particular patch, I have added a new field to > dev_archdata structure to store the dma domain information. > >> This field is updated whenever we attach a device to an iommu domain. > >> > >> Regards > >> Varun > > > > Would be good to see if this overlaps with Alexey's work for IOMMU > driver for powernv. > > > > - k > > > >> > >>> -----Original Message----- > >>> From: Joerg Roedel [mailto:j...@8bytes.org] > >>> Sent: Wednesday, February 27, 2013 5:01 PM > >>> To: Sethi Varun-B16395 > >>> Cc: io...@lists.linux-foundation.org; linuxppc-dev@lists.ozlabs.org; > >>> linux-ker...@vger.kernel.org; Wood Scott-B07421; Yoder Stuart-B08248 > >>> Subject: Re: [PATCH 1/6 v8] iommu/fsl: Store iommu domain > >>> information pointer in archdata. > >>> > >>> On Mon, Feb 18, 2013 at 06:22:14PM +0530, Varun Sethi wrote: > >>>> Add a new field in the device (powerpc) archdata structure for > >>>> storing iommu domain information pointer. This pointer is stored > >>>> when the device is attached to a particular domain. > >>>> > >>>> > >>>> Signed-off-by: Varun Sethi <varun.se...@freescale.com> > >>>> --- > >>>> - no change. > >>>> arch/powerpc/include/asm/device.h | 4 ++++ > >>>> 1 files changed, 4 insertions(+), 0 deletions(-) > >>>> > >>>> diff --git a/arch/powerpc/include/asm/device.h > >>>> b/arch/powerpc/include/asm/device.h > >>>> index 77e97dd..6dc79fe 100644 > >>>> --- a/arch/powerpc/include/asm/device.h > >>>> +++ b/arch/powerpc/include/asm/device.h > >>>> @@ -28,6 +28,10 @@ struct dev_archdata { > >>>> void *iommu_table_base; > >>>> } dma_data; > >>>> > >>>> + /* IOMMU domain information pointer. This would be set > >>>> + * when this device is attached to an iommu_domain. > >>>> + */ > >>>> + void *iommu_domain; > >>> > >>> Please Cc the PowerPC Maintainers on this, so that they can have a > >>> look at it. This also must be put this into an #ifdef > CONFIG_IOMMU_API. > > > -- > Alexey _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev