From: ohad@wizery.com (Ohad Ben-Cohen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] x86: intel-iommu: move to drivers/iommu/
Date: Wed, 8 Jun 2011 13:33:10 +0300 [thread overview]
Message-ID: <BANLkTi=eRmd4h3+StGCR_-uVKo5F9fyd7g@mail.gmail.com> (raw)
In-Reply-To: <1307524659.4771.12.camel@i7.infradead.org>
On Wed, Jun 8, 2011 at 12:17 PM, David Woodhouse <dwmw2@infradead.org> wrote:
> At least iova.o wants to go with it. That's one of the parts that is a
> candidate for harmonisation across IOMMU implementations, either by
> removing it or by having others use it too. It's how we allocate virtual
> I/O address space.
>
> I suspect the interrupt remapping support may well want to move with it
> too. It's no more out-of-place in drivers/iommu than it is in
> drivers/pci. And then you can certainly move dmar.o too.
Sounds good, thanks.
I'll wait a bit to see if there're more comments, and then re-send this one
next prev parent reply other threads:[~2011-06-08 10:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 8:34 [PATCH 0/4] drivers/iommu/ relocations Ohad Ben-Cohen
2011-06-08 8:34 ` [PATCH 1/4] drivers: iommu: move to a dedicated folder Ohad Ben-Cohen
2011-06-08 8:34 ` [PATCH 2/4] msm: iommu: move to drivers/iommu/ Ohad Ben-Cohen
2011-06-08 22:27 ` David Brown
2011-06-10 16:24 ` Ohad Ben-Cohen
2011-06-08 8:34 ` [PATCH 3/4] x86: amd_iommu: " Ohad Ben-Cohen
2011-06-08 8:34 ` [PATCH 4/4] x86: intel-iommu: " Ohad Ben-Cohen
2011-06-08 9:17 ` David Woodhouse
2011-06-08 9:38 ` Roedel, Joerg
2011-06-08 10:33 ` Ohad Ben-Cohen [this message]
2011-06-08 17:47 ` Chris Wright
2011-06-08 19:35 ` Ohad Ben-Cohen
2011-06-08 9:35 ` [PATCH 0/4] drivers/iommu/ relocations Roedel, Joerg
2011-06-08 14:32 ` Ingo Molnar
2011-06-08 22:23 ` David Brown
2011-06-08 13:05 ` Matthew Wilcox
2011-06-08 13:11 ` Ohad Ben-Cohen
2011-06-08 13:35 ` Roedel, Joerg
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='BANLkTi=eRmd4h3+StGCR_-uVKo5F9fyd7g@mail.gmail.com' \
--to=ohad@wizery.com \
--cc=linux-arm-kernel@lists.infradead.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).