From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [git pull] IOMMU Updates for Linux v4.18
Date: Fri, 8 Jun 2018 17:03:14 +0200 [thread overview]
Message-ID: <20180608150309.esh35cutnhpf5ry4@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3038 bytes --]
Hi Linus,
The following changes since commit b04e217704b7f879c6b91222b066983a44a7a09f:
Linux 4.17-rc7 (2018-05-27 13:01:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-updates-v4.18
for you to fetch changes up to 1f568357117cafb48aafb10413cbd1567dc015b1:
Merge branches 'arm/io-pgtable', 'arm/qcom', 'arm/tegra', 'x86/vt-d', 'x86/amd' and 'core' into next (2018-05-29 16:58:17 +0200)
----------------------------------------------------------------
IOMMU Updates for Linux v4.18
Nothing big this time. In particular:
- Debugging code for Tegra-GART
- Improvement in Intel VT-d fault printing to prevent
soft-lockups when on fault storms
- Improvements in AMD IOMMU event reporting
- NUMA aware allocation in io-pgtable code for ARM
- Various other small fixes and cleanups all over the place
----------------------------------------------------------------
Andy Shevchenko (1):
iommu: Remove extra NULL check when call strtobool()
Anna-Maria Gleixner (2):
iommu/amd: Fix grammar of comments
iommu/amd: Prevent possible null pointer dereference and infinite loop
Dmitry Osipenko (2):
iommu/tegra: gart: Add debugging facility
iommu/tegra: gart: Fix gart_iommu_unmap()
Dmitry Safonov (1):
iommu/vt-d: Ratelimit each dmar fault printing
Gary R Hook (2):
iommu/amd: Update the PASID information printed to the system log
iommu/amd: Update logging information for new event type
Geert Uytterhoeven (1):
iommu: Remove depends on HAS_DMA in case of platform dependency
Joerg Roedel (1):
Merge branches 'arm/io-pgtable', 'arm/qcom', 'arm/tegra', 'x86/vt-d', 'x86/amd' and 'core' into next
Lu Baolu (4):
iommu/vt-d: Clean up unused variable in find_or_alloc_domain
iommu/vt-d: Clean up pasid quirk for pre-production devices
iommu/vt-d: Remove unnecessary parentheses
iommu: Clean up the comments for iommu_group_alloc
Peter Xu (2):
iommu/vt-d: Introduce __mapping_notify_one()
iommu/vt-d: Fix iotlb psi missing for mappings
Robin Murphy (1):
iommu/io-pgtable-arm: Make allocations NUMA-aware
Wolfram Sang (1):
iommu/qcom: Simplify getting .drvdata
YueHaibing (1):
iommu/io-pgtable-arm: Use for_each_set_bit to simplify code
drivers/iommu/Kconfig | 5 +-
drivers/iommu/amd_iommu.c | 69 ++++++++++++-------------
drivers/iommu/amd_iommu_types.h | 1 +
drivers/iommu/dmar.c | 8 ++-
drivers/iommu/intel-iommu.c | 101 ++++++++++++++++++-------------------
drivers/iommu/intel-svm.c | 2 +-
drivers/iommu/io-pgtable-arm-v7s.c | 5 +-
drivers/iommu/io-pgtable-arm.c | 18 ++++---
drivers/iommu/iommu.c | 7 +--
drivers/iommu/qcom_iommu.c | 6 +--
drivers/iommu/tegra-gart.c | 15 +++++-
include/linux/intel-iommu.h | 1 -
12 files changed, 122 insertions(+), 116 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2018-06-08 15:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180608150309.esh35cutnhpf5ry4@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome