From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Yi Liu <yi.l.liu@intel.com>, Dmytro Maluka <dmaluka@chromium.org>,
Jinhui Guo <guojinhui.liam@bytedance.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] [PULL REQUEST] Intel IOMMU updates for v6.20
Date: Thu, 22 Jan 2026 09:48:49 +0800 [thread overview]
Message-ID: <20260122014856.2457052-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
The following changes have been queued for v6.20-rc1. They are about
some non-critical fixes, including:
- Skip dev-iotlb flush for inaccessible PCIe device
- Flush cache for PASID table before using it
- Use right invalidation method for SVA and NESTED domains
- Ensure atomicity in context and PASID entry updates
These patches are based on v6.19-rc6. Please consider them for the
iommu/vt-d branch.
Best regards,
baolu
Dmytro Maluka (1):
iommu/vt-d: Flush cache for PASID table before using it
Jinhui Guo (2):
iommu/vt-d: Skip dev-iotlb flush for inaccessible PCIe device without
scalable mode
iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in
scalable mode
Lu Baolu (3):
iommu/vt-d: Clear Present bit before tearing down PASID entry
iommu/vt-d: Clear Present bit before tearing down context entry
iommu/vt-d: Fix race condition during PASID entry replacement
Yi Liu (1):
iommu/vt-d: Flush piotlb for SVM and Nested domain
drivers/iommu/intel/iommu.h | 21 +++-
drivers/iommu/intel/pasid.h | 28 ++---
drivers/iommu/intel/cache.c | 9 +-
drivers/iommu/intel/iommu.c | 33 +++---
drivers/iommu/intel/nested.c | 9 +-
drivers/iommu/intel/pasid.c | 212 ++++-------------------------------
6 files changed, 83 insertions(+), 229 deletions(-)
--
2.43.0
next reply other threads:[~2026-01-22 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 1:48 Lu Baolu [this message]
2026-01-22 1:48 ` [PATCH 1/7] iommu/vt-d: Skip dev-iotlb flush for inaccessible PCIe device without scalable mode Lu Baolu
2026-01-22 1:48 ` [PATCH 2/7] iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in " Lu Baolu
2026-01-22 1:48 ` [PATCH 3/7] iommu/vt-d: Flush cache for PASID table before using it Lu Baolu
2026-01-22 1:48 ` [PATCH 4/7] iommu/vt-d: Flush piotlb for SVM and Nested domain Lu Baolu
2026-01-22 1:48 ` [PATCH 5/7] iommu/vt-d: Clear Present bit before tearing down PASID entry Lu Baolu
2026-01-22 1:48 ` [PATCH 6/7] iommu/vt-d: Clear Present bit before tearing down context entry Lu Baolu
2026-01-22 1:48 ` [PATCH 7/7] iommu/vt-d: Fix race condition during PASID entry replacement Lu Baolu
2026-01-22 8:20 ` [PATCH 0/7] [PULL REQUEST] Intel IOMMU updates for v6.20 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=20260122014856.2457052-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dmaluka@chromium.org \
--cc=guojinhui.liam@bytedance.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.l.liu@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