From: Fabiano Rosas <farosas@suse.de>
To: Ivan Klokov <ivan.klokov@syntacore.com>, qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, palmer@dabbelt.com,
alistair.francis@wdc.com, bmeng.cn@gmail.com,
liwei1518@gmail.com, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com, lvivier@redhat.com,
pbonzini@redhat.com, Ivan Klokov <ivan.klokov@syntacore.com>
Subject: Re: [PATCH v8 0/2] Support RISC-V CSR read/write in Qtest environment
Date: Thu, 02 Jan 2025 12:47:38 -0300 [thread overview]
Message-ID: <87ttah8bfp.fsf@suse.de> (raw)
In-Reply-To: <20241225123718.45991-1-ivan.klokov@syntacore.com>
Ivan Klokov <ivan.klokov@syntacore.com> writes:
> These patches add functionality for unit testing RISC-V-specific registers.
> The first patch adds a Qtest backend, and the second implements a simple test.
>
> ---
> v8:
> - Delete RFC label.
> v7:
> - Fix build errors, add Reviewed-by, Acked-by.
> ---
>
> Ivan Klokov (2):
> target/riscv: Add RISC-V CSR qtest support
> tests/qtest: QTest example for RISC-V CSR register
>
> hw/riscv/riscv_hart.c | 56 ++++++++++++++++++++++++++++++++++++
> tests/qtest/libqtest.c | 27 +++++++++++++++++
> tests/qtest/libqtest.h | 14 +++++++++
> tests/qtest/meson.build | 2 +-
> tests/qtest/riscv-csr-test.c | 56 ++++++++++++++++++++++++++++++++++++
> 5 files changed, 154 insertions(+), 1 deletion(-)
> create mode 100644 tests/qtest/riscv-csr-test.c
Hi, there are some CI jobs failing with this series, could you take a
look?
https://gitlab.com/farosas/qemu/-/pipelines/1609210965
prev parent reply other threads:[~2025-01-02 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 12:37 [PATCH v8 0/2] Support RISC-V CSR read/write in Qtest environment Ivan Klokov
2024-12-25 12:37 ` [PATCH v8 1/2] target/riscv: Add RISC-V CSR qtest support Ivan Klokov
2025-01-06 1:32 ` Alistair Francis
2024-12-25 12:37 ` [PATCH v8 2/2] tests/qtest: QTest example for RISC-V CSR register Ivan Klokov
2025-01-06 1:34 ` Alistair Francis
2025-01-02 15:47 ` Fabiano Rosas [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=87ttah8bfp.fsf@suse.de \
--to=farosas@suse.de \
--cc=alistair.francis@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=ivan.klokov@syntacore.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).