From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [PATCH] target/sparc: Handle FPRS correctly on big-endian hosts
Date: Fri, 14 Jul 2023 19:52:23 +0200 [thread overview]
Message-ID: <869d9cf9-003a-b721-651c-b5bb82ed593d@linaro.org> (raw)
In-Reply-To: <20230714172602.397267-1-peter.maydell@linaro.org>
Hi Peter,
On 14/7/23 19:26, Peter Maydell wrote:
> In CPUSparcState we define the fprs field as uint64_t. However we
> then refer to it in translate.c via a TCGv_i32 which we set up with
> tcg_global_mem_new_ptr(). This means that on a big-endian host when
> the guest does something to writo te the FPRS register this value
> ends up in the wrong half of the uint64_t, and the QEMU C code that
> refers to env->fprs sees the wrong value. The effect of this is that
> guest code that enables the FPU crashes with spurious FPU Disabled
> exceptions. In particular, this is why
> tests/avocado/machine_sparc64_sun4u.py:Sun4uMachine.test_sparc64_sun4u
> times out on an s390 host.
>
> There are multiple ways we could fix this; since there are actually
> only three bits in the FPRS register and the code in translate.c
> would be a bit painful to convert to dealing with a TCGv_i64, change
> the type of the CPU state struct field to match what translate.c is
> expecting.
>
> (None of the other fields referenced by the r32[] array in
> sparc_tcg_init() have the wrong type.)
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> Another in my occasional series of "fix an avocado failure on
> s390" Friday afternoon patches :-)
:)
> diff --git a/target/sparc/gdbstub.c b/target/sparc/gdbstub.c
> index a1c8fdc4d55..bddb9609b7b 100644
> --- a/target/sparc/gdbstub.c
> +++ b/target/sparc/gdbstub.c
> @@ -96,7 +96,10 @@ int sparc_cpu_gdb_read_register(CPUState *cs, GByteArray *mem_buf, int n)
> case 83:
> return gdb_get_regl(mem_buf, env->fsr);
> case 84:
> - return gdb_get_regl(mem_buf, env->fprs);
> + {
> + target_ulong fprs = env->fprs;
> + return gdb_get_regl(mem_buf, fprs);
Why not return gdb_get_reg32() ?
> + }
next prev parent reply other threads:[~2023-07-14 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 17:26 [PATCH] target/sparc: Handle FPRS correctly on big-endian hosts Peter Maydell
2023-07-14 17:29 ` Peter Maydell
2023-07-14 17:52 ` Philippe Mathieu-Daudé [this message]
2023-07-16 17:32 ` Peter Maydell
2023-07-17 11:42 ` Philippe Mathieu-Daudé
2023-07-16 17:09 ` 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=869d9cf9-003a-b721-651c-b5bb82ed593d@linaro.org \
--to=philmd@linaro.org \
--cc=atar4qemu@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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 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).