blob: 6194005ca92726f00663c0216cb1c4edd71bec1d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
arm: 0.884
device: 0.821
hypervisor: 0.771
architecture: 0.758
graphic: 0.749
boot: 0.642
semantic: 0.639
mistranslation: 0.622
performance: 0.543
i386: 0.426
vnc: 0.407
debug: 0.392
VMM: 0.364
ppc: 0.364
PID: 0.362
files: 0.341
register: 0.329
user-level: 0.327
virtual: 0.320
x86: 0.311
socket: 0.309
network: 0.307
peripherals: 0.272
permissions: 0.231
risc-v: 0.222
assembly: 0.220
KVM: 0.219
kernel: 0.207
TCG: 0.142
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.
|