From: Jason Gunthorpe <jgg@ziepe.ca>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
dwmw2@infradead.org, baolu.lu@linux.intel.com, joro@8bytes.org,
will@kernel.org, robin.murphy@arm.com, kevin.tian@intel.com
Subject: Re: [PATCH 0/3] iommupt/vtd: Support dirty tracking on PASID
Date: Thu, 5 Feb 2026 20:43:25 -0400 [thread overview]
Message-ID: <20260206004325.GB943673@ziepe.ca> (raw)
In-Reply-To: <20260205023405.41583-1-zhenzhong.duan@intel.com>
On Wed, Feb 04, 2026 at 09:34:01PM -0500, 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
>
>
> Zhenzhong Duan (3):
> iommupt/vtd: Pass dmar_domain pointer to device_set_dirty_tracking()
> iommupt/vtd: Support dirty tracking on PASID
> iommufd/selftest: Test dirty tracking on PASID
I'm not sure why you marked this s iommupt? It isn't right?
Also only the second stage table supports dirty tracking so I'm
confused what is the issue? Is it trying to say that if a second stage
is written to a pasid entry on a !=0 pasid path it doesn't work right?
But it does work on a 0 pasid?
Huh?
That sounds like a systemic problem, the two flows shouldn't actually
be any different.
Jason
next prev parent reply other threads:[~2026-02-06 0:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 2:34 Zhenzhong Duan
2026-02-05 2:34 ` [PATCH 1/3] iommupt/vtd: Pass dmar_domain pointer to device_set_dirty_tracking() Zhenzhong Duan
2026-02-05 2:34 ` [PATCH 2/3] iommupt/vtd: Support dirty tracking on PASID Zhenzhong Duan
2026-03-27 7:51 ` Tian, Kevin
2026-03-27 9:12 ` Duan, Zhenzhong
2026-02-05 2:34 ` [PATCH 3/3] iommufd/selftest: Test " Zhenzhong Duan
2026-02-06 0:43 ` Jason Gunthorpe [this message]
2026-02-06 3:44 ` [PATCH 0/3] iommupt/vtd: Support " Duan, Zhenzhong
2026-03-23 1:51 ` Duan, Zhenzhong
2026-03-23 2:54 ` Baolu Lu
2026-03-26 10:54 ` Yi Liu
2026-03-30 2:04 ` Duan, Zhenzhong
2026-03-30 7:57 ` Baolu Lu
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=20260206004325.GB943673@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--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=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
all inboxes | Powered by JetHome®