qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: arikalo@wavecomp.com, Aurelien Jarno <aurelien@aurel32.net>,
	QEMU Developers <qemu-devel@nongnu.org>,
	lixinyu <precinct@mail.ustc.edu.cn>
Subject: Re: [PATCH] tcg/mips: mips sync* encode error
Date: Sat, 11 Apr 2020 20:37:23 +0200	[thread overview]
Message-ID: <CAHiYmc4r4zcRX02FQa0pjLYExZquVBrLGKYF_SDFZOYZhMFaCw@mail.gmail.com> (raw)
In-Reply-To: <c3fac325-df9a-be96-72d0-1898635afef9@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

20:08 Sub, 11.04.2020. Richard Henderson <richard.henderson@linaro.org> је
написао/ла:
>
> On 4/11/20 5:46 AM, lixinyu wrote:
> > OPC_SYNC_WMB, OPC_SYNC_MB, OPC_SYNC_ACQUIRE, OPC_SYNC_RELEASE and
> > OPC_SYNC_RMB have wrong encode. According to the mips manual,
> > their encode should be 'OPC_SYNC | 0x?? << 6' rather than
> > 'OPC_SYNC | 0x?? << 5'. Wrong encode can lead illegal instruction
> > errors. These instructions often appear with multi-threaded
> > simulation.
>
> Good catch.
>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>
> Queued to tcg-for-5.0.
>

Reviewed-by: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>

Thanks to Lixinyu, in the first place, for reporting the problem, and also
thanks to Richard for reviewing and incorporating this patch into his queue
for 5.0. I also think, as Richard does, that this should go into 5.0, even
in this final stages.

Happy Easter, or hapy and sunny weekend, whatever you choose.

Aleksandar

>
> r~
>

[-- Attachment #2: Type: text/html, Size: 1490 bytes --]

  reply	other threads:[~2020-04-11 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11 12:46 [PATCH] tcg/mips: mips sync* encode error lixinyu
2020-04-11 18:07 ` Richard Henderson
2020-04-11 18:37   ` Aleksandar Markovic [this message]
2020-04-12 17:25 ` Philippe Mathieu-Daudé

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=CAHiYmc4r4zcRX02FQa0pjLYExZquVBrLGKYF_SDFZOYZhMFaCw@mail.gmail.com \
    --to=aleksandar.qemu.devel@gmail.com \
    --cc=arikalo@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --cc=precinct@mail.ustc.edu.cn \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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).