From: Zhenzhong Duan <zhenzhong.duan@intel.com>
To: linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Cc: dwmw2@infradead.org, baolu.lu@linux.intel.com, joro@8bytes.org,
will@kernel.org, robin.murphy@arm.com, jgg@ziepe.ca,
kevin.tian@intel.com, Zhenzhong Duan <zhenzhong.duan@intel.com>
Subject: [PATCH 1/3] iommupt/vtd: Pass dmar_domain pointer to device_set_dirty_tracking()
Date: Wed, 4 Feb 2026 21:34:02 -0500 [thread overview]
Message-ID: <20260205023405.41583-2-zhenzhong.duan@intel.com> (raw)
In-Reply-To: <20260205023405.41583-1-zhenzhong.duan@intel.com>
Pass dmar_domain pointer to device_set_dirty_tracking() instead of
device list in the domain.
This is a prerequisite patch to support dirty tracking on PASIDs.
No functional changes intended.
Suggested-by: Lu Baolu <baolu.lu@linux.intel.com>
Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
---
drivers/iommu/intel/iommu.c | 21 +++++++++------------
1 file changed, 9 insertions(+), 12 deletions(-)
diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
index 134302fbcd92..acaa6eaf7e2f 100644
--- a/drivers/iommu/intel/iommu.c
+++ b/drivers/iommu/intel/iommu.c
@@ -3687,16 +3687,15 @@ static void *intel_iommu_hw_info(struct device *dev, u32 *length,
return vtd;
}
-/*
- * Set dirty tracking for the device list of a domain. The caller must
- * hold the domain->lock when calling it.
- */
-static int device_set_dirty_tracking(struct list_head *devices, bool enable)
+/* Set dirty tracking for the devices that the domain has been attached. */
+static int device_set_dirty_tracking(struct dmar_domain *domain, bool enable)
{
struct device_domain_info *info;
int ret = 0;
- list_for_each_entry(info, devices, link) {
+ lockdep_assert_held(&domain->lock);
+
+ list_for_each_entry(info, &domain->devices, link) {
ret = intel_pasid_setup_dirty_tracking(info->iommu, info->dev,
IOMMU_NO_PASID, enable);
if (ret)
@@ -3716,7 +3715,7 @@ static int parent_domain_set_dirty_tracking(struct dmar_domain *domain,
spin_lock(&domain->s1_lock);
list_for_each_entry(s1_domain, &domain->s1_domains, s2_link) {
spin_lock_irqsave(&s1_domain->lock, flags);
- ret = device_set_dirty_tracking(&s1_domain->devices, enable);
+ ret = device_set_dirty_tracking(s1_domain, enable);
spin_unlock_irqrestore(&s1_domain->lock, flags);
if (ret)
goto err_unwind;
@@ -3727,8 +3726,7 @@ static int parent_domain_set_dirty_tracking(struct dmar_domain *domain,
err_unwind:
list_for_each_entry(s1_domain, &domain->s1_domains, s2_link) {
spin_lock_irqsave(&s1_domain->lock, flags);
- device_set_dirty_tracking(&s1_domain->devices,
- domain->dirty_tracking);
+ device_set_dirty_tracking(s1_domain, domain->dirty_tracking);
spin_unlock_irqrestore(&s1_domain->lock, flags);
}
spin_unlock(&domain->s1_lock);
@@ -3745,7 +3743,7 @@ static int intel_iommu_set_dirty_tracking(struct iommu_domain *domain,
if (dmar_domain->dirty_tracking == enable)
goto out_unlock;
- ret = device_set_dirty_tracking(&dmar_domain->devices, enable);
+ ret = device_set_dirty_tracking(dmar_domain, enable);
if (ret)
goto err_unwind;
@@ -3762,8 +3760,7 @@ static int intel_iommu_set_dirty_tracking(struct iommu_domain *domain,
return 0;
err_unwind:
- device_set_dirty_tracking(&dmar_domain->devices,
- dmar_domain->dirty_tracking);
+ device_set_dirty_tracking(dmar_domain, dmar_domain->dirty_tracking);
spin_unlock(&dmar_domain->lock);
return ret;
}
--
2.47.3
next prev parent reply other threads:[~2026-02-05 2:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 2:34 [PATCH 0/3] iommupt/vtd: Support dirty tracking on PASID Zhenzhong Duan
2026-02-05 2:34 ` Zhenzhong Duan [this message]
2026-02-05 2:34 ` [PATCH 2/3] " 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 ` [PATCH 0/3] iommupt/vtd: Support " Jason Gunthorpe
2026-02-06 3:44 ` 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=20260205023405.41583-2-zhenzhong.duan@intel.com \
--to=zhenzhong.duan@intel.com \
--cc=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 \
/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