From: Thomas Huth <thuth@redhat.com>
To: Ivan Klokov <ivan.klokov@syntacore.com>, qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, palmer@dabbelt.com, bmeng.cn@gmail.com,
liwei1518@gmail.com, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com, lvivier@redhat.com,
pbonzini@redhat.com
Subject: Re: [RFC PATCH v3 1/2] target/riscv: Add RISC-V CSR qtest support
Date: Wed, 26 Jun 2024 09:56:10 +0200 [thread overview]
Message-ID: <c9d65417-0235-4452-8dd5-a756dd2ae9e9@redhat.com> (raw)
In-Reply-To: <20240625153555.104088-2-ivan.klokov@syntacore.com>
On 25/06/2024 17.35, Ivan Klokov wrote:
> The RISC-V architecture supports the creation of custom
> CSR-mapped devices. It would be convenient to test them in the same way
> as MMIO-mapped devices. To do this, a new call has been added
> to read/write CSR registers.
>
> Signed-off-by: Ivan Klokov <ivan.klokov@syntacore.com>
> ---
> target/riscv/cpu.c | 14 +++++++++++
> target/riscv/cpu.h | 3 +++
> target/riscv/csr.c | 53 +++++++++++++++++++++++++++++++++++++++++-
> tests/qtest/libqtest.c | 27 +++++++++++++++++++++
> tests/qtest/libqtest.h | 14 +++++++++++
> 5 files changed, 110 insertions(+), 1 deletion(-)
>
> diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
> index 69a08e8c2c..55cc01bfb3 100644
> --- a/target/riscv/cpu.c
> +++ b/target/riscv/cpu.c
> @@ -1148,7 +1148,17 @@ void riscv_cpu_finalize_features(RISCVCPU *cpu, Error **errp)
> }
> }
> }
> +#ifndef CONFIG_USER_ONLY
> +static void riscv_cpu_register_csr_qtest_callback(void)
> +{
> + static gsize reinit_done;
> + if (g_once_init_enter(&reinit_done)) {
> + qtest_set_command_cb(csr_qtest_callback);
>
> + g_once_init_leave(&reinit_done, 1);
> + }
> +}
> +#endif
> static void riscv_cpu_realize(DeviceState *dev, Error **errp)
Could you please add an empty line before the #ifndef and after the #endif
line? Thanks!
> diff --git a/tests/qtest/libqtest.c b/tests/qtest/libqtest.c
> index c7f6897d78..f8c3ff15a9 100644
> --- a/tests/qtest/libqtest.c
> +++ b/tests/qtest/libqtest.c
> @@ -1205,6 +1205,33 @@ uint64_t qtest_rtas_call(QTestState *s, const char *name,
> return 0;
> }
>
> +static void qtest_rsp_csr(QTestState *s, uint64_t *val)
> +{
> + gchar **args;
> + uint64_t ret;
> + int rc;
> +
> + args = qtest_rsp_args(s, 3);
> +
> + rc = qemu_strtou64(args[1], NULL, 16, &ret);
> + g_assert(rc == 0);
> + rc = qemu_strtou64(args[2], NULL, 16, val);
> + g_assert(rc == 0);
> +
> + g_strfreev(args);
> +}
> +
> +uint64_t qtest_csr_call(QTestState *s, const char *name,
> + uint64_t cpu, int csr,
> + uint64_t *val)
> +{
> + qtest_sendf(s, "csr %s 0x%"PRIx64" %d 0x%"PRIx64"\n",
> + name, cpu, csr, *val);
> +
> + qtest_rsp_csr(s, val);
> + return 0;
> +}
> +
> void qtest_add_func(const char *str, void (*fn)(void))
> {
> gchar *path = g_strdup_printf("/%s/%s", qtest_get_arch(), str);
> diff --git a/tests/qtest/libqtest.h b/tests/qtest/libqtest.h
> index c261b7e0b3..53cd8fe9f0 100644
> --- a/tests/qtest/libqtest.h
> +++ b/tests/qtest/libqtest.h
> @@ -577,6 +577,20 @@ uint64_t qtest_rtas_call(QTestState *s, const char *name,
> uint32_t nargs, uint64_t args,
> uint32_t nret, uint64_t ret);
>
> +/**
> + * qtest_csr_call:
> + * @s: #QTestState instance to operate on.
> + * @name: name of the command to call.
> + * @cpu: hart number.
> + * @csr: CSR number.
> + * @val: Value for reading/writing.
> + *
> + * Call an CSR function
Maybe mention RISC-V here in the comment?
> + */
> +uint64_t qtest_csr_call(QTestState *s, const char *name,
> + uint64_t cpu, int csr,
> + unsigned long *val);
> +
> /**
> * qtest_bufread:
> * @s: #QTestState instance to operate on.
For the tests/qtest part:
Acked-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2024-06-26 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 15:35 [RFC PATCH v3 0/2] Support RISC-V CSR read/write in Qtest environment Ivan Klokov
2024-06-25 15:35 ` [RFC PATCH v3 1/2] target/riscv: Add RISC-V CSR qtest support Ivan Klokov
2024-06-26 7:56 ` Thomas Huth [this message]
2024-06-25 15:35 ` [RFC PATCH v3 2/2] tests/qtest: QTest example for RISC-V CSR register Ivan Klokov
2024-06-26 7:57 ` Thomas Huth
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=c9d65417-0235-4452-8dd5-a756dd2ae9e9@redhat.com \
--to=thuth@redhat.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).