From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: BALATON Zoltan <balaton@eik.bme.hu>,
qemu-devel@nongnu.org, alex.bennee@linaro.org,
qemu-stable@nongnu.org
Subject: Re: [PATCH] target/sh4: Fix TB_FLAG_UNALIGN
Date: Wed, 31 Aug 2022 10:30:15 +0900 [thread overview]
Message-ID: <87y1v5xkrc.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <ecaee2a6-c2be-388e-425d-3cbe3dda2a4a@linaro.org>
On Tue, 30 Aug 2022 01:10:29 +0900,
Richard Henderson wrote:
>
> On 8/29/22 02:05, BALATON Zoltan wrote:
> > On Sun, 28 Aug 2022, Richard Henderson wrote:
> >> The value previously chosen overlaps GUSA_MASK.
> >>
> >> Cc: qemu-stable@nongnu.org
> >> Fixes: 4da06fb3062 ("target/sh4: Implement prctl_unalign_sigbus")
> >> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/856
> >> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> >> ---
> >> target/sh4/cpu.h | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/target/sh4/cpu.h b/target/sh4/cpu.h
> >> index 9f15ef913c..e79cbc59e2 100644
> >> --- a/target/sh4/cpu.h
> >> +++ b/target/sh4/cpu.h
> >> @@ -84,7 +84,7 @@
> >> #define DELAY_SLOT_RTE (1 << 2)
> >>
> >> #define TB_FLAG_PENDING_MOVCA (1 << 3)
> >> -#define TB_FLAG_UNALIGN (1 << 4)
> >> +#define TB_FLAG_UNALIGN (1 << 13)
> >
> > Is it worth a comment to note why that value to avoid the same
> > problem if another flag is added in the future?
>
> Hmm, or perhaps move it down below, so that we see bit 3 used, then bits 4-12, then bit 13.
>
>
> r~
It looks like the gUSA and unalign access flags are mixed.
I think the flags should also be separated as the two features are not related.
--
Yosinori Sato
next prev parent reply other threads:[~2022-08-31 1:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 2:13 [PATCH] target/sh4: Fix TB_FLAG_UNALIGN Richard Henderson
2022-08-29 2:16 ` Richard Henderson
2022-08-29 9:05 ` BALATON Zoltan
2022-08-29 16:10 ` Richard Henderson
2022-08-31 1:30 ` Yoshinori Sato [this message]
2022-08-31 16:55 ` Richard Henderson
2022-08-31 8:30 ` Yoshinori Sato
2022-08-31 16:56 ` 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=87y1v5xkrc.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=alex.bennee@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.