public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	"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>,
	David Woodhouse <dwmw2@infradead.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 0/4] drivers/iommu/ relocations
Date: Wed, 8 Jun 2011 15:35:55 +0200	[thread overview]
Message-ID: <20110608133555.GC21591@amd.com> (raw)
In-Reply-To: <BANLkTin5JYt4=gru181N_BuvnHB7kUTUeQ@mail.gmail.com>

On Wed, Jun 08, 2011 at 09:11:16AM -0400, Ohad Ben-Cohen wrote:
> On Wed, Jun 8, 2011 at 4:05 PM, Matthew Wilcox <matthew@wil.cx> wrote:
> > You've missed at least parisc, ia64, alpha, sparc, powerpc and sh which
> > have IOMMUs.
> 
> None of these seem to call register_iommu.
> 
> > Not that they necessarily all need to be moved across in
> > one patchset, but saying "all iommu drivers" is clearly false.
> 
> I've moved only the existing IOMMU API users.

And I think that is good for now. The iommu-api needs to be extended to
cover all kinds of iommus (like the iommus available on other
architectures). It is definitly the plan to do that and have a common
dma_ops implementation for all of them. But lets start small by now and
move forward step by step :-)

	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 13:35 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
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 [this message]

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=20110608133555.GC21591@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=matthew@wil.cx \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox