From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] arm-smmu: Implementation and context format differentiation
Date: Wed, 13 Apr 2016 18:12:56 +0100 [thread overview]
Message-ID: <cover.1460391217.git.robin.murphy@arm.com> (raw)
Hi all,
This is almost 3 separate sub-series, but there's enough interdependency
and horrid merge conflicts that I've been keeping it all together.
- Patches 1-3 rationalise implementation-specific details and errata,
in order to start shovelling in yet more wonderful workarounds.
- Patches 3-6 do a broadly similar thing for context formats, breaking
the effective hard-coding to allow it to become a runtime choice.
(With the bonus of unblocking short-descriptor support, once I find
and revive the hac^Wpatches I was using for that.)
- Patch 7 then takes advantage of the previous changes to support the
hilarious raison d'etre of MMU-401, in all its glory.
This is all based on top of the ThunderX patches in Will's iommu/devel
branch. It also conflicts somewhat with my per-domain page size series;
since this is probably less contentious, I expect I'll optimistically
rebase that on top of this one before I post it again.
Robin.
---
Robin Murphy (7):
iommu/arm-smmu: Differentiate specific implementations
iommu/arm-smmu: Convert ThunderX workaround to new method
iommu/arm-smmu: Work around MMU-500 prefetch errata
io-64-nonatomic: Add relaxed accessor variants
iommu/arm-smmu: Tidy up 64-bit/atomic I/O accesses
iommu/arm-smmu: Decouple context format from kernel config
iommu/arm-smmu: Support SMMUv1 64KB supplement
Documentation/arm64/silicon-errata.txt | 1 +
drivers/iommu/arm-smmu.c | 238 +++++++++++++++++++++++----------
include/linux/io-64-nonatomic-hi-lo.h | 25 ++++
include/linux/io-64-nonatomic-lo-hi.h | 25 ++++
4 files changed, 216 insertions(+), 73 deletions(-)
--
2.7.3.dirty
next reply other threads:[~2016-04-13 17:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 17:12 Robin Murphy [this message]
2016-04-13 17:12 ` [PATCH 1/7] iommu/arm-smmu: Differentiate specific implementations Robin Murphy
2016-04-13 21:15 ` Chalamarla, Tirumalesh
2016-04-13 17:12 ` [PATCH 2/7] iommu/arm-smmu: Convert ThunderX workaround to new method Robin Murphy
2016-04-13 21:16 ` Chalamarla, Tirumalesh
2016-04-13 17:12 ` [PATCH 3/7] iommu/arm-smmu: Work around MMU-500 prefetch errata Robin Murphy
2016-04-21 16:15 ` Will Deacon
2016-04-21 16:16 ` Will Deacon
2016-04-13 17:13 ` [PATCH 4/7] io-64-nonatomic: Add relaxed accessor variants Robin Murphy
2016-04-21 16:18 ` Will Deacon
2016-04-22 17:08 ` Robin Murphy
2016-04-25 13:32 ` Will Deacon
2016-04-25 15:21 ` Arnd Bergmann
2016-04-25 15:28 ` Robin Murphy
2016-04-25 15:41 ` Arnd Bergmann
2016-04-25 16:11 ` Will Deacon
2016-04-25 16:11 ` Arnd Bergmann
2016-04-26 10:38 ` [PATCH v2] " Robin Murphy
2016-04-13 17:13 ` [PATCH 5/7] iommu/arm-smmu: Tidy up 64-bit/atomic I/O accesses Robin Murphy
2016-04-13 17:13 ` [PATCH 6/7] iommu/arm-smmu: Decouple context format from kernel config Robin Murphy
2016-04-21 16:30 ` Will Deacon
2016-04-22 17:38 ` Robin Murphy
2016-04-25 11:02 ` Will Deacon
2016-04-25 13:14 ` Robin Murphy
2016-04-25 13:41 ` Will Deacon
2016-04-25 16:21 ` Robin Murphy
2016-04-28 16:12 ` [PATCH v2] " Robin Murphy
2016-04-13 17:13 ` [PATCH 7/7] iommu/arm-smmu: Support SMMUv1 64KB supplement 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.1460391217.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).