diff for duplicates of <1354645371.16710.15@snotra> diff --git a/a/1.txt b/N1/1.txt index 0f6b88e..d79ad50 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,12 +1,12 @@ On 12/04/2012 05:53:33 AM, Sethi Varun-B16395 wrote: -> -> +>=20 +>=20 > > -----Original Message----- > > From: Wood Scott-B07421 > > Sent: Monday, December 03, 2012 10:34 PM > > To: Sethi Varun-B16395 > > Cc: Joerg Roedel; linux-kernel@vger.kernel.org; iommu@lists.linux- -> > foundation.org; Wood Scott-B07421; linuxppc-dev@lists.ozlabs.org; +> > foundation.org; Wood Scott-B07421; linuxppc-dev@lists.ozlabs.org; =20 > Tabi > > Timur-B04825 > > Subject: Re: [PATCH 3/4 v5] iommu/fsl: Add iommu domain attributes @@ -20,44 +20,44 @@ On 12/04/2012 05:53:33 AM, Sethi Varun-B16395 wrote: > > > > bounces@lists.linux-foundation.org] On Behalf Of Joerg Roedel > > > > Sent: Sunday, December 02, 2012 7:33 PM > > > > To: Sethi Varun-B16395 -> > > > Cc: linux-kernel@vger.kernel.org; +> > > > Cc: linux-kernel@vger.kernel.org; =20 > iommu@lists.linux-foundation.org; > > > Wood > > > > Scott-B07421; linuxppc-dev@lists.ozlabs.org; Tabi Timur-B04825 -> > > > Subject: Re: [PATCH 3/4 v5] iommu/fsl: Add iommu domain +> > > > Subject: Re: [PATCH 3/4 v5] iommu/fsl: Add iommu domain =20 > attributes > > > > required by fsl PAMU driver. > > > > > > > > Hmm, we need to work out a good abstraction for this. > > > > > > > > On Tue, Nov 20, 2012 at 07:24:56PM +0530, Varun Sethi wrote: -> > > > > Added the following domain attributes required by FSL PAMU +> > > > > Added the following domain attributes required by FSL PAMU =20 > driver: -> > > > > 1. Subwindows field added to the iommu domain geometry +> > > > > 1. Subwindows field added to the iommu domain geometry =20 > attribute. > > > > -> > > > Are the Subwindows mapped with full size or do you map only +> > > > Are the Subwindows mapped with full size or do you map only =20 > parts > > > of the > > > > subwindows? > > > > -> > > [Sethi Varun-B16395] It's possible to map a part of the subwindow +> > > [Sethi Varun-B16395] It's possible to map a part of the subwindow =20 > i.e. > > > size of the mapping can be less than the sub window size. > > > > > > > > + * This attribute indicates number of DMA subwindows > > supported > > > by -> > > > > + * the geometry. If there is a single window that maps +> > > > > + * the geometry. If there is a single window that maps =20 > the > > > entire -> > > > > + * geometry, attribute must be set to "1". A value of +> > > > > + * geometry, attribute must be set to "1". A value of =20 > "0" > > > implies -> > > > > + * that this mechanism is not used at all(normal paging +> > > > > + * that this mechanism is not used at all(normal paging =20 > is > > > used). -> > > > > + * Value other than* "0" or "1" indicates the actual +> > > > > + * Value other than* "0" or "1" indicates the actual =20 > number > > of > > > > > + * subwindows. @@ -65,21 +65,21 @@ On 12/04/2012 05:53:33 AM, Sethi Varun-B16395 wrote: > > > > > > > > This semantic is ugly, how about a feature detection mechanism? > > > > -> > > [Sethi Varun-B16395] A feature mechanism to query the type of +> > > [Sethi Varun-B16395] A feature mechanism to query the type of =20 > IOMMU? > > > > A feature mechanism to determine whether this subwindow mechanism is > > available, and what the limits are. > > -> So, we use the IOMMU capability interface to find out if IOMMU -> supports sub windows or not, right? But still number of sub windows -> would be specified as a part of the geometry and the valid value for +> So, we use the IOMMU capability interface to find out if IOMMU =20 +> supports sub windows or not, right? But still number of sub windows =20 +> would be specified as a part of the geometry and the valid value for =20 > sub windows would 0,1 or actual number of sub windows. -How does a user of the interface find out what values are possible for -the "actual number of subwindows"? How does a user of the interface -find out whether there are any limitations on specifying a value of -zero (in the case of PAMU, that would be a maximum 1 MiB +How does a user of the interface find out what values are possible for =20 +the "actual number of subwindows"? How does a user of the interface =20 +find out whether there are any limitations on specifying a value of =20 +zero (in the case of PAMU, that would be a maximum 1 MiB =20 naturally-aligned aperture to support arbitrary 4KiB mappings)? --Scott +-Scott= diff --git a/a/content_digest b/N1/content_digest index c35a1fe..f26b647 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,21 +5,21 @@ "To\0Sethi Varun-B16395 <B16395@freescale.com>\0" "Cc\0Wood Scott-B07421 <B07421@freescale.com>" Joerg Roedel <joro@8bytes.org> + Tabi Timur-B04825 <B04825@freescale.com> linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> iommu@lists.linux-foundation.org <iommu@lists.linux-foundation.org> - linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> - " Tabi Timur-B04825 <B04825@freescale.com>\0" + " linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org>\0" "\00:1\0" "b\0" "On 12/04/2012 05:53:33 AM, Sethi Varun-B16395 wrote:\n" - "> \n" - "> \n" + ">=20\n" + ">=20\n" "> > -----Original Message-----\n" "> > From: Wood Scott-B07421\n" "> > Sent: Monday, December 03, 2012 10:34 PM\n" "> > To: Sethi Varun-B16395\n" "> > Cc: Joerg Roedel; linux-kernel@vger.kernel.org; iommu@lists.linux-\n" - "> > foundation.org; Wood Scott-B07421; linuxppc-dev@lists.ozlabs.org; \n" + "> > foundation.org; Wood Scott-B07421; linuxppc-dev@lists.ozlabs.org; =20\n" "> Tabi\n" "> > Timur-B04825\n" "> > Subject: Re: [PATCH 3/4 v5] iommu/fsl: Add iommu domain attributes\n" @@ -33,44 +33,44 @@ "> > > > bounces@lists.linux-foundation.org] On Behalf Of Joerg Roedel\n" "> > > > Sent: Sunday, December 02, 2012 7:33 PM\n" "> > > > To: Sethi Varun-B16395\n" - "> > > > Cc: linux-kernel@vger.kernel.org; \n" + "> > > > Cc: linux-kernel@vger.kernel.org; =20\n" "> iommu@lists.linux-foundation.org;\n" "> > > Wood\n" "> > > > Scott-B07421; linuxppc-dev@lists.ozlabs.org; Tabi Timur-B04825\n" - "> > > > Subject: Re: [PATCH 3/4 v5] iommu/fsl: Add iommu domain \n" + "> > > > Subject: Re: [PATCH 3/4 v5] iommu/fsl: Add iommu domain =20\n" "> attributes\n" "> > > > required by fsl PAMU driver.\n" "> > > >\n" "> > > > Hmm, we need to work out a good abstraction for this.\n" "> > > >\n" "> > > > On Tue, Nov 20, 2012 at 07:24:56PM +0530, Varun Sethi wrote:\n" - "> > > > > Added the following domain attributes required by FSL PAMU \n" + "> > > > > Added the following domain attributes required by FSL PAMU =20\n" "> driver:\n" - "> > > > > 1. Subwindows field added to the iommu domain geometry \n" + "> > > > > 1. Subwindows field added to the iommu domain geometry =20\n" "> attribute.\n" "> > > >\n" - "> > > > Are the Subwindows mapped with full size or do you map only \n" + "> > > > Are the Subwindows mapped with full size or do you map only =20\n" "> parts\n" "> > > of the\n" "> > > > subwindows?\n" "> > > >\n" - "> > > [Sethi Varun-B16395] It's possible to map a part of the subwindow \n" + "> > > [Sethi Varun-B16395] It's possible to map a part of the subwindow =20\n" "> i.e.\n" "> > > size of the mapping can be less than the sub window size.\n" "> > >\n" "> > > > > +\t * This attribute indicates number of DMA subwindows\n" "> > supported\n" "> > > by\n" - "> > > > > +\t * the geometry. If there is a single window that maps \n" + "> > > > > +\t * the geometry. If there is a single window that maps =20\n" "> the\n" "> > > entire\n" - "> > > > > +\t * geometry, attribute must be set to \"1\". A value of \n" + "> > > > > +\t * geometry, attribute must be set to \"1\". A value of =20\n" "> \"0\"\n" "> > > implies\n" - "> > > > > +\t * that this mechanism is not used at all(normal paging \n" + "> > > > > +\t * that this mechanism is not used at all(normal paging =20\n" "> is\n" "> > > used).\n" - "> > > > > +\t * Value other than* \"0\" or \"1\" indicates the actual \n" + "> > > > > +\t * Value other than* \"0\" or \"1\" indicates the actual =20\n" "> number\n" "> > of\n" "> > > > > +\t * subwindows.\n" @@ -78,23 +78,23 @@ "> > > >\n" "> > > > This semantic is ugly, how about a feature detection mechanism?\n" "> > > >\n" - "> > > [Sethi Varun-B16395] A feature mechanism to query the type of \n" + "> > > [Sethi Varun-B16395] A feature mechanism to query the type of =20\n" "> IOMMU?\n" "> >\n" "> > A feature mechanism to determine whether this subwindow mechanism is\n" "> > available, and what the limits are.\n" "> >\n" - "> So, we use the IOMMU capability interface to find out if IOMMU \n" - "> supports sub windows or not, right? But still number of sub windows \n" - "> would be specified as a part of the geometry and the valid value for \n" + "> So, we use the IOMMU capability interface to find out if IOMMU =20\n" + "> supports sub windows or not, right? But still number of sub windows =20\n" + "> would be specified as a part of the geometry and the valid value for =20\n" "> sub windows would 0,1 or actual number of sub windows.\n" "\n" - "How does a user of the interface find out what values are possible for \n" - "the \"actual number of subwindows\"? How does a user of the interface \n" - "find out whether there are any limitations on specifying a value of \n" - "zero (in the case of PAMU, that would be a maximum 1 MiB \n" + "How does a user of the interface find out what values are possible for =20\n" + "the \"actual number of subwindows\"? How does a user of the interface =20\n" + "find out whether there are any limitations on specifying a value of =20\n" + "zero (in the case of PAMU, that would be a maximum 1 MiB =20\n" "naturally-aligned aperture to support arbitrary 4KiB mappings)?\n" "\n" - -Scott + -Scott= -92703076b5a092f74469a1816b7ecf7cf6ae860121664fed6f5943673b824810 +3671938cc4ada8f6d731ca399da420cd02e01bf25178459c3f821a1e664dd37c
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.