All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Max Filippov <jcmvbkbc@gmail.com>, qemu-devel@nongnu.org
Cc: Joaquin de Andres <me@xcancerberox.com.ar>, qemu-stable@nongnu.org
Subject: Re: [PATCH] target/xtensa: fix access ring in l32ex
Date: Wed, 19 May 2021 15:56:19 +0200	[thread overview]
Message-ID: <3811d64f-b41e-c73a-05f9-4fec714e128e@amsat.org> (raw)
In-Reply-To: <20210519104433.16870-1-jcmvbkbc@gmail.com>

Cc'ing Joaquin who has interest in Xtensa ISA :)

On 5/19/21 12:44 PM, Max Filippov wrote:
> l32ex does memory access as all regular load/store operations at CRING
> level. Fix apparent pasto from l32e that caused it to use RING instead.
> 
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
>  target/xtensa/translate.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/target/xtensa/translate.c b/target/xtensa/translate.c
> index f93df87ec490..95f6b21c2a1e 100644
> --- a/target/xtensa/translate.c
> +++ b/target/xtensa/translate.c
> @@ -1814,7 +1814,7 @@ static void translate_l32ex(DisasContext *dc, const OpcodeArg arg[],
>      tcg_gen_mov_i32(addr, arg[1].in);
>      gen_load_store_alignment(dc, 2, addr, true);
>      gen_check_exclusive(dc, addr, false);
> -    tcg_gen_qemu_ld_i32(arg[0].out, addr, dc->ring, MO_TEUL);
> +    tcg_gen_qemu_ld_i32(arg[0].out, addr, dc->cring, MO_TEUL);
>      tcg_gen_mov_i32(cpu_exclusive_addr, addr);
>      tcg_gen_mov_i32(cpu_exclusive_val, arg[0].out);
>      tcg_temp_free(addr);
> 

Looking at s32ex, it makes sense.

Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>


      reply	other threads:[~2021-05-19 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 10:44 [PATCH] target/xtensa: fix access ring in l32ex Max Filippov
2021-05-19 13:56 ` Philippe Mathieu-Daudé [this message]

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=3811d64f-b41e-c73a-05f9-4fec714e128e@amsat.org \
    --to=f4bug@amsat.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=me@xcancerberox.com.ar \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    /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.