From: Richard Henderson <richard.henderson@linaro.org>
To: Chao Liu <lc00631@tecorigin.com>,
bmeng.cn@gmail.com, liwei1518@gmail.com, palmer@dabbelt.com,
alistair.francis@wdc.com
Cc: dbarboza@ventanamicro.com, zhiwei_liu@linux.alibaba.com,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
zqz00548@tecorigin.com
Subject: Re: [PATCH v2 1/1] target/riscv: add VILL field for vtype register macro definition
Date: Wed, 11 Dec 2024 09:55:47 -0600 [thread overview]
Message-ID: <115a3d3d-a303-4e7d-88fd-de1a291db540@linaro.org> (raw)
In-Reply-To: <87f12c20620026268bc49cd030e6ce8f26e718c4.1733930699.git.lc00631@tecorigin.com>
On 12/11/24 09:48, Chao Liu wrote:
> Signed-off-by: Chao Liu <lc00631@tecorigin.com>
> ---
> target/riscv/cpu.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/target/riscv/cpu.h b/target/riscv/cpu.h
> index 284b112821..0d74ee4581 100644
> --- a/target/riscv/cpu.h
> +++ b/target/riscv/cpu.h
> @@ -170,7 +170,8 @@ FIELD(VTYPE, VSEW, 3, 3)
> FIELD(VTYPE, VTA, 6, 1)
> FIELD(VTYPE, VMA, 7, 1)
> FIELD(VTYPE, VEDIV, 8, 2)
> -FIELD(VTYPE, RESERVED, 10, sizeof(target_ulong) * 8 - 11)
> +FIELD(VTYPE, RESERVED, 10, sizeof(target_ulong) * 8 - 12)
> +FIELD(VTYPE, VILL, sizeof(target_ulong) * 8 - 1, 1)
Still incorrect, for the same reason.
We support execution of rv32 cpus with qemu-system-riscv64, where sizeof(target_ulong) is
always 8. We support SXL/UXL, which changes the behaviour at runtime.
And, really, why do you want to add a define that is never used?
r~
next prev parent reply other threads:[~2024-12-11 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 15:48 [PATCH v2 0/1] Add vtype.vill FIELD macro definition Chao Liu
2024-12-11 15:48 ` [PATCH v2 1/1] target/riscv: add VILL field for vtype register " Chao Liu
2024-12-11 15:55 ` Richard Henderson [this message]
2024-12-11 16:36 ` Chao Liu
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=115a3d3d-a303-4e7d-88fd-de1a291db540@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=lc00631@tecorigin.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.com \
--cc=zqz00548@tecorigin.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.