diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-05 06:55:18 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-05 06:55:18 +0000 |
| commit | 993a7c1ea28968a4479a87ad6c2637a7045d2d51 (patch) | |
| tree | 024d7266fc695c4f93ab6ce0fcd52326f3ac379d /results/classifier/108/other/1915027 | |
| parent | 2773b5e236e2217a35a53dbc298757610c7bbbc6 (diff) | |
| download | qemu-analysis-993a7c1ea28968a4479a87ad6c2637a7045d2d51.tar.gz qemu-analysis-993a7c1ea28968a4479a87ad6c2637a7045d2d51.zip | |
add new classifier result
Diffstat (limited to 'results/classifier/108/other/1915027')
| -rw-r--r-- | results/classifier/108/other/1915027 | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/results/classifier/108/other/1915027 b/results/classifier/108/other/1915027 new file mode 100644 index 000000000..74a503947 --- /dev/null +++ b/results/classifier/108/other/1915027 @@ -0,0 +1,29 @@ +graphic: 0.759 +other: 0.744 +performance: 0.649 +device: 0.634 +semantic: 0.632 +permissions: 0.288 +vnc: 0.284 +debug: 0.274 +network: 0.181 +boot: 0.140 +PID: 0.138 +socket: 0.116 +files: 0.081 +KVM: 0.044 + +RISC-V 64, CPUs do ilegal 0x00 write with SMP + +When QEMU is runt like this: + +qemu-system-riscv64 -d unimp,guest_errors -smp 8 + +Other harts will do a illegal write on address 0x00. + +This could be mostly (i think) because the initial assembly code is only loaded on the first hart and the others do a mess because there is no code to execute. + +Even with -smp 1 you will see the same errors. The problem is because there is nothing to run after OpenSBI jumps to the next stage. + +If you load a kernel you will not see the error messages. + |