From: Frank Chang <frank.chang@sifive.com>
To: Jason Chien <jason.chien@sifive.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
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>,
Junqiang Wang <wangjunqiang@iscas.ac.cn>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH] target/riscv: Update $pc after linking to $ra in trans_cm_jalt()
Date: Wed, 7 Feb 2024 01:05:09 +0800 [thread overview]
Message-ID: <CANzO1D0Bhdugi6gbL-sLsW5yF-Fd=oV699-zw2PqpJ7DTt_PMw@mail.gmail.com> (raw)
In-Reply-To: <20240206131911.10998-1-jason.chien@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 2157 bytes --]
Reviewed-by: Frank Chang <frank.chang@sifive.com>
On Tue, Feb 6, 2024 at 9:19 PM Jason Chien <jason.chien@sifive.com> wrote:
> The original implementation sets $pc to the address read from the jump
> vector table first and links $ra with the address of the next instruction
> after the updated $pc. After jumping to the updated $pc and executing the
> next ret instruction, the program jumps to $ra, which is in the same
> function currently executing, which results in an infinite loop.
> This commit reverses the two action. Firstly, $ra is updated with the
> address of the next instruction after $pc, and sets $pc to the address
> read from the jump vector table.
>
> Signed-off-by: Jason Chien <jason.chien@sifive.com>
> ---
> target/riscv/insn_trans/trans_rvzce.c.inc | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/target/riscv/insn_trans/trans_rvzce.c.inc
> b/target/riscv/insn_trans/trans_rvzce.c.inc
> index 8d8a64f493..a185e2315f 100644
> --- a/target/riscv/insn_trans/trans_rvzce.c.inc
> +++ b/target/riscv/insn_trans/trans_rvzce.c.inc
> @@ -293,13 +293,6 @@ static bool trans_cm_jalt(DisasContext *ctx,
> arg_cm_jalt *a)
> {
> REQUIRE_ZCMT(ctx);
>
> - /*
> - * Update pc to current for the non-unwinding exception
> - * that might come from cpu_ld*_code() in the helper.
> - */
> - gen_update_pc(ctx, 0);
> - gen_helper_cm_jalt(cpu_pc, cpu_env, tcg_constant_i32(a->index));
> -
> /* c.jt vs c.jalt depends on the index. */
> if (a->index >= 32) {
> TCGv succ_pc = dest_gpr(ctx, xRA);
> @@ -307,6 +300,13 @@ static bool trans_cm_jalt(DisasContext *ctx,
> arg_cm_jalt *a)
> gen_set_gpr(ctx, xRA, succ_pc);
> }
>
> + /*
> + * Update pc to current for the non-unwinding exception
> + * that might come from cpu_ld*_code() in the helper.
> + */
> + gen_update_pc(ctx, 0);
> + gen_helper_cm_jalt(cpu_pc, cpu_env, tcg_constant_i32(a->index));
> +
> tcg_gen_lookup_and_goto_ptr();
> ctx->base.is_jmp = DISAS_NORETURN;
> return true;
> --
> 2.43.0
>
>
>
[-- Attachment #2: Type: text/html, Size: 2725 bytes --]
next prev parent reply other threads:[~2024-02-06 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 13:18 [PATCH] target/riscv: Update $pc after linking to $ra in trans_cm_jalt() Jason Chien
2024-02-06 17:05 ` Frank Chang [this message]
2024-02-06 20:24 ` Richard Henderson
2024-02-07 3:33 ` Jason Chien
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='CANzO1D0Bhdugi6gbL-sLsW5yF-Fd=oV699-zw2PqpJ7DTt_PMw@mail.gmail.com' \
--to=frank.chang@sifive.com \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=jason.chien@sifive.com \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=wangjunqiang@iscas.ac.cn \
--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).