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-rc6
Date: Wed, 21 Sep 2022 14:19:05 +0200 [thread overview]
Message-ID: <YysBOff9ZGM/EfQh@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
Hi Linus,
The following changes since commit 521a547ced6477c54b4b0cc206000406c221b4d6:
Linux 6.0-rc6 (2022-09-18 13:44:14 -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-rc6
for you to fetch changes up to 154897807050c1161cb2660e502fc0470d46b986:
iommu/vt-d: Check correct capability for sagaw determination (2022-09-21 10:22:54 +0200)
----------------------------------------------------------------
IOMMU Fixes for Linux v6.0-rc6
Including:
- Two fixes for Intel VT-d:
- Check the right capability bit for 5-level page table support.
- Revert a previous fix which caused a regression with Thunderbolt
devices.
----------------------------------------------------------------
Lu Baolu (1):
Revert "iommu/vt-d: Fix possible recursive locking in intel_iommu_init()"
Yi Liu (1):
iommu/vt-d: Check correct capability for sagaw determination
drivers/iommu/intel/dmar.c | 7 -------
drivers/iommu/intel/iommu.c | 29 ++++++++++++++++++++++++++---
include/linux/dmar.h | 4 +---
3 files changed, 27 insertions(+), 13 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-09-21 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 12:19 Joerg Roedel [this message]
2022-09-21 16:15 ` [git pull] IOMMU Fixes for Linux v6.0-rc6 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=YysBOff9ZGM/EfQh@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