From: "Nutty.Liu" <nutty.liu@hotmail.com>
To: fangyu.yu@linux.alibaba.com, tomasz.jeznach@linux.dev,
joro@8bytes.org, will@kernel.org, robin.murphy@arm.com,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, baolu.lu@linux.intel.com, jroedel@suse.de,
zong.li@sifive.com, andrew.jones@linux.dev, anup@brainfault.org,
jgg@nvidia.com, jgg@ziepe.ca, kevin.tian@intel.com,
atish.patra@linux.dev, skhawaja@google.com, vasant.hegde@amd.com,
joerg.roedel@amd.com, tanchi25@mails.ucas.ac.cn,
gong.shuai@sanechips.com.cn
Cc: guoren@kernel.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
kvm-riscv@lists.infradead.org
Subject: Re: [RFC PATCH v5 09/10] iommu/riscv: Add dirty tracking support for second-stage domains
Date: Tue, 27 Oct 2026 19:52:46 +0800 [thread overview]
Message-ID: <TYZPR04MB749109BCE4854B21EC908E3AF3602@TYZPR04MB7491.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <20261020094106.92722-10-fangyu.yu@linux.alibaba.com>
On 10/20/2026 5:41 PM, fangyu.yu@linux.alibaba.com wrote:
> From: Fangyu Yu <fangyu.yu@linux.alibaba.com>
>
> Add hardware dirty tracking support for second-stage (iohgatp) domains
> used in KVM VFIO device pass-through.
>
> The RISC-V IOMMU can automatically set the dirty bit in PTEs on write
> access when DC.tc.GADE is set and the hardware has AMO_HWAD capability.
> Wire this up to the iommufd dirty tracking interface:
>
> - riscv_iommu_set_dirty_tracking(): Always enabled dirty tracking for
> second-stage domain.
>
> - riscv_iommu_dirty_ops: Exposes set_dirty_tracking and the generic
> page-table read_and_clear_dirty via IOMMU_PT_DIRTY_OPS(riscv_64).
>
> - domain_alloc_paging_flags: Assigns dirty_ops to second-stage domains
> when AMO_HWAD is advertised in hardware capabilities.
>
> - riscv_iommu_capable: Reports IOMMU_CAP_DIRTY_TRACKING when
> AMO_HWAD is present.
>
> Signed-off-by: Fangyu Yu <fangyu.yu@linux.alibaba.com>
Reviewed-by: Nutty Liu <nutty.liu@hotmail.com>
Thanks,
Nutty
> ---
> drivers/iommu/riscv/iommu.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/drivers/iommu/riscv/iommu.c b/drivers/iommu/riscv/iommu.c
> index 9310b818c038..e3791e912af3 100644
> --- a/drivers/iommu/riscv/iommu.c
> +++ b/drivers/iommu/riscv/iommu.c
> @@ -1376,6 +1376,21 @@ static int riscv_iommu_attach_paging_domain(struct iommu_domain *iommu_domain,
> return 0;
> }
>
> +static int riscv_iommu_set_dirty_tracking(struct iommu_domain *iommu_domain,
> + bool enable)
> +{
> + /*
> + * Always enabled and the dirty bitmap is cleared prior to
> + * set_dirty_tracking().
> + */
> + return 0;
> +}
> +
> +static const struct iommu_dirty_ops riscv_iommu_dirty_ops = {
> + IOMMU_PT_DIRTY_OPS(riscv_64),
> + .set_dirty_tracking = riscv_iommu_set_dirty_tracking,
> +};
> +
> static const struct iommu_domain_ops riscv_iommu_paging_domain_ops = {
> IOMMU_PT_DOMAIN_OPS(riscv_64),
> .attach_dev = riscv_iommu_attach_paging_domain,
> @@ -1466,6 +1481,8 @@ riscv_iommu_domain_alloc_paging_flags(struct device *dev, u32 flags,
> goto err_free;
> }
> cfg.common.features |= BIT(PT_FEAT_RISCV_S2);
> + if (iommu->caps & RISCV_IOMMU_CAPABILITIES_AMO_HWAD)
> + domain->domain.dirty_ops = &riscv_iommu_dirty_ops;
> break;
> default:
> ret = -EOPNOTSUPP;
> @@ -1541,9 +1558,13 @@ static struct iommu_group *riscv_iommu_device_group(struct device *dev)
>
> static bool riscv_iommu_capable(struct device *dev, enum iommu_cap cap)
> {
> + struct riscv_iommu_device *iommu = dev_to_iommu(dev);
> +
> switch (cap) {
> case IOMMU_CAP_CACHE_COHERENCY:
> return true;
> + case IOMMU_CAP_DIRTY_TRACKING:
> + return !!(iommu->caps & RISCV_IOMMU_CAPABILITIES_AMO_HWAD);
> default:
> return false;
> }
next prev parent reply other threads:[~2026-10-27 11:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 9:40 [RFC PATCH v5 00/10] iommu/riscv: Add hardware dirty tracking " fangyu.yu
2026-10-20 9:40 ` [RFC PATCH v5 01/10] iommupt: Add RISC-V Second-stage (iohgatp) page table support fangyu.yu
2026-10-28 15:28 ` Jason Gunthorpe
2026-10-20 9:40 ` [RFC PATCH v5 02/10] iommupt: Add RISC-V dirty tracking PTE ops fangyu.yu
2026-10-28 15:28 ` Jason Gunthorpe
2026-10-20 9:40 ` [RFC PATCH v5 03/10] iommu/riscv: report iommu capabilities fangyu.yu
2026-10-28 15:28 ` Jason Gunthorpe
2026-10-30 2:31 ` Gong Shuai
2026-10-30 2:49 ` fangyu.yu
2026-10-20 9:41 ` [RFC PATCH v5 04/10] iommu/riscv: use data structure instead of individual values fangyu.yu
2026-10-28 15:28 ` Jason Gunthorpe
2026-10-20 9:41 ` [RFC PATCH v5 05/10] iommu/riscv: support GSCID and GVMA invalidation command fangyu.yu
2026-10-20 9:41 ` [RFC PATCH v5 06/10] RISC-V: KVM: Enable KVM_VFIO interfaces on RISC-V arch fangyu.yu
2026-10-20 9:41 ` [RFC PATCH v5 07/10] iommu/riscv: Add domain_alloc_paging_flags for second-stage domain fangyu.yu
2026-10-28 15:28 ` Jason Gunthorpe
2026-10-29 1:41 ` fangyu.yu
2026-10-20 9:41 ` [RFC PATCH v5 08/10] iommu/riscv: Pre-enable GADE for second-stage domains fangyu.yu
2026-10-27 11:43 ` Nutty.Liu
2026-10-20 9:41 ` [RFC PATCH v5 09/10] iommu/riscv: Add dirty tracking support " fangyu.yu
2026-10-27 11:52 ` Nutty.Liu [this message]
2026-10-20 9:41 ` [RFC PATCH v5 10/10] iommu/riscv: Add IOTINVAL.GVMA invalidations fangyu.yu
2026-10-27 11:46 ` Nutty.Liu
2026-10-28 15:28 ` [RFC PATCH v5 00/10] iommu/riscv: Add hardware dirty tracking for second-stage domains Jason Gunthorpe
2026-10-29 1:52 ` fangyu.yu
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=TYZPR04MB749109BCE4854B21EC908E3AF3602@TYZPR04MB7491.apcprd04.prod.outlook.com \
--to=nutty.liu@hotmail.com \
--cc=alex@ghiti.fr \
--cc=andrew.jones@linux.dev \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=baolu.lu@linux.intel.com \
--cc=fangyu.yu@linux.alibaba.com \
--cc=gong.shuai@sanechips.com.cn \
--cc=guoren@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=kevin.tian@intel.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robin.murphy@arm.com \
--cc=skhawaja@google.com \
--cc=tanchi25@mails.ucas.ac.cn \
--cc=tomasz.jeznach@linux.dev \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
--cc=zong.li@sifive.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®