1 files changed, 47 insertions, 0 deletions
diff --git a/results/classifier/118/none/1824778 b/results/classifier/118/none/1824778
new file mode 100644
index 000000000..361c96143
--- /dev/null
+++ b/results/classifier/118/none/1824778
@@ -0,0 +1,47 @@
+ppc: 0.672
+architecture: 0.669
+device: 0.493
+semantic: 0.280
+graphic: 0.275
+VMM: 0.273
+network: 0.264
+PID: 0.236
+files: 0.221
+boot: 0.202
+vnc: 0.194
+register: 0.184
+user-level: 0.177
+arm: 0.158
+socket: 0.151
+permissions: 0.146
+virtual: 0.145
+TCG: 0.145
+debug: 0.140
+risc-v: 0.137
+kernel: 0.136
+mistranslation: 0.124
+hypervisor: 0.110
+peripherals: 0.110
+performance: 0.083
+x86: 0.076
+i386: 0.057
+KVM: 0.054
+assembly: 0.052
+
+PowerPC64: tlbivax does not work for addresses above 4G
+
+The tlbivax instruction in QEMU does not work for address above 4G. The reason behind this is a simple 32bit trunction of an address.
+Changing the argument ea from uint32_t to target_ulong for the function booke206_invalidate_ea_tlb() in target/ppc/mmu_helper.c solves the issue.
+
+I did not reproduce this using Linux so I have no public example for reproducing it. However it's a pretty straight forward change.
+
+Issue can be seen in all version of QEMU.
+
+
+This is an automated cleanup. This bug report has been moved
+to QEMU's new bug tracker on gitlab.com and thus gets marked
+as 'expired' now. Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/52
+
+