add 18th iteration of classifier

1 files changed, 70 insertions, 0 deletions

diff --git a/results/classifier/118/risc-v/1850378 b/results/classifier/118/risc-v/1850378
new file mode 100644
index 000000000..529ae75b5
--- /dev/null
+++ b/results/classifier/118/risc-v/1850378
@@ -0,0 +1,70 @@
+risc-v: 0.832
+user-level: 0.800
+kernel: 0.799
+graphic: 0.759
+device: 0.751
+architecture: 0.732
+performance: 0.713
+virtual: 0.662
+semantic: 0.653
+debug: 0.612
+mistranslation: 0.556
+peripherals: 0.551
+network: 0.513
+PID: 0.488
+assembly: 0.478
+hypervisor: 0.466
+socket: 0.463
+ppc: 0.462
+permissions: 0.455
+register: 0.402
+x86: 0.401
+i386: 0.393
+boot: 0.385
+VMM: 0.374
+vnc: 0.343
+TCG: 0.323
+KVM: 0.268
+arm: 0.266
+files: 0.191
+
+RISC-V unreliable IPIs
+
+I am working on a project with custom inter processor interrupts (IPIs) on the RISC-V virt machine.
+After upgrading from version 3.1.0 to 4.1.0 which fixes a related issue (https://github.com/riscv/riscv-qemu/issues/132) I am able to use the CPU hotplug feature.
+
+However, if I try to use IPIs for communication between two cores, the wfi instruction behaves strangely. Either it does not return, or it returns on timer interrupts, even though they are disabled. The code, I use on one core to wait for an interrupt is the following.
+
+	csr_clear(sie, SIE_SEIE | SIE_STIE);
+	do {
+		wait_for_interrupt();
+		sipval = csr_read(sip);
+		sieval = csr_read(sie);
+		scauseval = csr_read(scause) & 0xFF;
+	/* only break if wfi returns for an software interrupt */
+	} while ((sipval & sieval) == 0 && scauseval != 1);
+	csr_set(sie, SIE_SEIE | SIE_STIE);
+
+Since the resulting sequence does not seem to be deterministic, my guess is, that it has something to do with the communication of qemu's threads for the different cores.
+
+Can you post a whole program that reproduces this?  freedom-e-sdk <https://github.com/sifive/freedom-e-sdk> will run bare-metal code on QEMU if you don't want to post the rest of the surrounding infrastructure.
+
+I created a minimal example from my setup. I'm running a kernel 4.19.57 with a custom firmware based on bbl (https://github.com/riscv/riscv-pk). 
+An ioctl device from a kernel module is used to execute the code above in kernel space.
+In the example, the userspace application proceeds after a couple of seconds without receiving the custom IPI.
+
+The QEMU project is currently considering to move its bug tracking to
+another system. For this we need to know which bugs are still valid
+and which could be closed already. Thus we are setting older bugs to
+"Incomplete" now.
+
+If you still think this bug report here is valid, then please switch
+the state back to "New" within the next 60 days, otherwise this report
+will be marked as "Expired". Or please mark it as "Fix Released" if
+the problem has been solved with a newer version of QEMU already.
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+