From: Baolu Lu <baolu.lu@linux.intel.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: dwmw2@infradead.org, jgg@ziepe.ca, kevin.tian@intel.com,
joro@8bytes.org, will@kernel.org, robin.murphy@arm.com,
yi.l.liu@intel.com
Subject: Re: [PATCH v2 0/4] iommupt/vtd: Support dirty tracking on PASID
Date: Wed, 1 Apr 2026 14:46:16 +0800 [thread overview]
Message-ID: <619eae3d-db3a-400b-b733-f9ee8340ee17@linux.intel.com> (raw)
In-Reply-To: <20260330101108.12594-1-zhenzhong.duan@intel.com>
On 3/30/26 18:11, Zhenzhong Duan wrote:
> Hi,
>
> When we add pasid support in QEMU for passthrough device, we found
> PASID attachment to a nested parent domain with dirty tracking failed.
>
> It's because PASID-level dirty tracking is not there yet, by adding it,
> we can enable PASID attachment to such domain.
>
> Thanks
> Zhenzhong
>
> Changelog:
> v2:
> - a new patch1 to add a check in intel_nested_set_dev_pasid() (Kevin)
> - s/device_set_dirty_tracking/domain_set_dirty_tracking (Liuyi)
> - add R-b
>
> Zhenzhong Duan (4):
> iommu/vt-d: Block PASID attachment to nested domain with dirty
> tracking
> iommupt/vtd: Rename device_set_dirty_tracking() and pass dmar_domain
> pointer
> iommupt/vtd: Support dirty tracking on PASID
> iommufd/selftest: Test dirty tracking on PASID
Queued for iommu next with "iommupt/vtd" changed to "iommu/vt-d" in the
titles.
Thanks,
baolu
prev parent reply other threads:[~2026-04-01 6:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 10:11 Zhenzhong Duan
2026-03-30 10:11 ` [PATCH v2 1/4] iommu/vt-d: Block PASID attachment to nested domain with dirty tracking Zhenzhong Duan
2026-03-31 7:19 ` Tian, Kevin
2026-03-31 7:36 ` Yi Liu
2026-04-01 9:02 ` Duan, Zhenzhong
2026-03-30 10:11 ` [PATCH v2 2/4] iommupt/vtd: Rename device_set_dirty_tracking() and pass dmar_domain pointer Zhenzhong Duan
2026-03-31 7:19 ` Tian, Kevin
2026-03-30 10:11 ` [PATCH v2 3/4] iommupt/vtd: Support dirty tracking on PASID Zhenzhong Duan
2026-03-31 7:19 ` Tian, Kevin
2026-03-30 10:11 ` [PATCH v2 4/4] iommufd/selftest: Test " Zhenzhong Duan
2026-03-31 7:19 ` Tian, Kevin
2026-04-01 6:46 ` Baolu Lu [this message]
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=619eae3d-db3a-400b-b733-f9ee8340ee17@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
--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
Powered by JetHome