From: Scott Wood <scottwood@freescale.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Sethi Varun-B16395 <B16395@freescale.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Wood Scott-B07421 <B07421@freescale.com>,
Yoder Stuart-B08248 <B08248@freescale.com>
Subject: Re: [PATCH 4/4] iommu: Add domain window handling functions
Date: Mon, 4 Feb 2013 17:36:20 -0600 [thread overview]
Message-ID: <1360020980.14901.17@snotra> (raw)
In-Reply-To: <20130204130214.GN25591@8bytes.org> (from joro@8bytes.org on Mon Feb 4 07:02:14 2013)
On 02/04/2013 07:02:14 AM, Joerg Roedel wrote:
> On Thu, Jan 31, 2013 at 09:32:26AM +0000, Sethi Varun-B16395 wrote:
> > We need a mechanism to determine the maximum number of subwindows
> supported by PAMU. How about representing it in the iommu_domain
> structure:
> > struct iommu_domain {
> > struct iommu_ops *ops;
> > void *priv;
> > iommu_fault_handler_t handler;
> > void *handler_token;
> > struct iommu_domain_geometry geometry;
> > u32 max_sub_windows; -----> maximum number of sub windows
> supported by the hardware.
> > }
>
> I`ll leave that flag to the private-data of the IOMMU domain. Instead
> I
> added a DOMAIN_ATTR_WINDOWS attribute to get/set the number of
> subwindows. I'll post the updated patch-set soon.
If it's private data, how does the caller know what sort of geometry it
can request?
-Scott
next prev parent reply other threads:[~2013-02-04 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 21:43 [PATCH 0/4] iommu: Support non-paging IOMMUs Joerg Roedel
2013-01-30 21:43 ` [PATCH 1/4] iommu: Make sure DOMAIN_ATTR_MAX is really the maximum Joerg Roedel
2013-01-30 21:43 ` [PATCH 2/4] iommu: Check for valid pgsize_bitmap in iommu_map/unmap Joerg Roedel
2013-01-30 21:43 ` [PATCH 3/4] iommu: Implement DOMAIN_ATTR_PAGING attribute Joerg Roedel
2013-01-30 21:43 ` [PATCH 4/4] iommu: Add domain window handling functions Joerg Roedel
2013-01-31 9:32 ` Sethi Varun-B16395
2013-02-04 13:02 ` Joerg Roedel
2013-02-04 23:36 ` Scott Wood [this message]
2013-02-05 3:41 ` Yoder Stuart-B08248
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=1360020980.14901.17@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=B16395@freescale.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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