From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [git pull] IOMMU Fixes for Linux v6.0-rc4
Date: Sun, 11 Sep 2022 09:31:01 +0200 [thread overview]
Message-ID: <Yx2Otdo+oqAeDG6s@8bytes.org> (raw)
Hi Linus,
The following changes since commit 7e18e42e4b280c85b76967a9106a13ca61c16179:
Linux 6.0-rc4 (2022-09-04 13:10:01 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v6.0-rc4
for you to fetch changes up to 2380f1e8195ef612deea1dc7a3d611c5d2b9b56a:
iommu: Fix false ownership failure on AMD systems with PASID activated (2022-09-11 08:30:41 +0200)
----------------------------------------------------------------
IOMMU Fixes for Linux v6.0-rc4
Including:
- Intel VT-d fixes from Lu Baolu
- Boot kdump kernels with VT-d scalable mode on
- Calculate the right page table levels
- Fix two recursive locking issues
- Fix a lockdep splat issue
- AMD IOMMU fixes:
- Fix for completion-wait command to use full 64 bits of data
- Fix PASID related issue where GPU sound devices failed to
initialize
- Fix for Virtio-IOMMU to report correct caching behavior, needed for
use with VFIO
----------------------------------------------------------------
Jason Gunthorpe (1):
iommu: Fix false ownership failure on AMD systems with PASID activated
Jean-Philippe Brucker (1):
iommu/virtio: Fix interaction with VFIO
John Sperbeck (1):
iommu/amd: use full 64-bit value in build_completion_wait()
Lu Baolu (5):
iommu/vt-d: Fix kdump kernels boot failure with scalable mode
iommu/vt-d: Correctly calculate sagaw value of IOMMU
iommu/vt-d: Fix recursive lock issue in iommu_flush_dev_iotlb()
iommu/vt-d: Fix lockdep splat due to klist iteration in atomic context
iommu/vt-d: Fix possible recursive locking in intel_iommu_init()
drivers/iommu/amd/iommu.c | 3 +-
drivers/iommu/amd/iommu_v2.c | 2 +
drivers/iommu/intel/dmar.c | 7 ++
drivers/iommu/intel/iommu.c | 241 ++++++++++++++++++++-----------------------
drivers/iommu/intel/iommu.h | 9 +-
drivers/iommu/iommu.c | 21 +++-
drivers/iommu/virtio-iommu.c | 11 ++
include/linux/dmar.h | 4 +-
8 files changed, 163 insertions(+), 135 deletions(-)
Please pull.
Thanks,
Joerg
next reply other threads:[~2022-09-11 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 7:31 Joerg Roedel [this message]
2022-09-11 19:36 ` [git pull] IOMMU Fixes for Linux v6.0-rc4 pr-tracker-bot
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=Yx2Otdo+oqAeDG6s@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.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