linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] devicetree: Add generic IOMMU device tree bindings
Date: Thu, 05 Jun 2014 11:42:12 +0200	[thread overview]
Message-ID: <6794037.0YTCc6JFQV@wuerfel> (raw)
In-Reply-To: <20140604213159.GB18780@mithrandir>

On Wednesday 04 June 2014 23:32:00 Thierry Reding wrote:
> On Fri, May 30, 2014 at 09:01:19PM +0200, Arnd Bergmann wrote:
> > On Friday 30 May 2014 12:22:32 Dave Martin wrote:
> > > > +
> > > > +Examples:
> > > > +=========
> > > > +
> > > > +Single-master IOMMU:
> > > > +--------------------
> > > > +
> > > > + iommu {
> > > > +         #address-cells = <0>;
> > > > +         #size-cells = <0>;
> > > > + };
> > > > +
> > > > + master {
> > > > +         iommus = <&/iommu>;
> > > > + };
> > > > +
> > > > +Multiple-master IOMMU with fixed associations:
> > > > +----------------------------------------------
> > > > +
> > > > + /* multiple-master IOMMU */
> > > > + iommu {
> > > > +         /*
> > > > +          * Masters are statically associated with this IOMMU and
> > > > +          * address translation is always enabled.
> > > > +          */
> > > > +         #address-cells = <0>;
> > > > +         #size-cells = <0>;
> > > 
> > > In this example, can different translations be set up for the different
> > > masters?
> > > 
> > > With no cells available to contain any sort of ID, it looks like this
> > > is not possible.
> > 
> > Correct, this example is for an IOMMU that does not use IDs but has a
> > shared address space for all devices.
> 
> Couldn't these device all still have separate address spaces?

No. If they had separate address spaces, they would require a more
sophisticated IOMMU. A simple IOMMU without IDs can only be used
for overcoming address space limits (e.g. for 32-bit DMA masters on
systems with more than 4GB RAM) but not for strict isolation.

You basically have one page table shared across all devices connected
to the IOMMU, and every call to dma_alloc_coherent or dma_map_*
allocates a new IOVA that isn't used by any of the other devices
already, but you can't prevent a malicious user from getting a device
to do DMA to an IOVA that has been set up for another device.

You could have one such IOMMU per device of course, but I guess that's
not what you mean.

	Arnd

  reply	other threads:[~2014-06-05  9:42 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 20:36 [PATCH v2] devicetree: Add generic IOMMU device tree bindings Thierry Reding
2014-05-29 15:52 ` Stephen Warren
2014-05-30  7:30   ` Thierry Reding
2014-05-30 11:27     ` Dave Martin
2014-05-30 19:11       ` Arnd Bergmann
2014-06-02 10:56         ` Dave Martin
2014-06-04 21:12       ` Thierry Reding
2014-06-16 12:57         ` Will Deacon
2014-06-17 11:58           ` Thierry Reding
2014-06-17 12:18             ` Will Deacon
2014-06-17 23:37               ` Thierry Reding
2014-06-18 10:14                 ` Will Deacon
2014-06-20 15:53                   ` Arnd Bergmann
2014-06-20 17:50                     ` Will Deacon
2014-06-20 18:55                       ` Arnd Bergmann
2014-05-30 11:22 ` Dave Martin
2014-05-30 19:01   ` Arnd Bergmann
2014-06-02 11:44     ` Dave Martin
2014-06-04 21:32     ` Thierry Reding
2014-06-05  9:42       ` Arnd Bergmann [this message]
     [not found] <1400877218-4113-1-git-send-email-thierry.reding@gmail.com>
2014-05-30 13:16 ` Rob Herring
2014-05-30 19:06   ` Arnd Bergmann
2014-05-30 19:29     ` Hiroshi Doyu
2014-05-30 19:54       ` Arnd Bergmann
2014-06-01  9:55         ` Will Deacon
2014-06-04 13:39           ` Thierry Reding
2014-06-04 13:44         ` Thierry Reding
2014-06-04 13:53           ` Arnd Bergmann
2014-06-04 13:56           ` Will Deacon
2014-06-04 14:01             ` Arnd Bergmann
2014-06-04 16:39               ` Will Deacon
2014-05-30 19:31     ` Rob Herring
2014-05-30 19:49       ` Arnd Bergmann
2014-06-02 10:41         ` Dave Martin
2014-06-04 14:35           ` Thierry Reding
2014-06-04 16:41             ` Will Deacon
2014-06-04 21:00               ` Thierry Reding
2014-06-05 19:10               ` Varun Sethi
2014-06-16 15:27                 ` Will Deacon
2014-06-16 16:56                   ` Stuart Yoder
2014-06-16 17:04                     ` Will Deacon
2014-06-16 17:30                       ` Arnd Bergmann
2014-06-16 18:53                       ` Stuart Yoder
2014-06-17 10:26                         ` Varun Sethi
2014-06-17 10:43                           ` Will Deacon
2014-06-17 11:21                             ` Varun Sethi
2014-06-17 14:50                               ` Stuart Yoder
2014-06-18  9:29                                 ` Will Deacon
2014-06-17 14:39                           ` Stuart Yoder
2014-06-20 23:16     ` Olav Haugan
2014-06-24  9:18       ` Will Deacon
2014-06-24 17:57         ` Olav Haugan
2014-06-24 18:11           ` Will Deacon
2014-06-24 18:20             ` Arnd Bergmann
2014-06-25  9:17               ` Will Deacon
2014-06-25  9:27                 ` Arnd Bergmann
2014-06-25  9:38                   ` Will Deacon
2014-06-25  9:48                     ` Arnd Bergmann
2014-06-25  9:57                       ` Will Deacon
2014-06-25 10:12                         ` Arnd Bergmann
2014-06-25 10:14                           ` Will Deacon
2014-06-24 21:35             ` Olav Haugan
2014-06-25  9:18               ` Will Deacon
2014-06-27 22:23                 ` Olav Haugan
2014-06-30  9:52                   ` Will Deacon
2014-07-09  1:07                     ` Olav Haugan
2014-07-09 10:54                       ` Will Deacon
2014-07-10 22:32                         ` Olav Haugan
2014-07-11 12:24                           ` Will Deacon
     [not found] <20140606224542.GA22188@mithrandir>
2014-06-07 13:22 ` Arnd Bergmann
2014-06-09 10:49   ` Thierry Reding

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=6794037.0YTCc6JFQV@wuerfel \
    --to=arnd@arndb.de \
    --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).