From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: Vladimir Isaev <vladimir.isaev@syntacore.com>, qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, palmer@dabbelt.com,
alistair.francis@wdc.com, bmeng.cn@gmail.com,
liwei1518@gmail.com, zhiwei_liu@linux.alibaba.com,
mjc@sifive.com
Subject: Re: [PATCH] target/riscv: fix C extension disabling on misa write
Date: Thu, 20 Feb 2025 14:59:58 -0300 [thread overview]
Message-ID: <3ffe3ecf-4bd8-447e-a984-442c71a94f89@ventanamicro.com> (raw)
In-Reply-To: <20250220163120.77328-1-vladimir.isaev@syntacore.com>
On 2/20/25 1:31 PM, Vladimir Isaev wrote:
> According to spec:
> Writing misa may increase IALIGN, e.g., by disabling the "C" extension. If an instruction that would
> write misa increases IALIGN, and the subsequent instruction’s address is not IALIGN-bit aligned, the
> write to misa is suppressed, leaving misa unchanged.
>
> So we should suppress disabling "C" if it is already enabled and
> next instruction is not aligned to 4.
>
> Fixes: f18637cd611c ("RISC-V: Add misa runtime write support")
> Signed-off-by: Vladimir Isaev <vladimir.isaev@syntacore.com>
> ---
> target/riscv/csr.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/target/riscv/csr.c b/target/riscv/csr.c
> index afb7544f0780..32f9b7b16f6f 100644
> --- a/target/riscv/csr.c
> +++ b/target/riscv/csr.c
> @@ -2067,11 +2067,12 @@ static RISCVException write_misa(CPURISCVState *env, int csrno,
> val &= env->misa_ext_mask;
>
> /*
> - * Suppress 'C' if next instruction is not aligned
> + * Disabling 'C' increases IALIGN to 32. If subsequent instruction's address
> + * is not 32-bit aligned, write to misa is suppressed.
> * TODO: this should check next_pc
> */
> - if ((val & RVC) && (GETPC() & ~3) != 0) {
> - val &= ~RVC;
Not related to your changes but it would be nice if we made more use of
QEMU_IS_ALIGNED() instead of doing these bitwise ops to check alignment.
E.g. to check if pc is aligned to 4: QEMU_IS_ALIGNED(GETPC(), 4).
> + if (!(val & RVC) && (env->misa_ext & RVC) && (GETPC() & 0x3)) {
> + return RISCV_EXCP_NONE;
> }
This will abort the write altogether, skipping valid changes to other bits. What
we want is a "val &= ~RVC" if the proper conditions for clearing RVC are met.
Thanks,
Daniel
>
> /* Disable RVG if any of its dependencies are disabled */
next prev parent reply other threads:[~2025-02-20 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 16:31 [PATCH] target/riscv: fix C extension disabling on misa write Vladimir Isaev
2025-02-20 17:59 ` Daniel Henrique Barboza [this message]
2025-02-21 7:58 ` Vladimir Isaev
2025-02-21 9:13 ` Daniel Henrique Barboza
2025-02-20 18:49 ` Richard Henderson
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=3ffe3ecf-4bd8-447e-a984-442c71a94f89@ventanamicro.com \
--to=dbarboza@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=liwei1518@gmail.com \
--cc=mjc@sifive.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=vladimir.isaev@syntacore.com \
--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 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.