From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] [PULL REQUEST] iommu/vt-d: Fixes for v6.18-rc1
Date: Fri, 26 Sep 2025 10:41:29 +0800 [thread overview]
Message-ID: <20250926024130.157514-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
The following fix has been queued for the Intel iommu driver. It aims to
solve the following problem:
- Disallow dirty tracking if page walk is incoherent
This fix is not so critical for v6.17-rc. Considering the upcoming merge
window, it would be fine to include them with other patches for v6.18.
Please consider it.
Best regards,
baolu
Lu Baolu (1):
iommu/vt-d: Disallow dirty tracking if incoherent page walk
drivers/iommu/intel/iommu.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2025-09-26 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 2:41 Lu Baolu [this message]
2025-09-26 2:41 ` [PATCH 1/1] iommu/vt-d: Disallow dirty tracking if incoherent page walk Lu Baolu
2025-09-26 8:03 ` [PATCH 0/1] [PULL REQUEST] iommu/vt-d: Fixes for v6.18-rc1 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=20250926024130.157514-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.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