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

 drivers/iommu/intel/iommu.c             | 33 ++++++++++++++-----------
 tools/testing/selftests/iommu/iommufd.c | 27 ++++++++++++++++++++
 2 files changed, 45 insertions(+), 15 deletions(-)

-- 
2.47.3

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