From: Robin Murphy <robin.murphy@arm.com>
To: joro@8bytes.org
Cc: baolu.lu@linux.intel.com, andreas.noever@gmail.com,
michael.jamet@intel.com, mika.westerberg@linux.intel.com,
YehezkelShB@gmail.com, iommu@lists.linux-foundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
mario.limonciello@amd.com, hch@lst.de
Subject: [PATCH v4 0/4] iommu, thunderbolt: Make iommu_dma_protection more accurate
Date: Mon, 25 Apr 2022 13:42:01 +0100 [thread overview]
Message-ID: <cover.1650878781.git.robin.murphy@arm.com> (raw)
Hi all,
As promised, here's the really-actually-final version, cleaning up the
new interface in patch #1 to not introduce the new parameter before it's
ready, and rebased to make sure it correctly applies on -rc3.
Thanks,
Robin.
Mario Limonciello (1):
iommu/amd: Indicate whether DMA remap support is enabled
Robin Murphy (3):
iommu: Introduce device_iommu_capable()
iommu: Add capability for pre-boot DMA protection
thunderbolt: Make iommu_dma_protection more accurate
drivers/iommu/amd/amd_iommu_types.h | 4 +++
drivers/iommu/amd/init.c | 3 ++
drivers/iommu/amd/iommu.c | 2 ++
drivers/iommu/intel/iommu.c | 2 ++
drivers/iommu/iommu.c | 23 +++++++++++++++
drivers/thunderbolt/domain.c | 12 ++------
drivers/thunderbolt/nhi.c | 44 +++++++++++++++++++++++++++++
include/linux/iommu.h | 8 ++++++
include/linux/thunderbolt.h | 2 ++
9 files changed, 91 insertions(+), 9 deletions(-)
--
2.35.3.dirty
next reply other threads:[~2022-04-25 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 12:42 Robin Murphy [this message]
2022-04-25 12:42 ` [PATCH v4 1/4] iommu: Introduce device_iommu_capable() Robin Murphy
2022-04-25 12:42 ` [PATCH v4 2/4] iommu: Add capability for pre-boot DMA protection Robin Murphy
2022-04-25 12:42 ` [PATCH v4 3/4] thunderbolt: Make iommu_dma_protection more accurate Robin Murphy
2022-04-25 12:42 ` [PATCH v4 4/4] iommu/amd: Indicate whether DMA remap support is enabled 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.1650878781.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=baolu.lu@linux.intel.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
/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