From: Alistair Francis <alistair23@gmail.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Mikhail Tyutin" <m.tyutin@yadro.com>,
"Aleksandr Anenkov" <a.anenkov@yadro.com>,
qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Fabiano Rosas" <farosas@suse.de>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Bin Meng" <bin.meng@windriver.com>,
"Weiwei Li" <liweiwei@iscas.ac.cn>,
"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
qemu-riscv@nongnu.org
Subject: Re: [PATCH v6 1/5] hw/riscv: Use misa_mxl instead of misa_mxl_max
Date: Thu, 23 Nov 2023 13:04:35 +1000 [thread overview]
Message-ID: <CAKmqyKMo41GMJ0vVN2_CsfOVrfsz8H9AtxTe6-JbtX+Pi6B3DA@mail.gmail.com> (raw)
In-Reply-To: <20231030054834.39145-2-akihiko.odaki@daynix.com>
On Mon, Oct 30, 2023 at 3:50 PM Akihiko Odaki <akihiko.odaki@daynix.com> wrote:
>
> The effective MXL value matters when booting.
This doesn't sound right. Surely the max is what matters here
Also, this was specifically changed to misa_mxl_max in db23e5d981a
"target/riscv: Replace riscv_cpu_is_32bit with riscv_cpu_mxl".
This needs a much better description of why this change should be made
Alistair
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> hw/riscv/boot.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/riscv/boot.c b/hw/riscv/boot.c
> index 52bf8e67de..dad3f6e7b1 100644
> --- a/hw/riscv/boot.c
> +++ b/hw/riscv/boot.c
> @@ -36,7 +36,7 @@
>
> bool riscv_is_32bit(RISCVHartArrayState *harts)
> {
> - return harts->harts[0].env.misa_mxl_max == MXL_RV32;
> + return harts->harts[0].env.misa_mxl == MXL_RV32;
> }
>
> /*
> --
> 2.42.0
>
>
next prev parent reply other threads:[~2023-11-23 3:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 5:46 [PATCH v6 0/5] gdbstub and TCG plugin improvements Akihiko Odaki
2023-10-30 5:46 ` [PATCH v6 1/5] hw/riscv: Use misa_mxl instead of misa_mxl_max Akihiko Odaki
2023-11-23 3:04 ` Alistair Francis [this message]
2023-11-23 7:24 ` Akihiko Odaki
2023-12-15 5:34 ` Alistair Francis
2023-12-15 6:34 ` Akihiko Odaki
2023-12-18 3:15 ` Alistair Francis
2023-10-30 5:46 ` [PATCH v6 2/5] target/riscv: Remove misa_mxl validation Akihiko Odaki
2023-11-23 3:08 ` Alistair Francis
2023-10-30 5:46 ` [PATCH v6 3/5] target/riscv: Move misa_mxl_max to class Akihiko Odaki
2023-10-30 5:46 ` [PATCH v6 4/5] target/riscv: Validate misa_mxl_max only once Akihiko Odaki
2023-10-30 5:46 ` [PATCH v6 5/5] default-configs: Add TARGET_XML_FILES definition Akihiko Odaki
2023-10-30 8:47 ` Philippe Mathieu-Daudé
2023-10-31 22:37 ` Alex Bennée
2023-11-23 3:10 ` [PATCH v6 0/5] gdbstub and TCG plugin improvements Alistair Francis
2023-11-23 7:30 ` Akihiko Odaki
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=CAKmqyKMo41GMJ0vVN2_CsfOVrfsz8H9AtxTe6-JbtX+Pi6B3DA@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=a.anenkov@yadro.com \
--cc=akihiko.odaki@daynix.com \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=farosas@suse.de \
--cc=liweiwei@iscas.ac.cn \
--cc=m.tyutin@yadro.com \
--cc=palmer@dabbelt.com \
--cc=philmd@linaro.org \
--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).