linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] iommu/arm-smmu: updates for 3.14
Date: Tue, 17 Dec 2013 18:08:54 +0000	[thread overview]
Message-ID: <20131217180854.GG349@mudshark.cambridge.arm.com> (raw)

Hi Joerg, Alex,

Please pull the arm-smmu updates below for 3.14. The main changes are adding
an IOMMU_EXEC flag to allow for non-executable mappings (in response to work
that rmk has done for the CPU-side of things) and automatically adding
devices to an IOMMU group.

Thanks,

Will

--->8

The following changes since commit 319e2e3f63c348a9b66db4667efa73178e18b17d:

  Linux 3.13-rc4 (2013-12-15 12:31:33 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git for-joerg/arm-smmu/updates

for you to fetch changes up to cf2d45b19ddb361241f36d8c9f3d0b234a18459b:

  iommu/arm-smmu: add support for IOMMU_EXEC (2013-12-16 19:30:32 +0000)

----------------------------------------------------------------
Antonios Motakis (1):
      iommu/arm-smmu: add devices attached to the SMMU to an IOMMU group

Will Deacon (3):
      iommu/arm-smmu: use VA_BITS to determine arm64 virtual address space
      iommu: add IOMMU_EXEC flag for safely allowing XN mappings
      iommu/arm-smmu: add support for IOMMU_EXEC

 drivers/iommu/arm-smmu.c | 33 ++++++++++++++++++++++++++-------
 include/linux/iommu.h    |  7 ++++---
 2 files changed, 30 insertions(+), 10 deletions(-)

             reply	other threads:[~2013-12-17 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17 18:08 Will Deacon [this message]
2013-12-30 13:19 ` [GIT PULL] iommu/arm-smmu: updates for 3.14 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=20131217180854.GG349@mudshark.cambridge.arm.com \
    --to=will.deacon@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).