From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Anton Johansson <anjo@rev.ng>
Cc: qemu-devel@nongnu.org, pierrick.bouvier@linaro.org,
alistair.francis@wdc.com, richard.henderson@linaro.org,
palmer@dabbelt.com
Subject: Re: [PATCH v2 2/3] hw/riscv: Replace target_ulong uses
Date: Thu, 30 Oct 2025 13:52:38 +0100 [thread overview]
Message-ID: <a3d39ae0-9c0d-4822-9dfc-9ddcf79f63e5@linaro.org> (raw)
In-Reply-To: <2y2ism54afg4ke5oeykqin5oy2kn4lb4gcd7fidgrmlwwbe6df@5h4wudvpyll4>
On 30/10/25 13:32, Anton Johansson wrote:
> On 29/10/25, Philippe Mathieu-Daudé wrote:
>> On 27/10/25 13:35, Anton Johansson wrote:
>>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>>> Signed-off-by: Anton Johansson <anjo@rev.ng>
>>> ---
>>> hw/riscv/riscv-iommu.c | 6 ++++--
>>> hw/riscv/riscv_hart.c | 2 +-
>>> 2 files changed, 5 insertions(+), 3 deletions(-)
>>> diff --git a/hw/riscv/riscv_hart.c b/hw/riscv/riscv_hart.c
>>> index c7e98a4308..65d2c92018 100644
>>> --- a/hw/riscv/riscv_hart.c
>>> +++ b/hw/riscv/riscv_hart.c
>>> @@ -93,7 +93,7 @@ static bool csr_qtest_callback(CharBackend *chr, gchar **words)
>>> g_assert(rc == 0);
>>> csr_call(words[1], cpu, csr, &val);
>>> - qtest_sendf(chr, "OK 0 "TARGET_FMT_lx"\n", (target_ulong)val);
>>> + qtest_sendf(chr, "OK 0 %"PRIx64"\n", val);
>>> return true;
>>> }
>>>
>>
>> What about csr_call()?
>
> csr_call() is handled in the other series making cpu.h target agnostic,
> there we expose 64 bit variants of reading/writing CSRs which are then
> used by csr_call().
Ah, good then, thanks!
next prev parent reply other threads:[~2025-10-30 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 12:35 [PATCH v2 0/3] single-binary: Prepare hw/riscv for single compilation Anton Johansson via
2025-10-27 12:35 ` [PATCH v2 1/3] hw/riscv: Use generic hwaddr for firmware addressses Anton Johansson via
2025-10-27 12:39 ` Philippe Mathieu-Daudé
2025-10-27 18:13 ` Anton Johansson via
2025-10-27 12:35 ` [PATCH v2 2/3] hw/riscv: Replace target_ulong uses Anton Johansson via
2025-10-29 18:01 ` Philippe Mathieu-Daudé
2025-10-30 12:32 ` Anton Johansson via
2025-10-30 12:52 ` Philippe Mathieu-Daudé [this message]
2025-10-30 4:10 ` Alistair Francis
2025-10-27 12:35 ` [PATCH v2 3/3] hw/riscv: Widen OpenSBI dynamic info struct Anton Johansson via
2025-10-27 12:42 ` Philippe Mathieu-Daudé
2025-10-28 7:25 ` [PATCH v2 0/3] single-binary: Prepare hw/riscv for single compilation Philippe Mathieu-Daudé
2025-10-29 21:56 ` Philippe Mathieu-Daudé
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=a3d39ae0-9c0d-4822-9dfc-9ddcf79f63e5@linaro.org \
--to=philmd@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=anjo@rev.ng \
--cc=palmer@dabbelt.com \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).