From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Zhenzhong Duan <zhenzhong.duan@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Jason Gunthorpe <jgg@nvidia.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 00/10] [PULL REQUEST] Intel IOMMU updates for v7.1
Date: Thu, 2 Apr 2026 14:57:23 +0800 [thread overview]
Message-ID: <20260402065734.1687476-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
The following changes are queued for v7.1-rc1. This update introduces a
new feature and several refactorings, including:
- Support for dirty tracking on domains attached to PASID.
- Removal of unnecessary read*()/write*() wrappers.
- Improvements to the invalidation paths.
These patches are based on v7.0-rc6. Please consider them for the
iommu/vt-d branch.
Best regards,
baolu
Bjorn Helgaas (2):
iommu/vt-d: Remove dmar_readl() and dmar_readq()
iommu/vt-d: Remove dmar_writel() and dmar_writeq()
Jason Gunthorpe (4):
iommu/vt-d: Split piotlb invalidation into range and all
iommu/vt-d: Pass size_order to qi_desc_piotlb() not npages
iommu/vt-d: Remove the remaining pages along the invalidation path
iommu/vt-d: Simplify calculate_psi_aligned_address()
Zhenzhong Duan (4):
iommu/vt-d: Block PASID attachment to nested domain with dirty
tracking
iommu/vt-d: Rename device_set_dirty_tracking() and pass dmar_domain
pointer
iommu/vt-d: Support dirty tracking on PASID
iommufd/selftest: Test dirty tracking on PASID
drivers/iommu/intel/iommu.h | 47 +++++------
drivers/iommu/intel/trace.h | 18 ++---
drivers/iommu/intel/cache.c | 100 ++++++++++--------------
drivers/iommu/intel/debugfs.c | 18 ++---
drivers/iommu/intel/dmar.c | 43 ++++------
drivers/iommu/intel/iommu.c | 55 +++++++------
drivers/iommu/intel/irq_remapping.c | 6 +-
drivers/iommu/intel/pasid.c | 6 +-
drivers/iommu/intel/perfmon.c | 50 ++++++------
drivers/iommu/intel/prq.c | 28 +++----
tools/testing/selftests/iommu/iommufd.c | 27 +++++++
11 files changed, 193 insertions(+), 205 deletions(-)
--
2.43.0
next reply other threads:[~2026-04-02 7:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 6:57 Lu Baolu [this message]
2026-04-02 6:57 ` [PATCH 01/10] iommu/vt-d: Block PASID attachment to nested domain with dirty tracking Lu Baolu
2026-04-02 6:57 ` [PATCH 02/10] iommu/vt-d: Rename device_set_dirty_tracking() and pass dmar_domain pointer Lu Baolu
2026-04-02 6:57 ` [PATCH 03/10] iommu/vt-d: Support dirty tracking on PASID Lu Baolu
2026-04-02 6:57 ` [PATCH 04/10] iommufd/selftest: Test " Lu Baolu
2026-04-02 6:57 ` [PATCH 05/10] iommu/vt-d: Remove dmar_readl() and dmar_readq() Lu Baolu
2026-04-02 6:57 ` [PATCH 06/10] iommu/vt-d: Remove dmar_writel() and dmar_writeq() Lu Baolu
2026-04-02 6:57 ` [PATCH 07/10] iommu/vt-d: Split piotlb invalidation into range and all Lu Baolu
2026-04-02 6:57 ` [PATCH 08/10] iommu/vt-d: Pass size_order to qi_desc_piotlb() not npages Lu Baolu
2026-04-02 6:57 ` [PATCH 09/10] iommu/vt-d: Remove the remaining pages along the invalidation path Lu Baolu
2026-04-02 6:57 ` [PATCH 10/10] iommu/vt-d: Simplify calculate_psi_aligned_address() Lu Baolu
2026-04-02 8:39 ` Baolu Lu
2026-04-02 9:46 ` Joerg Roedel
2026-04-02 15:35 ` Jason Gunthorpe
2026-04-02 7:26 ` [PATCH 00/10] [PULL REQUEST] Intel IOMMU updates for v7.1 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=20260402065734.1687476-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenzhong.duan@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