From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: Chao Liu <chao.liu.zevorn@gmail.com>,
Alistair Francis <alistair.francis@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Weiwei Li <liwei1518@gmail.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
Fabiano Rosas <farosas@suse.de>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Tao Tang <tangtao1634@phytium.com.cn>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
hust-os-kernel-patches@googlegroups.com
Subject: Re: [RFC PATCH v1 0/2] tests/qtest: Add RISC-V IOMMU bare-metal test using iommu-testdev
Date: Wed, 28 Jan 2026 11:42:36 -0300 [thread overview]
Message-ID: <97143bc3-b473-4e72-877c-b3bf9a70819d@ventanamicro.com> (raw)
In-Reply-To: <cover.1769600111.git.chao.liu.zevorn@gmail.com>
On 1/28/2026 9:09 AM, Chao Liu wrote:
> Hi,
>
> This patch series adds a bare-metal qtest for the RISC-V IOMMU using the
> iommu-testdev framework. The test exercises address translation paths
> without requiring a full guest OS boot.
>
> Motivation
> ----------
>
> The existing RISC-V IOMMU qtest (riscv-iommu-test.c) focuses on PCI device
> enumeration and register-level validation:
> - PCI configuration space verification (vendor/device ID)
> - Register reset value checks
> - Queue initialization procedures (CQ/FQ/PQ)
>
> However, it does not test the actual address translation functionality.
> This new test fills that gap by using iommu-testdev to trigger DMA
> transactions and validate the IOMMU's translation logic.
>
> Comparison with Existing Test
> -----------------------------
>
> | Feature | riscv-iommu-test.c | iommu-riscv-test.c (new) |
> |-----------------------|--------------------|--------------------------|
> | PCI config | Yes | No |
> | Register reset | Yes | No |
> | Queue init | Yes | Yes (via helper) |
> | Bare translation | No | Yes |
> | S-stage (SV39) | No | Yes |
> | G-stage (SV39x4) | No | Yes |
> | Nested translation | No | Yes |
> | DMA verification | No | Yes |
> | Uses iommu-testdev | No | Yes |
>
> The new test provides:
> - Device context (DC) configuration and validation
> - SV39 page table walks for S-stage translation
> - SV39x4 page table walks for G-stage translation
> - Nested translation combining both stages
> - FCTL register constraint validation
> - End-to-end DMA verification
I have a customized environment just to test IOMMU stuff (boot an Ubuntu
emulated RISC-V host, see if the riscv-iommu works with a PCI net card).
And even then this kind of test is limited by the amount of stuff the
current Linux driver is capable of doing. And yet I have to at least
give it a try with every IOMMU change/fix sent ... This new test will
give us additional coverage that neither the existing test nor my manual
testing can provide.
Thank you for the time and effort putting into this work. This is really
remarkable.
>
> Note: The current implementation only supports SV39/SV39x4. Support for
> SV48/SV48x4/SV57/SV57x4 can be added in future patches.
>
> Testing
> -------
>
> QTEST_QEMU_BINARY=./build/qemu-system-riscv64 \
> ./build/tests/qtest/iommu-riscv-test --tap -k
>
> Question for Maintainers
> ------------------------
>
> The existing riscv-iommu-test.c and the new iommu-riscv-test.c serve
> complementary purposes. Would it be beneficial to merge these two tests
> into a single source file for easier maintenance? This would consolidate
> all RISC-V IOMMU testing in one place while preserving both the
> register-level and translation-level test coverage.
I'll give my non-maintainer opinion because I happen to be the author of
riscv-iommu-test.c: as long as we preserve the existing tests for both
files I'm ok with it. Maybe there are code re-use opportunities that
will be exposed when merging the 2 together.
But I believe this can wait. We should push this upstream first (or at
least get it queued into the maintainer's tree).
Thanks,
Daniel
>
> Thanks,
> Chao
>
> Chao Liu (2):
> tests/qtest/libqos: Add RISC-V IOMMU helper library
> tests/qtest: Add RISC-V IOMMU bare-metal test
>
> MAINTAINERS | 2 +
> tests/qtest/iommu-riscv-test.c | 279 +++++++++++++++++++
> tests/qtest/libqos/meson.build | 2 +-
> tests/qtest/libqos/qos-riscv-iommu.c | 400 +++++++++++++++++++++++++++
> tests/qtest/libqos/qos-riscv-iommu.h | 172 ++++++++++++
> tests/qtest/meson.build | 5 +-
> 6 files changed, 858 insertions(+), 2 deletions(-)
> create mode 100644 tests/qtest/iommu-riscv-test.c
> create mode 100644 tests/qtest/libqos/qos-riscv-iommu.c
> create mode 100644 tests/qtest/libqos/qos-riscv-iommu.h
>
> --
> 2.52.0
>
next prev parent reply other threads:[~2026-01-28 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 12:09 [RFC PATCH v1 0/2] tests/qtest: Add RISC-V IOMMU bare-metal test using iommu-testdev Chao Liu
2026-01-28 12:09 ` [RFC PATCH v1 1/2] tests/qtest/libqos: Add RISC-V IOMMU helper library Chao Liu
2026-01-28 14:30 ` Daniel Henrique Barboza
2026-01-28 15:23 ` Tao Tang
2026-01-28 15:45 ` Chao Liu
2026-01-29 1:59 ` Tao Tang
2026-01-28 12:09 ` [RFC PATCH v1 2/2] tests/qtest: Add RISC-V IOMMU bare-metal test Chao Liu
2026-01-28 14:30 ` Daniel Henrique Barboza
2026-01-28 15:36 ` Tao Tang
2026-01-28 16:17 ` Chao Liu
2026-01-28 14:42 ` Daniel Henrique Barboza [this message]
2026-01-28 16:25 ` [RFC PATCH v1 0/2] tests/qtest: Add RISC-V IOMMU bare-metal test using iommu-testdev Chao Liu
2026-01-28 14:54 ` Tao Tang
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=97143bc3-b473-4e72-877c-b3bf9a70819d@ventanamicro.com \
--to=dbarboza@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=chao.liu.zevorn@gmail.com \
--cc=farosas@suse.de \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=liwei1518@gmail.com \
--cc=lvivier@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=tangtao1634@phytium.com.cn \
--cc=zhiwei_liu@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.