1 files changed, 56 insertions, 0 deletions
diff --git a/results/classifier/deepseek-1/output/hypervisor/1817846 b/results/classifier/deepseek-1/output/hypervisor/1817846
new file mode 100644
index 00000000..5d4820db
--- /dev/null
+++ b/results/classifier/deepseek-1/output/hypervisor/1817846
@@ -0,0 +1,56 @@
+
+Qemu 3.1 Aarch64 TLBI VAE1, x0
+
+Hello,
+
+In my code I'm trying to remove some permissions to a 4KiB MMU descriptor. After that I invalidate the MMU with 
+
+TLBI VAE1, x0
+
+where x0 is the start of the address of the 4 KiB page. 
+
+In Qemu 2.12 this did not work, but I worked around it with:
+
+
+    /* invalidate the address */
+    TLBI VAE1, x0
+
+
+    /*****************************************************************/
+    /*****************************************************************/
+    /* NOTE: THIS IS A TRICK FOR QEMU!!!!!!!!!!!!                                                               */
+    /* Apparently we have to change the TTBR0_EL1 when we change a descriptor (especially to remove permissions) */
+    /* Otherwise qemu (2.12) will continue with the same descriptor with permissions!                          **/
+   /*****************************************************************/
+   /*****************************************************************/
+     
+    /* do a trick (in qemu) */
+    mrs     x1 , TTBR0_EL1
+
+    ldr     x2 , =kernelTable0Table
+
+    msr     TTBR0_EL1 , x2
+
+    isb
+
+    msr     TTBR0_EL1 , x1
+
+    /* return from function */
+    ret
+
+
+That is, I just replaced the TTBR0_EL1 with a temporary value, and then restored it. (guess qemu 2.12 just needed to reload the values again).
+
+However, even this procedure is not working with qemu 3.1. (I just tested again with qemu 2.12 and the code works fine, with qemu 3.1 it does not).
+
+Thanks,
+Pharos team
+
+Could you provide a test binary (and the QEMU command line to run it) that demonstrates the bug, please?
+
+
+Marking bug as incomplete -- we can't investigate without a test case.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+