public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
	"stepanm@codeaurora.org" <stepanm@codeaurora.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"dwalker@codeaurora.org" <dwalker@codeaurora.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] arm: msm: Add System MMU support.
Date: Thu, 29 Jul 2010 11:25:04 +0200	[thread overview]
Message-ID: <20100729092503.GO26098@amd.com> (raw)
In-Reply-To: <20100729181412H.fujita.tomonori@lab.ntt.co.jp>

On Thu, Jul 29, 2010 at 05:14:49AM -0400, FUJITA Tomonori wrote:
> On Thu, 29 Jul 2010 11:06:08 +0200
> "Roedel, Joerg" <Joerg.Roedel@amd.com> wrote:
> > I have no clue about the ARM iommus on the omap-platform. From a quick
> > look into the header file I see some similarities to the IOMMU-API. I am
> 
> ARM's iommu stuff might be more appropriate as the IOMMU-API than
> include/linux/iommu.h

Then lets add this functionality to the generic IOMMU-API.

> > also very open for discussions about how the IOMMU-API could be extended
> > to fit the needs of other platforms. Only because nobody has tried to
> > discuss about such an effort is no reason to push the IOMMU-API back.
> 
> Well, the reason (nobody has tried) might be that linux/iommu.h
> doesn't look something intended for the generic IOMMU-API.

How does it not look like a generic intention? The function names are
all generic and do not express that this API should only be used for
KVM. If you talk about the design of the API itself, it was designed for
the IOMMUs I was aware of at the time writing the API (in fact, the
initial design was not my own, it was a generalization of the VT-d
interfaces for KVM).
In other words it was a bottom-up approach to fit the needs of the time
it was written. But its an kernel-only API so we can easily change it
and extend it for other users/iommus when the need arises. I think this
is the way we should go instead of letting each architecture design
their own IOMMU-interfaces.

		Joerg

-- 
Joerg Roedel - 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:[~2010-07-29  9:22 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 22:41 [PATCH 1/2] arm: msm: Add System MMU support Stepan Moskovchenko
2010-07-27 22:43 ` Daniel Walker
2010-07-28  8:39 ` Arnd Bergmann
2010-07-28 17:39   ` stepanm
2010-07-28 17:50     ` Arnd Bergmann
2010-07-28 21:21       ` Russell King - ARM Linux
2010-07-29  4:15         ` FUJITA Tomonori
2010-07-29  8:12         ` Arnd Bergmann
2010-07-29 11:47           ` Russell King - ARM Linux
2010-07-30  6:14             ` FUJITA Tomonori
2010-07-29  0:58       ` stepanm
2010-07-29  3:35         ` FUJITA Tomonori
2010-07-29  8:26           ` Arnd Bergmann
2010-07-29  8:35             ` FUJITA Tomonori
2010-07-29  8:40             ` Roedel, Joerg
2010-07-29  8:46               ` FUJITA Tomonori
2010-07-29  9:06                 ` Roedel, Joerg
2010-07-29  9:14                   ` FUJITA Tomonori
2010-07-29  9:25                     ` Roedel, Joerg [this message]
2010-07-29  9:28                     ` Roedel, Joerg
2010-07-29  9:44                       ` FUJITA Tomonori
2010-07-29 10:01                         ` Roedel, Joerg
2010-07-29 11:25                           ` Arnd Bergmann
2010-07-29 12:12                             ` Roedel, Joerg
2010-07-29 13:01                               ` Arnd Bergmann
2010-07-30  5:19                   ` stepanm
2010-07-30  8:01                     ` Arnd Bergmann
2010-07-30 16:25                       ` stepanm
2010-07-30 21:59                         ` Arnd Bergmann
2010-07-30 22:58                           ` stepanm
2010-07-31  9:37                             ` Arnd Bergmann
2010-08-02  7:58                     ` Roedel, Joerg
2010-08-02 20:29                       ` Zach Pfeffer
2010-08-03  9:23                         ` Roedel, Joerg
2010-08-03 18:43                           ` Stepan Moskovchenko
2010-08-04  9:52                             ` Roedel, Joerg
2010-07-31  3:15             ` Benjamin Herrenschmidt
2010-08-02  7:48               ` Roedel, Joerg
2010-08-02  8:03                 ` Benjamin Herrenschmidt
2010-08-02  8:10                   ` Roedel, Joerg
2010-08-02  8:30                   ` FUJITA Tomonori
2010-08-02  9:03                     ` Russell King - ARM Linux
2010-08-02  9:20                       ` FUJITA Tomonori
2010-08-02 10:04                         ` Russell King - ARM Linux
2010-08-02 15:26                           ` FUJITA Tomonori
2010-08-02  9:45                     ` Roedel, Joerg
2010-08-02  8:35                   ` Roedel, Joerg
2010-07-31  2:30           ` Benjamin Herrenschmidt

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=20100729092503.GO26098@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=arnd@arndb.de \
    --cc=dwalker@codeaurora.org \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stepanm@codeaurora.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