restructure results

1 files changed, 42 insertions, 0 deletions

diff --git a/results/classifier/zero-shot/118/hypervisor/1647 b/results/classifier/zero-shot/118/hypervisor/1647
new file mode 100644
index 00000000..e0bcc767
--- /dev/null
+++ b/results/classifier/zero-shot/118/hypervisor/1647
@@ -0,0 +1,42 @@
+hypervisor: 0.985
+kernel: 0.957
+risc-v: 0.892
+device: 0.773
+graphic: 0.705
+vnc: 0.629
+architecture: 0.585
+network: 0.551
+ppc: 0.547
+permissions: 0.536
+socket: 0.523
+register: 0.505
+semantic: 0.502
+files: 0.485
+arm: 0.424
+boot: 0.413
+performance: 0.376
+debug: 0.376
+virtual: 0.361
+user-level: 0.324
+mistranslation: 0.316
+VMM: 0.310
+x86: 0.307
+i386: 0.307
+TCG: 0.302
+PID: 0.246
+peripherals: 0.125
+KVM: 0.113
+assembly: 0.100
+
+Potential Bug in RISCV Hypervisor Extension: Timer Interrupt Handling in QEMU v8.0.0-rc1
+Steps to reproduce:
+1. Build and run a simple hypervisor on QEMU v8.0.0-rc1 with the hypervisor extension feature of RISCV.
+2. Set up hideleg, henvcfg, etc., in hypervisor and run the Linux kernel.
+3. Observe the issue of infinite loop caused by the pending timer interrupt.
+Additional information:
+Linux version: riscv_aia_v1 from github.com/avpatel/linux
+OpenSBI version: Modified 1.1
+
+I would greatly appreciate it if you could kindly provide some guidance. Is this behavior expected or could this be a bug? I've tried to provide a detailed analysis of my observations, but I'm not 100% certain if my understanding is correct.
+
+Thank you for your time and consideration.