summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/graphic/2154
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/graphic/2154')
-rw-r--r--results/classifier/zero-shot/108/graphic/215422
1 files changed, 22 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/graphic/2154 b/results/classifier/zero-shot/108/graphic/2154
new file mode 100644
index 000000000..a52f29c54
--- /dev/null
+++ b/results/classifier/zero-shot/108/graphic/2154
@@ -0,0 +1,22 @@
+graphic: 0.966
+device: 0.872
+other: 0.840
+socket: 0.780
+debug: 0.770
+network: 0.746
+vnc: 0.685
+PID: 0.639
+semantic: 0.609
+performance: 0.604
+boot: 0.366
+files: 0.241
+permissions: 0.231
+KVM: 0.157
+
+ID_AA64MMFR2_EL1 is all zeros
+Description of problem:
+When the `ID_AA64MMFR2_EL1` register is read via `mrs x[n], ID_AA64MMFR2_EL1`, it is read as all zeros. This is at the very least not correct for `ID_AA64MMFR2_EL1.ST`, which describes support for small translation tables (FEAT_TTST).
+Steps to reproduce:
+1. Run `mrs x[n], ID_AA64MMFR2_EL1` within qemu-system-aarch64
+Additional information:
+FEAT_TTST is a relatively new aarch64 feature that appears to have caused many problems basically everywhere. However, [qemu has reportedly implemented it](https://www.qemu.org/2021/04/30/qemu-6-0-0/).