From: Vivian Wang <wangruikang@iscas.ac.cn>
To: Tomasz Jeznach <tjeznach@rivosinc.com>
Cc: Anup Patel <apatel@ventanamicro.com>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>,
linux@rivosinc.com, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Sebastien Boeuf <seb@rivosinc.com>,
iommu@lists.linux.dev, Palmer Dabbelt <palmer@dabbelt.com>,
Nick Kossifidis <mick@ics.forth.gr>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-riscv@lists.infradead.org, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v10 0/7] Linux RISC-V IOMMU Support
Date: Wed, 5 Nov 2025 18:08:53 +0800 [thread overview]
Message-ID: <0a0b8b94-ad94-46ea-ac0d-cbf35dec0f50@iscas.ac.cn> (raw)
In-Reply-To: <cover.1729059707.git.tjeznach@rivosinc.com>
Hi Tomasz,
On 10/16/24 14:52, Tomasz Jeznach wrote:
> This patch series introduces support for RISC-V IOMMU architected
> hardware into the Linux kernel.
>
> [...]
>
> Follow-up patch series providing MSI interrupt remapping, complete ATS/PRI/SVA
> and VFIO/IOMMUFD support are available at the GitHub [2], and has been tested
> with published QEMU RISC-V IOMMU device model [3].
I'm currently looking into building drivers for some "accelerator" style
devices, and I'm trying to figure out the current situation of drivers
for the more advanced IOMMU features, specifically the ATS/PRI/SVA combo.
I see that the GitHub branch has been rebased in May to 6.15, but
seemingly hasn't been touched since. Is this still the latest version of
these patches? Aside from other IOMMU subsystem-wide changes since
v6.15, is there any other code/information that I should take into account?
This isn't super urgent or anything, but I'm pretty new to this, and
given that a year has passed since this series has been merged, I'm not
sure if there's some other development I've missed.
Thanks for your help.
Vivian "dramforever" Wang
prev parent reply other threads:[~2025-11-05 10:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 6:52 Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 1/7] dt-bindings: iommu: riscv: Add bindings for RISC-V IOMMU Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 2/7] iommu/riscv: Add RISC-V IOMMU platform device driver Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 3/7] iommu/riscv: Add RISC-V IOMMU PCIe " Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 4/7] iommu/riscv: Enable IOMMU registration and device probe Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 5/7] iommu/riscv: Device directory management Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 6/7] iommu/riscv: Command and fault queue support Tomasz Jeznach
2024-10-16 6:52 ` [PATCH v10 7/7] iommu/riscv: Paging domain support Tomasz Jeznach
2024-10-16 23:58 ` [PATCH v10 0/7] Linux RISC-V IOMMU Support Palmer Dabbelt
2024-10-24 13:09 ` Will Deacon
2024-10-29 8:42 ` Joerg Roedel
2025-11-05 10:08 ` Vivian Wang [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=0a0b8b94-ad94-46ea-ac0d-cbf35dec0f50@iscas.ac.cn \
--to=wangruikang@iscas.ac.cn \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rivosinc.com \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=seb@rivosinc.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
all inboxes | Powered by JetHome®