summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/1850378
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:24:58 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:27:06 +0000
commit33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch)
tree406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/1850378
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloadqemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/1850378')
-rw-r--r--results/scraper/launchpad-without-comments/185037818
1 files changed, 18 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1850378 b/results/scraper/launchpad-without-comments/1850378
new file mode 100644
index 000000000..a71c12e52
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1850378
@@ -0,0 +1,18 @@
+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.
\ No newline at end of file