diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/2665')
| -rw-r--r-- | results/classifier/zero-shot/108/other/2665 | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/2665 b/results/classifier/zero-shot/108/other/2665 new file mode 100644 index 000000000..dc774555f --- /dev/null +++ b/results/classifier/zero-shot/108/other/2665 @@ -0,0 +1,26 @@ +device: 0.821 +graphic: 0.749 +boot: 0.642 +semantic: 0.639 +performance: 0.543 +other: 0.498 +vnc: 0.407 +debug: 0.392 +PID: 0.362 +files: 0.341 +socket: 0.309 +network: 0.307 +permissions: 0.231 +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. |