From: mitchelh@codeaurora.org (Mitchel Humpherys)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Add access-protected IOMMU mappings
Date: Wed, 17 Sep 2014 13:16:07 -0700 [thread overview]
Message-ID: <1410984969-2340-1-git-send-email-mitchelh@codeaurora.org> (raw)
This series introduces a new mapping flag to indicate that the mapping
should be created with access protection applied. Support for this new flag
is then added to the ARM SMMU driver.
Mitchel Humpherys (2):
iommu: add IOMMU_PRIV flag for access-protected mappings
iommu/arm-smmu: add support for access-protected mappings
drivers/iommu/arm-smmu.c | 5 +++--
include/linux/iommu.h | 1 +
2 files changed, 4 insertions(+), 2 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2014-09-17 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 20:16 Mitchel Humpherys [this message]
2014-09-17 20:16 ` [PATCH 1/2] iommu: add IOMMU_PRIV flag for access-protected mappings Mitchel Humpherys
2014-09-17 20:16 ` [PATCH 2/2] iommu/arm-smmu: add support " Mitchel Humpherys
2014-09-19 22:05 ` Will Deacon
2014-09-22 22:28 ` Mitchel Humpherys
2014-09-24 16:27 ` Will Deacon
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=1410984969-2340-1-git-send-email-mitchelh@codeaurora.org \
--to=mitchelh@codeaurora.org \
--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).