From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [Linaro-mm-sig] [RFC 2/3] ARM: dma-mapping: Pass DMA attrs as IOMMU prot
Date: Thu, 20 Jun 2013 12:13:13 +0200 [thread overview]
Message-ID: <201306201213.13644.arnd@arndb.de> (raw)
In-Reply-To: <20130620.125431.1161068035083905855.hdoyu@nvidia.com>
On Thursday 20 June 2013, Hiroshi Doyu wrote:
> > If devices allocate via dma-mapping API, physical mem allocation, iova
> > allocation and iommu mapping happens internally.
> > Devices may allocate physical memory using any allocator (say ION
> > including carveout area), use "iommu mapping" API which will do iova
> > allocation and iommu mapping. The prot flags could be useful in this
> > case as well - not sure whether we would need dma-attrs here.
>
> I haven't followed ION recently, but can't ION backed by DMA mapping
> API instead of using IOMMU API directly?
For a GPU with an IOMMU, you typically want per-process IOMMU contexts,
which are only available when using the IOMMU API directly, as the
dma-mapping abstraction uses only one context for kernel space.
Arnd
next prev parent reply other threads:[~2013-06-20 10:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 5:49 [RFC 0/3] How to pass IOMMU map attr via DMA API? Hiroshi Doyu
[not found] ` <1371707384-30037-4-git-send-email-hdoyu@nvidia.com>
2013-06-20 6:50 ` [Linaro-mm-sig] [RFC 3/3] iommu/tegra: smmu: Support read-only mapping Kyungmin Park
2013-06-20 7:27 ` Hiroshi Doyu
[not found] ` <1371707384-30037-3-git-send-email-hdoyu@nvidia.com>
2013-06-20 8:07 ` [Linaro-mm-sig] [RFC 2/3] ARM: dma-mapping: Pass DMA attrs as IOMMU prot Nishanth Peethambaran
2013-06-20 8:24 ` Hiroshi Doyu
2013-06-20 8:55 ` Nishanth Peethambaran
2013-06-20 9:54 ` Hiroshi Doyu
2013-06-20 10:13 ` Arnd Bergmann [this message]
2013-06-20 10:34 ` Hiroshi Doyu
2013-06-20 10:57 ` Arnd Bergmann
2013-06-20 12:49 ` Nishanth Peethambaran
2013-06-20 9:31 ` [RFC 0/3] How to pass IOMMU map attr via DMA API? Will Deacon
2013-06-20 9:59 ` Hiroshi Doyu
2013-06-20 10:11 ` Catalin Marinas
2013-06-20 11:00 ` Hiroshi Doyu
2013-06-20 10:12 ` Will Deacon
2013-06-21 7:17 ` Marek Szyprowski
2013-06-21 16:03 ` Joerg Roedel
2013-06-24 5:17 ` Hiroshi Doyu
2013-06-24 7:21 ` Joerg Roedel
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=201306201213.13644.arnd@arndb.de \
--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).