mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: fangyu.yu@linux.alibaba.com
To: jgg@nvidia.com
Cc: alex@ghiti.fr, andrew.jones@linux.dev, anup@brainfault.org,
	aou@eecs.berkeley.edu, atish.patra@linux.dev,
	baolu.lu@linux.intel.com, fangyu.yu@linux.alibaba.com,
	gong.shuai@sanechips.com.cn, guoren@kernel.org,
	iommu@lists.linux.dev, jgg@ziepe.ca, joerg.roedel@amd.com,
	joro@8bytes.org, jroedel@suse.de, kevin.tian@intel.com,
	kvm-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	pjw@kernel.org, robin.murphy@arm.com, skhawaja@google.com,
	tanchi25@mails.ucas.ac.cn, tomasz.jeznach@linux.dev,
	vasant.hegde@amd.com, will@kernel.org, zong.li@sifive.com
Subject: Re: [RFC PATCH v5 00/10] iommu/riscv: Add hardware dirty tracking for second-stage domains
Date: Thu, 29 Oct 2026 09:52:07 +0800	[thread overview]
Message-ID: <20261029015207.82522-1-fangyu.yu@linux.alibaba.com> (raw)
In-Reply-To: <179320128818.2412245.14186677086155168748.b4-review@b4>

>> From: Fangyu Yu <fangyu.yu@linux.alibaba.com>
>>
>> The RISC-V IOMMU architecture defines an AMO_HWAD capability (Hardware
>> Access/Dirty update) that allows the IOMMU to atomically set the A/D bits
>> in second-stage PTEs on DMA access.  When DC.tc.GADE is asserted, the IOMMU
>> autonomously sets D on the first write to a page mapped by an iohgatp
>> domain.  This series wires that capability up to the iommufd dirty-tracking
>> interface (IOMMU_HWPT_SET_DIRTY_TRACKING / IOMMU_HWPT_GET_DIRTY_BITMAP) and
>> reports IOMMU_CAP_DIRTY_TRACKING.
>
>These patches don't apply, so sashiko couldn't run:
>
>https://sashiko.dev/#/patchset/20261020094106.92722-1-fangyu.yu%40linux.alibaba.com
>
>> [ ... 86 lines skipped ... ]
>> [1] https://lore.kernel.org/linux-iommu/1-v2-563ee63886f0+1209-iommupt_armv8_jgg@nvidia.com/
>> [2] https://lore.kernel.org/linux-iommu/20260818092444.42755-1-andrew.jones@oss.qualcomm.com/
>
>Because of these extra patches I suppose.
>
>Please figure out how to fix this before you send it again..
>
>Also no base-commit trailer which helps sashiko apply them.
>

Sure, I'll fix the apply issues and add a base-commit trailer in the
next version.

Thanks,
Fangyu

>--
>Jason

      reply	other threads:[~2026-10-29  1:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20  9:40 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-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
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 [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=20261029015207.82522-1-fangyu.yu@linux.alibaba.com \
    --to=fangyu.yu@linux.alibaba.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=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®