From: Jason Gunthorpe <jgg@nvidia.com>
To: Tomasz Jeznach <tjeznach@rivosinc.com>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
Albert Ou <aou@eecs.berkeley.edu>,
iommu@lists.linux.dev, Joerg Roedel <joro@8bytes.org>,
linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>,
lihangjing@bytedance.com, Xu Lu <luxu.kernel@bytedance.com>,
patches@lists.linux.dev, Paul Walmsley <pjw@kernel.org>,
Vincent Chen <vincent.chen@sifive.com>,
xieyongji@bytedance.com, tjeznach@fb.com
Subject: Re: [PATCH v3 0/5] Convert riscv to use the generic iommu page table
Date: Mon, 2 Feb 2026 11:29:53 -0400 [thread overview]
Message-ID: <20260202152953.GQ2223369@nvidia.com> (raw)
In-Reply-To: <CAH2o1u5-VuEUJp2MNb41uxQJk=SR1uZbQkiqQWoLBj-+GXTVkw@mail.gmail.com>
On Sun, Feb 01, 2026 at 10:01:55PM -0800, Tomasz Jeznach wrote:
> All tested, run with NVMe / NICs. No issues. Some minor performance
> changes (positive or negative depending on the workload). No issues.
> Open issue on QEMU RISC-V IOMMU model - SVNAPOT support is missing.
> I've made a local change to fix it, and will post it soon.
Thanks! I was wondering if the failure you reported was SVNAPOT
related, good job finding that qemu is not following the HW spec..
Jason
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-02-02 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 0:00 [PATCH v3 0/5] Convert riscv to use the generic iommu page table Jason Gunthorpe
2026-01-31 0:00 ` [PATCH v3 1/5] iommupt: Add the RISC-V page table format Jason Gunthorpe
2026-01-31 0:00 ` [PATCH v3 2/5] iommu/riscv: Disable SADE Jason Gunthorpe
2026-01-31 0:00 ` [PATCH v3 3/5] iommu/riscv: Use the generic iommu page table Jason Gunthorpe
2026-01-31 0:00 ` [PATCH v3 4/5] iommu/riscv: Enable SVNAPOT support for contiguous ptes Jason Gunthorpe
2026-01-31 0:00 ` [PATCH v3 5/5] iommu/riscv: Allow RISC_VIOMMU to COMPILE_TEST Jason Gunthorpe
2026-02-02 6:01 ` [PATCH v3 0/5] Convert riscv to use the generic iommu page table Tomasz Jeznach
2026-02-02 15:29 ` Jason Gunthorpe [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=20260202152953.GQ2223369@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=lihangjing@bytedance.com \
--cc=linux-riscv@lists.infradead.org \
--cc=luxu.kernel@bytedance.com \
--cc=palmer@dabbelt.com \
--cc=patches@lists.linux.dev \
--cc=pjw@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tjeznach@fb.com \
--cc=tjeznach@rivosinc.com \
--cc=vincent.chen@sifive.com \
--cc=will@kernel.org \
--cc=xieyongji@bytedance.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