All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: [GIT PULL] iommu: IOMMU_PRIV support for 4.11
Date: Fri, 27 Jan 2017 16:46:21 +0000	[thread overview]
Message-ID: <20170127164621.GB10758@arm.com> (raw)

Hi Joerg,

Please pull the following IOMMU changes for 4.11. These patches from
Sricharan add support for "privileged" IOMMU mappings, which are useful
with master devices that support transactions at different privilege
levels and want to control the permissions independently.

Cheers,

Will

--->8

The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:

  Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git iommu/iommu-priv

for you to fetch changes up to fa8c57db44068a77903d9688382b461a836eee68:

  iommu: Better document the IOMMU_PRIV flag (2017-01-27 13:49:35 +0000)

----------------------------------------------------------------
Jeremy Gebben (1):
      iommu/io-pgtable-arm: add support for the IOMMU_PRIV flag

Mitchel Humpherys (4):
      iommu: add IOMMU_PRIV attribute
      common: DMA-mapping: add DMA_ATTR_PRIVILEGED attribute
      arm64/dma-mapping: Implement DMA_ATTR_PRIVILEGED
      dmaengine: pl330: Make sure microcode is privileged

Robin Murphy (3):
      iommu/io-pgtable-arm-v7s: Add support for the IOMMU_PRIV flag
      Revert "iommu/arm-smmu: Set PRIVCFG in stage 1 STEs"
      iommu: Better document the IOMMU_PRIV flag

Sricharan R (2):
      arm/dma-mapping: Implement DMA_ATTR_PRIVILEGED
      iommu/arm-smmu: Set privileged attribute to 'default' instead of 'unprivileged'

 Documentation/DMA-attributes.txt   | 10 +++++++
 arch/arm/mm/dma-mapping.c          | 60 +++++++++++++++++++-------------------
 arch/arm64/mm/dma-mapping.c        |  6 ++--
 drivers/dma/pl330.c                |  5 ++--
 drivers/iommu/arm-smmu-v3.c        |  7 +----
 drivers/iommu/arm-smmu.c           |  2 +-
 drivers/iommu/dma-iommu.c          | 12 ++++++--
 drivers/iommu/io-pgtable-arm-v7s.c |  6 +++-
 drivers/iommu/io-pgtable-arm.c     |  5 +++-
 include/linux/dma-iommu.h          |  3 +-
 include/linux/dma-mapping.h        |  7 +++++
 include/linux/iommu.h              | 10 +++++++
 12 files changed, 85 insertions(+), 48 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] iommu: IOMMU_PRIV support for 4.11
Date: Fri, 27 Jan 2017 16:46:21 +0000	[thread overview]
Message-ID: <20170127164621.GB10758@arm.com> (raw)

Hi Joerg,

Please pull the following IOMMU changes for 4.11. These patches from
Sricharan add support for "privileged" IOMMU mappings, which are useful
with master devices that support transactions at different privilege
levels and want to control the permissions independently.

Cheers,

Will

--->8

The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:

  Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git iommu/iommu-priv

for you to fetch changes up to fa8c57db44068a77903d9688382b461a836eee68:

  iommu: Better document the IOMMU_PRIV flag (2017-01-27 13:49:35 +0000)

----------------------------------------------------------------
Jeremy Gebben (1):
      iommu/io-pgtable-arm: add support for the IOMMU_PRIV flag

Mitchel Humpherys (4):
      iommu: add IOMMU_PRIV attribute
      common: DMA-mapping: add DMA_ATTR_PRIVILEGED attribute
      arm64/dma-mapping: Implement DMA_ATTR_PRIVILEGED
      dmaengine: pl330: Make sure microcode is privileged

Robin Murphy (3):
      iommu/io-pgtable-arm-v7s: Add support for the IOMMU_PRIV flag
      Revert "iommu/arm-smmu: Set PRIVCFG in stage 1 STEs"
      iommu: Better document the IOMMU_PRIV flag

Sricharan R (2):
      arm/dma-mapping: Implement DMA_ATTR_PRIVILEGED
      iommu/arm-smmu: Set privileged attribute to 'default' instead of 'unprivileged'

 Documentation/DMA-attributes.txt   | 10 +++++++
 arch/arm/mm/dma-mapping.c          | 60 +++++++++++++++++++-------------------
 arch/arm64/mm/dma-mapping.c        |  6 ++--
 drivers/dma/pl330.c                |  5 ++--
 drivers/iommu/arm-smmu-v3.c        |  7 +----
 drivers/iommu/arm-smmu.c           |  2 +-
 drivers/iommu/dma-iommu.c          | 12 ++++++--
 drivers/iommu/io-pgtable-arm-v7s.c |  6 +++-
 drivers/iommu/io-pgtable-arm.c     |  5 +++-
 include/linux/dma-iommu.h          |  3 +-
 include/linux/dma-mapping.h        |  7 +++++
 include/linux/iommu.h              | 10 +++++++
 12 files changed, 85 insertions(+), 48 deletions(-)

             reply	other threads:[~2017-01-27 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 16:46 Will Deacon [this message]
2017-01-27 16:46 ` [GIT PULL] iommu: IOMMU_PRIV support for 4.11 Will Deacon
     [not found] ` <20170127164621.GB10758-5wv7dgnIgG8@public.gmane.org>
2017-01-30 15:06   ` Joerg Roedel
2017-01-30 15:06     ` 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=20170127164621.GB10758@arm.com \
    --to=will.deacon-5wv7dgnigg8@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.