From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 0/3] arm64: IOMMU-backed DMA mapping
Date: Fri, 6 Feb 2015 14:55:12 +0000 [thread overview]
Message-ID: <cover.1423226542.git.robin.murphy@arm.com> (raw)
Hi all,
This is an updated RFC to address some of the initial comments[1].
The first two patches of the original posting, along with the IOVA
series, are now in -next so aren't included here.
If this is starting to look tidy enough, then I'll get to work on
porting arch/arm as well so I can repost as a formal patch set.
Thanks,
Robin.
A branch with all the necessary bits is available at:
git://linux-arm.org/linux-rm iommu/dma
Main changes since v1:
* rebased to -rc7
* moved common code to drivers/iommu, and tidied up the config
dependencies
* renamed iommu_dma_mapping to better reflect that it's a managed domain
* abstracted away the explicit use of archdata
* finished the map_sg implementation
* fixed up the mmap implementation with the arch/arm one for now
* removed the iova_to_phys accessor in favour of (more flexibly)
exposing the iommu domain for where it's needed
More complicated things still to do:
* understand and sort out the compound pages issue
* get domain and group allocation right - I'd like to try integrating
Joerg's proposals for that area[2][3], which should help.
[1]:http://article.gmane.org/gmane.linux.kernel.iommu/8213
[2]:http://thread.gmane.org/gmane.linux.ports.tegra/20907
[3]:http://thread.gmane.org/gmane.linux.kernel.iommu/8492
Robin Murphy (3):
iommu: implement common IOMMU ops for DMA mapping
arm64: add IOMMU dma_ops
arm64: hook up IOMMU dma_ops
arch/arm64/Kconfig | 1 +
arch/arm64/include/asm/device.h | 3 +
arch/arm64/include/asm/dma-mapping.h | 28 +-
arch/arm64/mm/dma-mapping.c | 335 +++++++++++++++++++++
drivers/iommu/Kconfig | 7 +
drivers/iommu/Makefile | 1 +
drivers/iommu/dma-iommu.c | 552 +++++++++++++++++++++++++++++++++++
include/linux/dma-iommu.h | 94 ++++++
8 files changed, 1016 insertions(+), 5 deletions(-)
create mode 100644 drivers/iommu/dma-iommu.c
create mode 100644 include/linux/dma-iommu.h
--
1.9.1
next reply other threads:[~2015-02-06 14:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 14:55 Robin Murphy [this message]
2015-02-06 14:55 ` [RFC PATCH v2 1/3] iommu: implement common IOMMU ops for DMA mapping Robin Murphy
2015-02-09 4:05 ` Will Deacon
2015-02-10 15:11 ` Robin Murphy
2015-03-12 12:45 ` Marek Szyprowski
2015-02-06 14:55 ` [RFC PATCH v2 2/3] arm64: add IOMMU dma_ops Robin Murphy
2015-02-09 6:02 ` Will Deacon
2015-02-10 15:40 ` Robin Murphy
2015-02-10 4:39 ` Yingjoe Chen
2015-02-10 12:07 ` Robin Murphy
2015-02-14 8:03 ` Yong Wu
2015-02-16 20:04 ` Robin Murphy
2015-03-03 3:38 ` Yong Wu
2015-03-03 12:15 ` Robin Murphy
2015-03-05 0:19 ` Laura Abbott
2015-03-05 11:16 ` Robin Murphy
2015-03-09 17:59 ` Russell King - ARM Linux
2015-03-09 20:09 ` Robin Murphy
2015-03-10 10:16 ` Robin Murphy
2015-03-12 12:50 ` Marek Szyprowski
2015-02-06 14:55 ` [RFC PATCH v2 3/3] arm64: hook up " Robin Murphy
2015-03-03 11:05 ` leizhen
2015-03-03 13:10 ` Robin Murphy
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=cover.1423226542.git.robin.murphy@arm.com \
--to=robin.murphy@arm.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).