All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	David Brown <davidb@codeaurora.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 4/4] x86: intel-iommu: move to drivers/iommu/
Date: Wed, 8 Jun 2011 11:38:01 +0200	[thread overview]
Message-ID: <20110608093801.GH4407@amd.com> (raw)
In-Reply-To: <1307524659.4771.12.camel@i7.infradead.org>

On Wed, Jun 08, 2011 at 05:17:38AM -0400, David Woodhouse wrote:
> On Wed, 2011-06-08 at 11:34 +0300, Ohad Ben-Cohen wrote:
> > --- a/drivers/pci/Makefile
> > +++ b/drivers/pci/Makefile
> > @@ -30,7 +30,7 @@ obj-$(CONFIG_PCI_MSI) += msi.o
> >  obj-$(CONFIG_HT_IRQ) += htirq.o
> >  
> >  # Build Intel IOMMU support
> > -obj-$(CONFIG_DMAR) += dmar.o iova.o intel-iommu.o
> > +obj-$(CONFIG_DMAR) += dmar.o iova.o
> >  
> >  obj-$(CONFIG_INTR_REMAP) += dmar.o intr_remapping.o
> >  
> 
> 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.

Interrupt remapping certainly makes sense too. I am not sure yet how to
generalize it because the AMD version of it is significantly different
from VT-d, but we'll see.

	Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632


WARNING: multiple messages have this Message-ID (diff)
From: Joerg.Roedel@amd.com (Roedel, Joerg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] x86: intel-iommu: move to drivers/iommu/
Date: Wed, 8 Jun 2011 11:38:01 +0200	[thread overview]
Message-ID: <20110608093801.GH4407@amd.com> (raw)
In-Reply-To: <1307524659.4771.12.camel@i7.infradead.org>

On Wed, Jun 08, 2011 at 05:17:38AM -0400, David Woodhouse wrote:
> On Wed, 2011-06-08 at 11:34 +0300, Ohad Ben-Cohen wrote:
> > --- a/drivers/pci/Makefile
> > +++ b/drivers/pci/Makefile
> > @@ -30,7 +30,7 @@ obj-$(CONFIG_PCI_MSI) += msi.o
> >  obj-$(CONFIG_HT_IRQ) += htirq.o
> >  
> >  # Build Intel IOMMU support
> > -obj-$(CONFIG_DMAR) += dmar.o iova.o intel-iommu.o
> > +obj-$(CONFIG_DMAR) += dmar.o iova.o
> >  
> >  obj-$(CONFIG_INTR_REMAP) += dmar.o intr_remapping.o
> >  
> 
> 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.

Interrupt remapping certainly makes sense too. I am not sure yet how to
generalize it because the AMD version of it is significantly different
from VT-d, but we'll see.

	Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632

  reply	other threads:[~2011-06-08  9:37 UTC|newest]

Thread overview: 44+ 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 ` Ohad Ben-Cohen
2011-06-08  8:34 ` 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   ` Ohad Ben-Cohen
2011-06-08  8:34   ` Ohad Ben-Cohen
2011-06-08  8:34 ` [PATCH 2/4] msm: iommu: move to drivers/iommu/ Ohad Ben-Cohen
2011-06-08  8:34   ` Ohad Ben-Cohen
2011-06-08  8:34   ` Ohad Ben-Cohen
2011-06-08 22:27   ` David Brown
2011-06-08 22:27     ` David Brown
2011-06-08 22:27     ` David Brown
2011-06-10 16:24     ` Ohad Ben-Cohen
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   ` Ohad Ben-Cohen
2011-06-08  8:34   ` Ohad Ben-Cohen
2011-06-08  8:34 ` [PATCH 4/4] x86: intel-iommu: " Ohad Ben-Cohen
2011-06-08  8:34   ` Ohad Ben-Cohen
2011-06-08  8:34   ` Ohad Ben-Cohen
2011-06-08  9:17   ` David Woodhouse
2011-06-08  9:17     ` David Woodhouse
2011-06-08  9:38     ` Roedel, Joerg [this message]
2011-06-08  9:38       ` Roedel, Joerg
2011-06-08 10:33     ` Ohad Ben-Cohen
2011-06-08 10:33       ` Ohad Ben-Cohen
2011-06-08 17:47   ` Chris Wright
2011-06-08 17:47     ` Chris Wright
2011-06-08 17:47     ` Chris Wright
2011-06-08 19:35     ` Ohad Ben-Cohen
2011-06-08 19:35       ` Ohad Ben-Cohen
2011-06-08  9:35 ` [PATCH 0/4] drivers/iommu/ relocations Roedel, Joerg
2011-06-08  9:35   ` Roedel, Joerg
2011-06-08 14:32   ` Ingo Molnar
2011-06-08 14:32     ` Ingo Molnar
2011-06-08 22:23   ` David Brown
2011-06-08 22:23     ` David Brown
2011-06-08 22:23     ` David Brown
2011-06-08 13:05 ` Matthew Wilcox
2011-06-08 13:05   ` Matthew Wilcox
2011-06-08 13:11   ` Ohad Ben-Cohen
2011-06-08 13:11     ` Ohad Ben-Cohen
2011-06-08 13:35     ` Roedel, Joerg
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=20110608093801.GH4407@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=arnd@arndb.de \
    --cc=davidb@codeaurora.org \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=ohad@wizery.com \
    /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 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.