From: Richard Henderson <richard.henderson@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
qemu-devel@nongnu.org
Cc: "Víctor Colombo" <victor.colombo@eldorado.org.br>,
"Matheus Ferst" <matheus.ferst@eldorado.org.br>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>
Subject: Re: [PATCH v2] target/ppc: Fix fallback to MFSS for MFFS* instructions on pre 3.0 ISAs
Date: Sat, 6 May 2023 08:27:38 +0100 [thread overview]
Message-ID: <d14a5c41-c4a2-3549-e272-1255f6dc79f9@linaro.org> (raw)
In-Reply-To: <20230506065240.3177798-1-richard.purdie@linuxfoundation.org>
On 5/6/23 07:52, Richard Purdie wrote:
> The following commits changed the code such that the fallback to MFSS for MFFSCRN,
> MFFSCRNI, MFFSCE and MFFSL on pre 3.0 ISAs was removed and became an illegal instruction:
>
> bf8adfd88b547680aa857c46098f3a1e94373160 - target/ppc: Move mffscrn[i] to decodetree
> 394c2e2fda70da722f20fb60412d6c0ca4bfaa03 - target/ppc: Move mffsce to decodetree
> 3e5bce70efe6bd1f684efbb21fd2a316cbf0657e - target/ppc: Move mffsl to decodetree
>
> The hardware will handle them as a MFFS instruction as the code did previously.
> This means applications that were segfaulting under qemu when encountering these
> instructions which is used in glibc libm functions for example.
>
> The fallback for MFFSCDRN and MFFSCDRNI added in a later patch was also missing.
>
> This patch restores the fallback to MFSS for these instructions on pre 3.0s ISAs
> as the hardware decoder would, fixing the segfaulting libm code. It and also ensures
> the MFSS instruction is used for currently reserved bits to handle other potential
> ISA additions more correctly.
>
> Signed-off-by: Richard Purdie<richard.purdie@linuxfoundation.org>
> ---
> target/ppc/insn32.decode | 19 ++++++++++++-------
> target/ppc/translate/fp-impl.c.inc | 30 ++++++++++++++++++++++++------
> 2 files changed, 36 insertions(+), 13 deletions(-)
>
> v2 - switch to use decodetree pattern groups per feedback
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2023-05-06 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 6:52 [PATCH v2] target/ppc: Fix fallback to MFSS for MFFS* instructions on pre 3.0 ISAs Richard Purdie
2023-05-06 7:27 ` Richard Henderson [this message]
2023-05-08 12:11 ` Matheus K. Ferst
2023-05-10 8:05 ` Richard Henderson
2023-05-10 7:28 ` 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=d14a5c41-c4a2-3549-e272-1255f6dc79f9@linaro.org \
--to=richard.henderson@linaro.org \
--cc=danielhb413@gmail.com \
--cc=matheus.ferst@eldorado.org.br \
--cc=qemu-devel@nongnu.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=victor.colombo@eldorado.org.br \
/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).