public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale•com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: joerg.roedel@amd•com, linux-kernel@vger•kernel.org,
	iommu@lists•linux-foundation.org,
	"<b16395@freescale•com>" <b16395@freescale•com>,
	Varun Sethi <Varun.Sethi@freescale•com>,
	linuxppc-dev@lists•ozlabs.org
Subject: Re: [RFC][PATCH 2/3] iommu/fsl: Add iommu domain attributes required by fsl PAMU driver.
Date: Wed, 19 Sep 2012 19:12:16 -0500	[thread overview]
Message-ID: <1348099936.22800.21@snotra> (raw)
In-Reply-To: <6B8A3365-C97E-4742-A0DD-D8FD6BA358EB@kernel.crashing.org> (from galak@kernel.crashing.org on Wed Sep 19 08:52:27 2012)

On 09/19/2012 08:52:27 AM, Kumar Gala wrote:
>=20
> On Sep 19, 2012, at 8:17 AM, <b16395@freescale•com> =20
> <b16395@freescale•com> wrote:
>=20
> > From: Varun Sethi <Varun.Sethi@freescale•com>
> >
> > Added the following domain attributes required by FSL PAMU driver:
> > 1. Subwindows field added to the iommu domain geometry attribute.
> > 2. Added new iommu stash attribute, which allows setting of the
> >   LIODN specific stash id parameter through IOMMU API.
> > 3. Added an attribute for enabling/disabling DMA to a particular
> >   memory window.
> >
> > Signed-off-by: Varun Sethi <Varun.Sethi@freescale•com>
> > ---
> > include/linux/iommu.h |   30 ++++++++++++++++++++++++++++++
> > 1 files changed, 30 insertions(+), 0 deletions(-)
> >
> > diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> > index 7e83370..eaa40c6 100644
> > --- a/include/linux/iommu.h
> > +++ b/include/linux/iommu.h
> > @@ -44,6 +44,28 @@ struct iommu_domain_geometry {
> > 	dma_addr_t aperture_start; /* First address that can be =20
> mapped    */
> > 	dma_addr_t aperture_end;   /* Last address that can be =20
> mapped     */
> > 	bool force_aperture;       /* DMA only allowed in mappable =20
> range? */
> > +
> > +	/* The subwindows field indicates number of DMA subwindows =20
> supported
> > +	 * by the geometry. Following is the interpretation of
> > +	 * values for this field:
> > +	 * 0 : This implies that the supported geometry size is 1 MB
> > +         * with each subwindow size being 4KB. Thus number of =20
> subwindows
> > +	 * being =3D 1MB/4KB =3D 256.
> > +	 * 1 : Only one DMA window i.e. no subwindows.
> > +	 * value other than 0 or 1 would indicate actual number of =20
> subwindows.
> > +	 */
> > +	u32 subwindows;
> > +};
> > +
> > +/* This attribute corresponds to IOMMUs capable of generating
> > + * a stash transaction. A stash transaction is typically a
> > + * hardware initiated prefetch of data from memory to cache.
> > + * This attribute allows configuring stashig specific parameters
> > + * in the IOMMU hardware.
> > + */
> > +struct iommu_stash_attribute {
> > +	u32 	cpu;	/* cpu number */
> > +	u32 	cache;	/* cache to stash to: L1,L2,L3 */
>=20
> seems like this should be enum instead of u32 for cache
>=20
> With enum being something like:
>=20
> enum iommu_attr_stash_cache {
> 	IOMMU_ATTR_CACHE_L1,
> 	IOMMU_ATTR_CACHE_L2,
> 	IOMMU_ATTR_CACHE_L3,
> };

Don't we want these structs to be usable via some VFIO ioctl?  In that =20
case they need to use fixed size types.

-Scott=

  reply	other threads:[~2012-09-20  0:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 13:17 [RFC][PATCH 0/3] iommu/fsl: Freescale PAMU driver and IOMMU API implementation b16395
2012-09-19 13:17 ` [RFC][PATCH 1/3] iommu/fsl: Store iommu domain information pointer in archdata b16395
2012-09-19 13:50   ` Kumar Gala
2012-10-04 16:30     ` Sethi Varun-B16395
2012-09-19 13:17 ` [RFC][PATCH 2/3] iommu/fsl: Add iommu domain attributes required by fsl PAMU driver b16395
2012-09-19 13:52   ` Kumar Gala
2012-09-20  0:12     ` Scott Wood [this message]
2012-09-20  9:46       ` Sethi Varun-B16395
2012-09-20 13:19         ` Kumar Gala
2012-09-19 13:17 ` [RFC][PATCH 3/3] iommu/fsl: Freescale PAMU driver and IOMMU API implementation b16395
2012-09-19 14:18   ` Kumar Gala
2012-09-19 13:49 ` [RFC][PATCH 0/3] " Kumar Gala
2012-09-20  0:14   ` Scott Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1348099936.22800.21@snotra \
    --to=scottwood@freescale$(echo .)com \
    --cc=Varun.Sethi@freescale$(echo .)com \
    --cc=b16395@freescale$(echo .)com \
    --cc=galak@kernel$(echo .)crashing.org \
    --cc=iommu@lists$(echo .)linux-foundation.org \
    --cc=joerg.roedel@amd$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox