From: patchwork-bot+linux-riscv@kernel.org
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-riscv@lists.infradead.org, alex@ghiti.fr,
aou@eecs.berkeley.edu, iommu@lists.linux.dev, joro@8bytes.org,
palmer@dabbelt.com, pjw@kernel.org, robin.murphy@arm.com,
tjeznach@rivosinc.com, will@kernel.org,
andrew.jones@oss.qualcomm.com, fangyu.yu@linux.alibaba.com,
patches@lists.linux.dev
Subject: Re: [PATCH v2 0/8] Support non-leaf and range invalidation features in RISC-V
Date: Fri, 26 Jun 2026 08:20:51 +0000 [thread overview]
Message-ID: <178246205139.3816447.9006141630589978031.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <0-v2-b5156f657dc1+25f-iommu_riscv_inv_jgg@nvidia.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Joerg Roedel <joerg.roedel@amd.com>:
On Fri, 8 May 2026 11:52:59 -0300 you wrote:
> This is part of the patch pile to get SMMUv3 moved to iommupt. From
> that perspective it introduces the PT_FEAT_DETAILED_GATHER which will
> be used by both RISC-V and SMMUv3 to generate optimized invalidation
> commands.
>
> I don't have any RISC-V anything so this needs to be tested by someone who
> does.
>
> [...]
Here is the summary with links:
- [v2,1/8] iommu: Split the kdoc comment for struct iommu_iotlb_gather
https://git.kernel.org/riscv/c/74c9d82c7e3f
- [v2,2/8] iommupt: Add struct iommupt_pending_gather
https://git.kernel.org/riscv/c/f0e4b7f5f875
- [v2,3/8] iommupt: Add PT_FEAT_DETAILED_GATHER
https://git.kernel.org/riscv/c/89792629d4b2
- [v2,4/8] iommu/riscv: Enable PT_FEAT_DETAILED_GATHER and pass gather to iotlb_inval
(no matching commit)
- [v2,5/8] iommu/riscv: Compute best stride for single invalidation
https://git.kernel.org/riscv/c/bb62adcf4513
- [v2,6/8] iommu/riscv: Add RISCV_IOMMU_CAPABILITIES_NL
https://git.kernel.org/riscv/c/e4084c6bbb42
- [v2,7/8] iommu/riscv: Include the dword number in RISCV_IOMMU_CMD macros
https://git.kernel.org/riscv/c/835d06ee7ef0
- [v2,8/8] iommu/riscv: Add NAPOT range invalidation support
https://git.kernel.org/riscv/c/082ad5ed0785
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-06-26 8:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 14:52 [PATCH v2 0/8] Support non-leaf and range invalidation features in RISC-V Jason Gunthorpe
2026-05-08 14:53 ` [PATCH v2 1/8] iommu: Split the kdoc comment for struct iommu_iotlb_gather Jason Gunthorpe
2026-05-08 20:24 ` Pranjal Shrivastava
2026-05-08 14:53 ` [PATCH v2 2/8] iommupt: Add struct iommupt_pending_gather Jason Gunthorpe
2026-05-08 20:26 ` Pranjal Shrivastava
2026-05-08 14:53 ` [PATCH v2 3/8] iommupt: Add PT_FEAT_DETAILED_GATHER Jason Gunthorpe
2026-05-08 20:35 ` Pranjal Shrivastava
2026-05-08 14:53 ` [PATCH v2 4/8] iommu/riscv: Enable PT_FEAT_DETAILED_GATHER and pass gather to iotlb_inval Jason Gunthorpe
2026-05-08 14:53 ` [PATCH v2 5/8] iommu/riscv: Compute best stride for single invalidation Jason Gunthorpe
2026-05-08 14:53 ` [PATCH v2 6/8] iommu/riscv: Add RISCV_IOMMU_CAPABILITIES_NL Jason Gunthorpe
2026-05-08 14:53 ` [PATCH v2 7/8] iommu/riscv: Include the dword number in RISCV_IOMMU_CMD macros Jason Gunthorpe
2026-05-14 20:04 ` Tomasz Jeznach
2026-05-08 14:53 ` [PATCH v2 8/8] iommu/riscv: Add NAPOT range invalidation support Jason Gunthorpe
2026-05-09 20:39 ` [PATCH v2 0/8] Support non-leaf and range invalidation features in RISC-V Andrew Jones
2026-06-26 8:20 ` patchwork-bot+linux-riscv [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=178246205139.3816447.9006141630589978031.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=andrew.jones@oss.qualcomm.com \
--cc=aou@eecs.berkeley.edu \
--cc=fangyu.yu@linux.alibaba.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=patches@lists.linux.dev \
--cc=pjw@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tjeznach@rivosinc.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