From: Richard Henderson <richard.henderson@linaro.org>
To: amagdy.afifi@gmail.com, qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, sagark@eecs.berkeley.edu,
kbastian@mail.uni-paderborn.de, palmer@sifive.com,
mjc@sifive.com, Alistair.Francis@wdc.com
Subject: Re: [Qemu-devel] [PATCH] riscv: Add proper alignment check and pending 'C' extension upon misa writes
Date: Fri, 22 Feb 2019 15:57:40 -0800 [thread overview]
Message-ID: <f782bdde-2a42-c612-5769-1cde42e7c2a4@linaro.org> (raw)
In-Reply-To: <20190222162555.13764-2-amagdy.afifi@gmail.com>
On 2/22/19 8:25 AM, amagdy.afifi@gmail.com wrote:
> @@ -373,9 +373,10 @@ static int write_misa(CPURISCVState *env, int csrno, target_ulong val)
> }
>
> /* Suppress 'C' if next instruction is not aligned
> - TODO: this should check next_pc */
> - if ((val & RVC) && (GETPC() & ~3) != 0) {
> + check next target pc */
> + if ((val & RVC) && (env->pc_next & 3) != 0) {
> val &= ~RVC;
> + env->pending_rvc = 1;
> }
>
> /* misa.MXL writes are not supported by QEMU */
> diff --git a/target/riscv/translate.c b/target/riscv/translate.c
> index 2321bba..c9d84ea 100644
> --- a/target/riscv/translate.c
> +++ b/target/riscv/translate.c
> @@ -1999,20 +1999,26 @@ static void decode_RV32_64G(DisasContext *ctx)
> }
> }
>
> -static void decode_opc(DisasContext *ctx)
> +static void decode_opc(DisasContext *ctx, CPUState *cpu)
> {
> + CPURISCVState *env = cpu->env_ptr;
> /* check for compressed insn */
> if (extract32(ctx->opcode, 0, 2) != 3) {
> if (!has_ext(ctx, RVC)) {
> gen_exception_illegal(ctx);
> } else {
> - ctx->pc_succ_insn = ctx->base.pc_next + 2;
> + env->pc_next = ctx->pc_succ_insn = ctx->base.pc_next + 2;
> decode_RV32_64C(ctx);
> }
> } else {
> - ctx->pc_succ_insn = ctx->base.pc_next + 4;
> + env->pc_next = ctx->pc_succ_insn = ctx->base.pc_next + 4;
> decode_RV32_64G(ctx);
> }
> + /* check pending RVC */
> + if (env->pending_rvc && ((env->pc_next & 3) != 0)) {
> + env->misa |= RVC;
> + env->pending_rvc = 0;
You cannot manipulate env like this during translation.
Neither the write to env->pc_next nor the read from env->pending_rvc here will
be in any synchronization with the execution of write_misa.
What semantics are you attempting to implement wrt setting/clearing RVC from MISA?
> @@ -2061,7 +2067,7 @@ static void riscv_tr_translate_insn
> CPURISCVState *env = cpu->env_ptr;
>
> ctx->opcode = cpu_ldl_code(env, ctx->base.pc_next);
> - decode_opc(ctx);
> + decode_opc(ctx, cpu);
This is exactly the reason why cpu is *not* passed down to decode_opc, so that
you cannot make this kind of mistake.
r~
next prev parent reply other threads:[~2019-02-22 23:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 16:25 [Qemu-devel] Add proper alignment check and pending 'C' extension for riscv amagdy.afifi
2019-02-22 16:25 ` [Qemu-devel] [PATCH] riscv: Add proper alignment check and pending 'C' extension upon misa writes amagdy.afifi
2019-02-22 23:57 ` Richard Henderson [this message]
2019-02-24 7:57 ` Amed Magdy
2019-02-24 19:04 ` Richard Henderson
2019-02-26 7:58 ` Amed Magdy
2019-02-26 8:11 ` Amed Magdy
2019-02-23 21:45 ` Eric Blake
2019-02-24 8:07 ` Amed Magdy
2019-02-25 14:14 ` Eric Blake
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=f782bdde-2a42-c612-5769-1cde42e7c2a4@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Alistair.Francis@wdc.com \
--cc=amagdy.afifi@gmail.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=mjc@sifive.com \
--cc=palmer@sifive.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).