summary refs log tree commit diff stats
path: root/results/classifier/108/other/2259
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-05 06:55:18 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-05 06:55:18 +0000
commit993a7c1ea28968a4479a87ad6c2637a7045d2d51 (patch)
tree024d7266fc695c4f93ab6ce0fcd52326f3ac379d /results/classifier/108/other/2259
parent2773b5e236e2217a35a53dbc298757610c7bbbc6 (diff)
downloadqemu-analysis-993a7c1ea28968a4479a87ad6c2637a7045d2d51.tar.gz
qemu-analysis-993a7c1ea28968a4479a87ad6c2637a7045d2d51.zip
add new classifier result
Diffstat (limited to 'results/classifier/108/other/2259')
-rw-r--r--results/classifier/108/other/225929
1 files changed, 29 insertions, 0 deletions
diff --git a/results/classifier/108/other/2259 b/results/classifier/108/other/2259
new file mode 100644
index 000000000..ee79eeb88
--- /dev/null
+++ b/results/classifier/108/other/2259
@@ -0,0 +1,29 @@
+graphic: 0.734
+device: 0.725
+files: 0.687
+debug: 0.503
+permissions: 0.483
+semantic: 0.472
+performance: 0.452
+network: 0.448
+vnc: 0.436
+socket: 0.412
+PID: 0.336
+boot: 0.320
+other: 0.273
+KVM: 0.084
+
+The cause code of a trap changes when qemu is nested in another qemu
+Description of problem:
+I am studying the feasibility of doing some practical work on RISCV plates. Since I don't have these boards yet, I'm emulating it with qemu. The practice in turn consists of launching with qemu a very small operating system with two tasks that make a series of system calls.
+
+When I run this practice on my host it works correctly, but when I run it on an Ubuntu emulated in riscv with qemu, the cause code for the trap changes (the first bit of the code).
+
+The demo can be found in this repository: https://github.com/Sft570/qemu-bug-report
+Steps to reproduce:
+1. Clone the repository on the host and run the demo with "make qemu"
+2. Emulate with qemu ubuntu in riscv, clone the repository and run the demo with "make qemu".
+
+The error displayed shows the change of the cause code bit. You can analyze its behavior in the trap.c file in the src folder.
+Additional information:
+