From: Joerg Roedel <joro@8bytes.org>
To: Sethi Varun-B16395 <B16395@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yoder Stuart-B08248 <B08248@freescale.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/3 v14] iommu/fsl: Add additional iommu attributes required by the PAMU driver.
Date: Wed, 24 Apr 2013 12:51:18 +0200 [thread overview]
Message-ID: <20130424105117.GI17148@8bytes.org> (raw)
In-Reply-To: <C5ECD7A89D1DC44195F34B25E172658D4B4D9A@039-SN2MPN1-011.039d.mgd.msft.net>
On Tue, Apr 23, 2013 at 02:10:25PM +0000, Sethi Varun-B16395 wrote:
> I think it's fine to have the header under linux, actually I also the
> intel-iommu header under linux.
Yes, the difference is that VT-d runs on x86 and on ia64. So there is no
single arch where the header could be placed. The amd-iommu.h file on
the other hand is x86 only and should also be moved to asm/, as I just
found out :)
And as long as PAMU is only needed on a single architecture the header
should also be arch-specific. If that changes someday the header can be
moved to a generic place.
Joerg
next prev parent reply other threads:[~2013-04-24 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 4:35 [PATCH 1/3 v2] iommu: Move swap_pci_ref function to pci.h Varun Sethi
2013-04-23 4:35 ` [PATCH 2/3 v14] iommu/fsl: Add additional iommu attributes required by the PAMU driver Varun Sethi
2013-04-23 13:38 ` Joerg Roedel
2013-04-23 14:10 ` Sethi Varun-B16395
2013-04-24 10:51 ` Joerg Roedel [this message]
2013-04-24 11:21 ` Sethi Varun-B16395
2013-04-23 15:26 ` Yoder Stuart-B08248
2013-04-23 4:35 ` [PATCH 3/3 v14] iommu/fsl: Freescale PAMU driver and iommu implementation Varun Sethi
2013-04-23 13:01 ` [PATCH 1/3 v2] iommu: Move swap_pci_ref function to pci.h Joerg Roedel
2013-04-23 13:02 ` Sethi Varun-B16395
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=20130424105117.GI17148@8bytes.org \
--to=joro@8bytes.org \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=B16395@freescale.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).