From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/7] Introduce automatic DMA configuration for IOMMU masters
Date: Wed, 03 Sep 2014 00:50:26 +0300 [thread overview]
Message-ID: <1804700.tdyjJcKU9T@avalon> (raw)
In-Reply-To: <3133975.8bg0CLVMMz@wuerfel>
On Tuesday 02 September 2014 14:43:18 Arnd Bergmann wrote:
> On Tuesday 02 September 2014 14:24:18 Marek Szyprowski wrote:
> > >>> For isolation purposes, it can only help to have more domains, but
> > >>> I would guess that there is some space overhead in maintaining lots
> > >>> of page tables.
> > >>
> > >> I'm okay with both approaches (separate domain for each device vs.
> > >> single common domain for all devices). Maybe this can be some kind of
> > >> Kconfig option added to DMA debugging? Separation might be really
> > >> helpful when debugging strange device behavior.
> > >
> > > One potential problem with a single domain is when you have multiple
> > > instances of a given IOMMU, each with different hardware restrictions.
> > > Then you can end up with multiple sets of page tables for the domain
> > > which, although not impossible to work with, is a bit of a mess.
> >
> > Maybe the default dma-mapping domain should be one per a given IOMMU
> > instance? This will simplify a lot of things in such case.
>
> Yes, that sounds like a good idea.
That would work as a default configuration for the Renesas IPMMU IOMMU, which
supports four TLBs to be shared between more than four bus masters. Ideally
I'd like to make the bus master to TLB association somehow configurable, but
associating all bus masters with a single TLB as a first step is fine.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-09-02 21:50 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 15:54 [RFC PATCH 0/7] Introduce automatic DMA configuration for IOMMU masters Will Deacon
2014-08-29 15:54 ` [RFC PATCH 1/7] iommu: provide early initialisation hook for IOMMU drivers Will Deacon
2014-09-01 7:52 ` Thierry Reding
2014-09-01 14:31 ` Arnd Bergmann
2014-09-01 16:36 ` Will Deacon
2014-09-02 6:56 ` Laurent Pinchart
2014-09-02 14:47 ` Varun Sethi
2014-09-02 15:04 ` Arnd Bergmann
2014-08-29 15:54 ` [RFC PATCH 2/7] dma-mapping: replace set_arch_dma_coherent_ops with arch_setup_dma_ops Will Deacon
2014-09-01 14:27 ` Arnd Bergmann
2014-09-01 16:20 ` Will Deacon
2014-08-29 15:54 ` [RFC PATCH 3/7] iommu: add new iommu_ops callback for adding a device with a set of IDs Will Deacon
2014-09-01 8:13 ` Thierry Reding
2014-09-01 14:39 ` Arnd Bergmann
2014-09-01 16:34 ` Will Deacon
2014-09-01 17:18 ` Arnd Bergmann
2014-08-29 15:54 ` [RFC PATCH 4/7] iommu: provide helper function to configure an IOMMU for an of master Will Deacon
2014-09-01 8:29 ` Thierry Reding
2014-09-01 14:46 ` Arnd Bergmann
2014-09-01 16:40 ` Will Deacon
2014-09-01 20:18 ` Arnd Bergmann
2014-09-02 10:03 ` Will Deacon
2014-09-02 12:15 ` Arnd Bergmann
2014-09-02 13:05 ` Will Deacon
2014-09-02 14:01 ` Arnd Bergmann
2014-09-02 20:59 ` jroedel at suse.de
2014-09-03 9:45 ` Will Deacon
2014-09-02 15:03 ` Varun Sethi
2014-09-02 15:08 ` Arnd Bergmann
2014-09-02 10:23 ` Laurent Pinchart
2014-09-02 10:51 ` Laurent Pinchart
2014-09-02 11:03 ` Will Deacon
2014-09-02 19:08 ` Laurent Pinchart
2014-09-02 14:55 ` Varun Sethi
2014-08-29 15:54 ` [RFC PATCH 5/7] dma-mapping: detect and configure IOMMU in of_dma_configure Will Deacon
2014-09-01 14:53 ` Arnd Bergmann
2014-08-29 15:54 ` [RFC PATCH 6/7] arm: call iommu_init before of_platform_populate Will Deacon
2014-08-29 15:54 ` [RFC PATCH 7/7] arm: dma-mapping: plumb our iommu mapping ops into arch_setup_dma_ops Will Deacon
2014-09-02 6:26 ` [RFC PATCH 0/7] Introduce automatic DMA configuration for IOMMU masters Marek Szyprowski
2014-09-02 8:31 ` Will Deacon
2014-09-02 8:48 ` Marek Szyprowski
2014-09-02 8:56 ` Arnd Bergmann
2014-09-02 10:42 ` Marek Szyprowski
2014-09-02 10:57 ` Will Deacon
2014-09-02 12:24 ` Marek Szyprowski
2014-09-02 12:43 ` Arnd Bergmann
2014-09-02 21:50 ` Laurent Pinchart [this message]
2014-09-02 12:22 ` Arnd Bergmann
2014-09-02 12:30 ` Marek Szyprowski
2014-09-02 12:46 ` Arnd Bergmann
2014-09-02 13:11 ` Marek Szyprowski
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=1804700.tdyjJcKU9T@avalon \
--to=laurent.pinchart@ideasonboard.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).