From: "Cédric Le Goater" <clegoate@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, Mads Ynddal <mads@ynddal.dk>
Subject: Re: [PATCH] target/arm: Restructure has_vfp_d32 test
Date: Mon, 19 Jun 2023 19:36:45 +0200 [thread overview]
Message-ID: <682ff90d-3de5-7f12-25b0-edf252d20c95@redhat.com> (raw)
In-Reply-To: <20230619140216.402530-1-richard.henderson@linaro.org>
On 6/19/23 16:02, Richard Henderson wrote:
> One cannot test for feature aa32_simd_r32 without first
> testing if AArch32 mode is supported at all. This leads to
>
> qemu-system-aarch64: ARM CPUs must have both VFP-D32 and Neon or neither
>
> for Apple M1 cpus.
The orangepi5 board I use didn't have that kind problem.
> We already have a check for ARMv8-A never setting vfp-d32 true,
> so restructure the code so that AArch64 avoids the test entirely.
>
> Reported-by: Mads Ynddal <mads@ynddal.dk>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Thanks for the fix,
C.
> ---
> target/arm/cpu.c | 28 +++++++++++++++-------------
> 1 file changed, 15 insertions(+), 13 deletions(-)
>
> diff --git a/target/arm/cpu.c b/target/arm/cpu.c
> index 353fc48567..706dbd37b1 100644
> --- a/target/arm/cpu.c
> +++ b/target/arm/cpu.c
> @@ -1402,25 +1402,27 @@ void arm_cpu_post_init(Object *obj)
> * KVM does not currently allow us to lie to the guest about its
> * ID/feature registers, so the guest always sees what the host has.
> */
> - if (arm_feature(&cpu->env, ARM_FEATURE_AARCH64)
> - ? cpu_isar_feature(aa64_fp_simd, cpu)
> - : cpu_isar_feature(aa32_vfp, cpu)) {
> - cpu->has_vfp = true;
> - if (!kvm_enabled()) {
> - qdev_property_add_static(DEVICE(obj), &arm_cpu_has_vfp_property);
> + if (arm_feature(&cpu->env, ARM_FEATURE_AARCH64)) {
> + if (cpu_isar_feature(aa64_fp_simd, cpu)) {
> + cpu->has_vfp = true;
> + cpu->has_vfp_d32 = true;
> + if (tcg_enabled() || qtest_enabled()) {
> + qdev_property_add_static(DEVICE(obj),
> + &arm_cpu_has_vfp_property);
> + }
> }
> - }
> -
> - if (cpu->has_vfp && cpu_isar_feature(aa32_simd_r32, cpu)) {
> - cpu->has_vfp_d32 = true;
> - if (!kvm_enabled()) {
> + } else if (cpu_isar_feature(aa32_vfp, cpu)) {
> + cpu->has_vfp = true;
> + if (cpu_isar_feature(aa32_simd_r32, cpu)) {
> + cpu->has_vfp_d32 = true;
> /*
> * The permitted values of the SIMDReg bits [3:0] on
> * Armv8-A are either 0b0000 and 0b0010. On such CPUs,
> * make sure that has_vfp_d32 can not be set to false.
> */
> - if (!(arm_feature(&cpu->env, ARM_FEATURE_V8) &&
> - !arm_feature(&cpu->env, ARM_FEATURE_M))) {
> + if ((tcg_enabled() || qtest_enabled())
> + && !(arm_feature(&cpu->env, ARM_FEATURE_V8)
> + && !arm_feature(&cpu->env, ARM_FEATURE_M))) {
> qdev_property_add_static(DEVICE(obj),
> &arm_cpu_has_vfp_d32_property);
> }
next prev parent reply other threads:[~2023-06-19 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 14:02 [PATCH] target/arm: Restructure has_vfp_d32 test Richard Henderson
2023-06-19 16:07 ` Philippe Mathieu-Daudé
2023-06-19 16:59 ` Richard Henderson
2023-06-19 17:36 ` Cédric Le Goater [this message]
2023-06-19 19:58 ` Mads Ynddal
2023-06-20 5:29 ` Philippe Mathieu-Daudé
2023-06-20 7:19 ` Richard Henderson
2023-06-23 10:27 ` Peter Maydell
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=682ff90d-3de5-7f12-25b0-edf252d20c95@redhat.com \
--to=clegoate@redhat.com \
--cc=mads@ynddal.dk \
--cc=qemu-arm@nongnu.org \
--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).