blob: 6457f96654473268752ba836df94c1e22c7ea6bf (
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
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
device: 0.886
performance: 0.885
risc-v: 0.884
kernel: 0.847
graphic: 0.846
architecture: 0.765
hypervisor: 0.761
peripherals: 0.750
vnc: 0.719
boot: 0.705
ppc: 0.700
semantic: 0.671
network: 0.668
files: 0.657
assembly: 0.614
permissions: 0.606
register: 0.600
mistranslation: 0.599
socket: 0.565
VMM: 0.536
PID: 0.520
debug: 0.510
arm: 0.497
TCG: 0.447
virtual: 0.402
user-level: 0.392
x86: 0.376
i386: 0.330
KVM: 0.255
getauxval(AT_HWCAP) returns different value under qemu-system-riscv64 and qemu-riscv64
Description of problem:
I have a test program that checks for the presence of the RISC-V Vector extension (RVV) via getauxval().
```c
#include <sys/auxv.h>
#include <stdio.h>
#define ISA_V_HWCAP (1 << ('v' - 'a'))
void main() {
unsigned long hw_cap = getauxval(AT_HWCAP);
printf("RVV %s\n", hw_cap & ISA_V_HWCAP ? "detected" : "not found");
}
```
When run inside `qemu-system-riscv64` with a 6.5-rc3 kernel where `CONFIG_RISCV_ISA_V=y` and `CONFIG_RISCV_ISA_V_DEFAULT_ENABLE=y` it correctly shows:
```
$ ./hwcap
RVV detected
```
However when executed with `qemu-riscv64` it does not return the V bit set:
```
$ qemu-riscv64 hwcap
RVV not found
```
Steps to reproduce:
1. Boot 6.5-rc3 kernel with `CONFIG_RISCV_ISA_V=y` and `CONFIG_RISCV_ISA_V_DEFAULT_ENABLE=y`
2. In guest run test program hwcap (source above)
3. On host run `qemu-riscv64 hwcap`
Additional information:
|