diff options
| author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-05-10 12:19:13 +0100 |
|---|---|---|
| committer | Daniel Henrique Barboza <danielhb413@gmail.com> | 2023-05-27 08:25:19 -0300 |
| commit | 5260ecffd24e36c029849f379c8b9cc3d099c879 (patch) | |
| tree | 76d37f18d97121c2e8911c698212003a039a3283 /hw/misc/iotkit-sysinfo.c | |
| parent | ac84b57b4d74606f7f83667a0606deef32b2049d (diff) | |
| download | qemu-5260ecffd24e36c029849f379c8b9cc3d099c879.zip qemu-5260ecffd24e36c029849f379c8b9cc3d099c879.tar.gz qemu-5260ecffd24e36c029849f379c8b9cc3d099c879.tar.bz2 | |
target/ppc: Fix fallback to MFSS for MFFS* instructions on pre 3.0 ISAs
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 doesn't have
the fallback for 3.0 onwards to match hardware behaviour.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reviewed-by: Matheus Ferst <matheus.ferst@eldorado.org.br>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-Id: <20230510111913.1718734-1-richard.purdie@linuxfoundation.org>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Diffstat (limited to 'hw/misc/iotkit-sysinfo.c')
0 files changed, 0 insertions, 0 deletions