From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Guanghui Feng <guanghuifeng@linux.alibaba.com>,
Zhenzhong Duan <zhenzhong.duan@intel.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/9][PULL REQUEST] Intel IOMMU updates for v7.4
Date: Mon, 28 Sep 2026 11:27:13 +0800 [thread overview]
Message-ID: <20260928032722.2868623-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
The following changes are queued for v7.4-rc1. This update includes a
set of quick fixes and cleanups, including:
- Enhanced IQE fault handling for batched multiple descriptors,
- Optimization of page-table level calculation in compute_vasz_lg2_ss(),
- Fixes for several pre-existing issues reported by Sashiko,
- General cleanup and refinement.
These patches are based on v7.3-rc5. The full series is also available
on GitHub:
https://github.com/LuBaolu/intel-iommu/commits/iommu/vt-d/next
Please consider pulling this series into the iommu/vt-d branch.
Best regards,
baolu
Guanghui Feng (1):
iommu/vt-d: Fix IQE handling to cover all descriptors in submission
range
Lu Baolu (7):
iommu/vt-d: Avoid out-of-range shift in qi_desc_dev_iotlb_pasid()
iommu/vt-d: Do not ignore context table copy failures
iommu/vt-d: Handle DID reservation errors when copying context tables
iommu/vt-d: Reserve scalable-mode DIDs from PASID entries during copy
iommu/vt-d: Use old domain parameter when attaching the blocking
domain
iommu/vt-d: Fix iopf refcount leak in nested attach
iommu/vt-d: Drop old iopf ref only after attach succeeds
Zhenzhong Duan (1):
iommu/vt-d: Fix page table level calculation in compute_vasz_lg2_ss()
drivers/iommu/intel/iommu.h | 17 +++-
drivers/iommu/intel/dmar.c | 70 +++++++++++++---
drivers/iommu/intel/iommu.c | 156 ++++++++++++++++++++++++++++++-----
drivers/iommu/intel/nested.c | 2 +
4 files changed, 211 insertions(+), 34 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-28 3:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 3:27 Lu Baolu [this message]
2026-09-28 3:27 ` [PATCH 1/9] iommu/vt-d: Fix page table level calculation in compute_vasz_lg2_ss() Lu Baolu
2026-09-28 3:27 ` [PATCH 2/9] iommu/vt-d: Avoid out-of-range shift in qi_desc_dev_iotlb_pasid() Lu Baolu
2026-09-28 3:27 ` [PATCH 3/9] iommu/vt-d: Do not ignore context table copy failures Lu Baolu
2026-09-28 3:27 ` [PATCH 4/9] iommu/vt-d: Handle DID reservation errors when copying context tables Lu Baolu
2026-09-28 3:27 ` [PATCH 5/9] iommu/vt-d: Reserve scalable-mode DIDs from PASID entries during copy Lu Baolu
2026-09-28 3:27 ` [PATCH 6/9] iommu/vt-d: Use old domain parameter when attaching the blocking domain Lu Baolu
2026-09-28 3:27 ` [PATCH 7/9] iommu/vt-d: Fix iopf refcount leak in nested attach Lu Baolu
2026-09-28 3:27 ` [PATCH 8/9] iommu/vt-d: Drop old iopf ref only after attach succeeds Lu Baolu
2026-09-28 3:27 ` [PATCH 9/9] iommu/vt-d: Fix IQE handling to cover all descriptors in submission range Lu Baolu
2026-09-28 8:18 ` [PATCH 0/9][PULL REQUEST] Intel IOMMU updates for v7.4 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=20260928032722.2868623-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=guanghuifeng@linux.alibaba.com \
--cc=iommu@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.