From: Alistair Francis <alistair23@gmail.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, bmeng@tinylab.org,
liwei1518@gmail.com, zhiwei_liu@linux.alibaba.com,
palmer@rivosinc.com, ajones@ventanamicro.com
Subject: Re: [PATCH for-9.0] target/riscv/cpu.c: fix machine IDs getters
Date: Mon, 18 Dec 2023 09:31:01 +1000 [thread overview]
Message-ID: <CAKmqyKOkXe-Jxn7WGSCom_4SK9oMF41=CYO5mgBdsMCC9hxmxQ@mail.gmail.com> (raw)
In-Reply-To: <20231211170732.2541368-1-dbarboza@ventanamicro.com>
On Tue, Dec 12, 2023 at 3:08 AM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> mvendorid is an uint32 property, mimpid/marchid are uint64 properties.
> But their getters are returning bools. The reason this went under the
> radar for this long is because we have no code using the getters.
>
> The problem can be seem via the 'qom-get' API though. Launching QEMU
> with the 'veyron-v1' CPU, a model with:
>
> VEYRON_V1_MVENDORID: 0x61f (1567)
> VEYRON_V1_MIMPID: 0x111 (273)
> VEYRON_V1_MARCHID: 0x8000000000010000 (9223372036854841344)
>
> This is what the API returns when retrieving these properties:
>
> (qemu) qom-get /machine/soc0/harts[0] mvendorid
> true
> (qemu) qom-get /machine/soc0/harts[0] mimpid
> true
> (qemu) qom-get /machine/soc0/harts[0] marchid
> true
>
> After this patch:
>
> (qemu) qom-get /machine/soc0/harts[0] mvendorid
> 1567
> (qemu) qom-get /machine/soc0/harts[0] mimpid
> 273
> (qemu) qom-get /machine/soc0/harts[0] marchid
> 9223372036854841344
>
> Fixes: 1e34150045 ("target/riscv/cpu.c: restrict 'mvendorid' value")
> Fixes: a1863ad368 ("target/riscv/cpu.c: restrict 'mimpid' value")
> Fixes: d6a427e2c0 ("target/riscv/cpu.c: restrict 'marchid' value")
> Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Thanks!
Applied to riscv-to-apply.next
Alistair
> ---
> target/riscv/cpu.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
> index 83c7c0cf07..70bf10aa7c 100644
> --- a/target/riscv/cpu.c
> +++ b/target/riscv/cpu.c
> @@ -1573,9 +1573,9 @@ static void cpu_set_mvendorid(Object *obj, Visitor *v, const char *name,
> static void cpu_get_mvendorid(Object *obj, Visitor *v, const char *name,
> void *opaque, Error **errp)
> {
> - bool value = RISCV_CPU(obj)->cfg.mvendorid;
> + uint32_t value = RISCV_CPU(obj)->cfg.mvendorid;
>
> - visit_type_bool(v, name, &value, errp);
> + visit_type_uint32(v, name, &value, errp);
> }
>
> static void cpu_set_mimpid(Object *obj, Visitor *v, const char *name,
> @@ -1602,9 +1602,9 @@ static void cpu_set_mimpid(Object *obj, Visitor *v, const char *name,
> static void cpu_get_mimpid(Object *obj, Visitor *v, const char *name,
> void *opaque, Error **errp)
> {
> - bool value = RISCV_CPU(obj)->cfg.mimpid;
> + uint64_t value = RISCV_CPU(obj)->cfg.mimpid;
>
> - visit_type_bool(v, name, &value, errp);
> + visit_type_uint64(v, name, &value, errp);
> }
>
> static void cpu_set_marchid(Object *obj, Visitor *v, const char *name,
> @@ -1652,9 +1652,9 @@ static void cpu_set_marchid(Object *obj, Visitor *v, const char *name,
> static void cpu_get_marchid(Object *obj, Visitor *v, const char *name,
> void *opaque, Error **errp)
> {
> - bool value = RISCV_CPU(obj)->cfg.marchid;
> + uint64_t value = RISCV_CPU(obj)->cfg.marchid;
>
> - visit_type_bool(v, name, &value, errp);
> + visit_type_uint64(v, name, &value, errp);
> }
>
> static void riscv_cpu_class_init(ObjectClass *c, void *data)
> --
> 2.41.0
>
>
prev parent reply other threads:[~2023-12-17 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 17:07 [PATCH for-9.0] target/riscv/cpu.c: fix machine IDs getters Daniel Henrique Barboza
2023-12-11 17:38 ` Philippe Mathieu-Daudé
2023-12-17 23:09 ` Alistair Francis
2023-12-17 23:31 ` Alistair Francis [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='CAKmqyKOkXe-Jxn7WGSCom_4SK9oMF41=CYO5mgBdsMCC9hxmxQ@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@rivosinc.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).