summary refs log tree commit diff stats
path: root/results/classifier/105/device/2665
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/105/device/2665')
-rw-r--r--results/classifier/105/device/266524
1 files changed, 24 insertions, 0 deletions
diff --git a/results/classifier/105/device/2665 b/results/classifier/105/device/2665
new file mode 100644
index 000000000..9b5678408
--- /dev/null
+++ b/results/classifier/105/device/2665
@@ -0,0 +1,24 @@
+device: 0.821
+instruction: 0.777
+graphic: 0.749
+boot: 0.642
+semantic: 0.639
+mistranslation: 0.622
+other: 0.498
+vnc: 0.407
+socket: 0.309
+network: 0.307
+assembly: 0.220
+KVM: 0.219
+
+target/arm: cannot boot when CPU supports SME
+Description of problem:
+On macOS 15.2 beta, Apple's Hypervisor.framework exposes the SME feat flag to QEMU. As a result, in `arm_cpu_sme_finalize`, `cpu_isar_feature(aa64_sme, cpu)` returns true and the program will always exit with the following:
+
+```
+qemu-aarch64-softmmu: cannot disable sme4224
+All SME vector lengths are disabled.
+With SME enabled, at least one vector length must be enabled.
+```
+
+This is because `vq_supported` and `vq_init` are both 0 as they are not initialized anywhere. It seems that in the original commit e74c097638d38b46d9c68f11565432034afc0ad0 the only place `cpu->sme_vq.supported` is initialized is with `aarch64_max_initfn` when KVM and HVF are not used as the backend.