add 18th iteration of classifier

26 files changed, 1962 insertions, 0 deletions

diff --git a/results/classifier/118/architecture/1023 b/results/classifier/118/architecture/1023
new file mode 100644
index 000000000..455cfd023
--- /dev/null
+++ b/results/classifier/118/architecture/1023
@@ -0,0 +1,120 @@
+architecture: 0.828
+kernel: 0.757
+virtual: 0.754
+performance: 0.739
+graphic: 0.725
+PID: 0.718
+device: 0.712
+boot: 0.690
+network: 0.672
+debug: 0.671
+permissions: 0.670
+semantic: 0.641
+ppc: 0.632
+x86: 0.620
+hypervisor: 0.618
+socket: 0.617
+files: 0.614
+arm: 0.590
+KVM: 0.576
+user-level: 0.563
+assembly: 0.562
+register: 0.552
+risc-v: 0.508
+TCG: 0.499
+vnc: 0.441
+peripherals: 0.413
+i386: 0.377
+VMM: 0.346
+mistranslation: 0.303
+--------------------
+x86: 0.968
+debug: 0.965
+kernel: 0.932
+KVM: 0.928
+TCG: 0.914
+virtual: 0.913
+hypervisor: 0.884
+user-level: 0.240
+performance: 0.202
+files: 0.125
+architecture: 0.089
+VMM: 0.059
+register: 0.048
+boot: 0.043
+PID: 0.035
+risc-v: 0.025
+semantic: 0.023
+device: 0.020
+ppc: 0.017
+assembly: 0.009
+socket: 0.007
+network: 0.004
+graphic: 0.004
+permissions: 0.003
+peripherals: 0.003
+i386: 0.002
+vnc: 0.001
+mistranslation: 0.001
+arm: 0.000
+
+TCG & LA57 (5-level page tables) causes intermittent triple fault when setting %CR3
+Description of problem:
+Enabling LA57 (5-level page tables) + TCG causes an intermittent triple fault when the kernel loads %cr3 in preparation for jumping to protected mode.  It is quite rare, only happening on perhaps 1 in 20 runs.
+
+The observed behaviour for most users is that we see SeaBIOS messages, and no kernel messages, and qemu exits.  (Triple fault in TCG code causes qemu to reset the virtual CPU, and we are using `-no-reboot` so that causes qemu to exit).
+
+There's a simple reproducer below.  I enabled qemu -d options to capture the full instruction traces which can be found here:
+
+http://oirase.annexia.org/tmp/fullexec-failed (error case)
+http://oirase.annexia.org/tmp/fullexec-good (successful run)
+
+I also added an `abort()` into qemu after the triple fault message in order to capture a stack trace, which can be found here: https://bugzilla.redhat.com/show_bug.cgi?id=2082806#c8
+Steps to reproduce:
+1. Save the following script into a file, adjusting the two variables at the top as appropriate:
+
+```
+#!/bin/bash -
+
+# Point this to any kernel in /boot:
+kernel=/boot/vmlinuz-4.18.0-387.el8.x86_64
+
+# Point this to qemu:
+qemu=/usr/libexec/qemu-kvm
+#qemu=/home/rjones/d/qemu/build/qemu-system-x86_64
+
+log=/tmp/log
+
+cpu=max
+#cpu=max,la57=off
+
+while $qemu \
+    -global virtio-blk-pci.scsi=off \
+    -no-user-config \
+    -nodefaults \
+    -display none \
+    -machine accel=tcg,graphics=off \
+    -cpu "$cpu" \
+    -m 2048 \
+    -no-reboot \
+    -rtc driftfix=slew \
+    -no-hpet \
+    -global kvm-pit.lost_tick_policy=discard \
+    -kernel $kernel \
+    -object rng-random,filename=/dev/urandom,id=rng0 \
+    -device virtio-rng-pci,rng=rng0 \
+    -device virtio-serial-pci \
+    -serial stdio \
+    -append "panic=1 console=ttyS0" >& $log &&
+    grep -sq "Linux version" $log; do
+    echo -n .
+done
+```
+
+2. Run the script.  It will run qemu many times, checking that it reaches the kernel.
+3. Eventually the script may exit. 
+4. Check `/tmp/log` and see if you only see SeaBIOS messages.
+5. Modify the script to add `-cpu max,la57=off` and the error will stop happening.
+Additional information:
+Downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2082806
+LA57 was enabled here: https://gitlab.com/qemu-project/qemu/-/issues/661
diff --git a/results/classifier/118/architecture/1104 b/results/classifier/118/architecture/1104
new file mode 100644
index 000000000..906c731d0
--- /dev/null
+++ b/results/classifier/118/architecture/1104
@@ -0,0 +1,61 @@
+architecture: 0.947
+device: 0.817
+assembly: 0.775
+network: 0.757
+arm: 0.710
+performance: 0.662
+register: 0.370
+boot: 0.368
+files: 0.345
+debug: 0.291
+vnc: 0.276
+socket: 0.269
+virtual: 0.227
+hypervisor: 0.223
+ppc: 0.206
+peripherals: 0.191
+risc-v: 0.185
+mistranslation: 0.182
+graphic: 0.179
+permissions: 0.169
+user-level: 0.123
+semantic: 0.115
+kernel: 0.068
+x86: 0.055
+PID: 0.050
+VMM: 0.046
+TCG: 0.028
+i386: 0.025
+KVM: 0.020
+--------------------
+architecture: 0.875
+virtual: 0.059
+files: 0.047
+device: 0.035
+semantic: 0.024
+peripherals: 0.014
+assembly: 0.014
+user-level: 0.011
+kernel: 0.008
+arm: 0.004
+register: 0.004
+network: 0.004
+debug: 0.004
+graphic: 0.004
+boot: 0.003
+TCG: 0.002
+risc-v: 0.001
+VMM: 0.001
+permissions: 0.001
+hypervisor: 0.001
+performance: 0.001
+PID: 0.001
+ppc: 0.001
+socket: 0.001
+KVM: 0.000
+mistranslation: 0.000
+vnc: 0.000
+i386: 0.000
+x86: 0.000
+
+PAN support for AArch32
diff --git a/results/classifier/118/architecture/1232 b/results/classifier/118/architecture/1232
new file mode 100644
index 000000000..5611cc48b
--- /dev/null
+++ b/results/classifier/118/architecture/1232
@@ -0,0 +1,73 @@
+architecture: 0.878
+register: 0.877
+device: 0.861
+graphic: 0.796
+assembly: 0.730
+mistranslation: 0.687
+performance: 0.645
+vnc: 0.616
+PID: 0.563
+semantic: 0.563
+permissions: 0.511
+debug: 0.507
+peripherals: 0.505
+arm: 0.500
+hypervisor: 0.477
+risc-v: 0.477
+user-level: 0.466
+VMM: 0.430
+TCG: 0.415
+network: 0.409
+kernel: 0.381
+x86: 0.378
+ppc: 0.350
+i386: 0.348
+socket: 0.340
+boot: 0.284
+KVM: 0.231
+virtual: 0.210
+files: 0.153
+--------------------
+register: 0.938
+virtual: 0.937
+assembly: 0.721
+debug: 0.653
+architecture: 0.613
+hypervisor: 0.606
+boot: 0.421
+kernel: 0.284
+user-level: 0.100
+TCG: 0.070
+permissions: 0.047
+device: 0.018
+files: 0.014
+VMM: 0.010
+KVM: 0.006
+peripherals: 0.006
+arm: 0.005
+semantic: 0.005
+performance: 0.005
+risc-v: 0.004
+PID: 0.002
+network: 0.001
+vnc: 0.001
+socket: 0.001
+graphic: 0.001
+ppc: 0.001
+x86: 0.001
+mistranslation: 0.000
+i386: 0.000
+
+AArch64 virt can't write to memory related to gicv3
+Description of problem:
+According to the info in generated dtb, the memory-mapped registers of gicv3-distributor have a base addr, which is `0x0800_0000`.
+And I have checked the validity by reading `gicd_typer`, which means the base addr is right.
+
+But when I want to configure the gicv3-distributor (like changing `gicd_ctlr`), the value is not changed, keeping the default value. The same thing happens on any register of GICD in my machine.
+
+**Even I write to this memory by gdb `set` command, the value is also unchangeable.**
+
+The addr of `gicd_ctlr` should be `0x0800_0000`(offset=0), which should be readable and writable, isn't it?
+
+I try to modify the value of this addr in assembly as soon as the **machine starts, without enabling MMU**. 
+This problem should be easier to reproduce.
diff --git a/results/classifier/118/architecture/1452 b/results/classifier/118/architecture/1452
new file mode 100644
index 000000000..6ee0c5515
--- /dev/null
+++ b/results/classifier/118/architecture/1452
@@ -0,0 +1,61 @@
+architecture: 0.955
+device: 0.718
+performance: 0.620
+mistranslation: 0.410
+risc-v: 0.401
+graphic: 0.361
+network: 0.315
+TCG: 0.286
+boot: 0.279
+arm: 0.273
+semantic: 0.260
+i386: 0.260
+x86: 0.257
+files: 0.251
+PID: 0.243
+vnc: 0.220
+peripherals: 0.214
+socket: 0.173
+virtual: 0.170
+assembly: 0.167
+VMM: 0.165
+ppc: 0.150
+register: 0.138
+debug: 0.104
+permissions: 0.072
+hypervisor: 0.071
+user-level: 0.061
+KVM: 0.043
+kernel: 0.010
+--------------------
+assembly: 0.863
+x86: 0.763
+kernel: 0.704
+TCG: 0.065
+virtual: 0.057
+peripherals: 0.051
+architecture: 0.048
+user-level: 0.023
+device: 0.018
+ppc: 0.017
+i386: 0.016
+semantic: 0.016
+files: 0.011
+debug: 0.007
+VMM: 0.007
+boot: 0.005
+KVM: 0.005
+PID: 0.005
+performance: 0.002
+arm: 0.002
+risc-v: 0.002
+network: 0.001
+graphic: 0.001
+mistranslation: 0.001
+hypervisor: 0.001
+register: 0.000
+vnc: 0.000
+socket: 0.000
+permissions: 0.000
+
+Tricore: support for shuffle and syscall instruction
diff --git a/results/classifier/118/architecture/1642 b/results/classifier/118/architecture/1642
new file mode 100644
index 000000000..0fd0ba6aa
--- /dev/null
+++ b/results/classifier/118/architecture/1642
@@ -0,0 +1,82 @@
+architecture: 0.805
+graphic: 0.800
+TCG: 0.729
+performance: 0.553
+device: 0.511
+ppc: 0.496
+semantic: 0.470
+vnc: 0.384
+mistranslation: 0.382
+socket: 0.376
+network: 0.339
+kernel: 0.294
+risc-v: 0.278
+peripherals: 0.269
+arm: 0.261
+PID: 0.257
+assembly: 0.257
+boot: 0.239
+files: 0.239
+register: 0.237
+user-level: 0.229
+hypervisor: 0.218
+debug: 0.199
+permissions: 0.195
+VMM: 0.161
+x86: 0.107
+virtual: 0.096
+i386: 0.088
+KVM: 0.077
+--------------------
+debug: 0.965
+TCG: 0.902
+hypervisor: 0.749
+assembly: 0.157
+virtual: 0.122
+arm: 0.098
+performance: 0.061
+register: 0.054
+files: 0.052
+architecture: 0.047
+kernel: 0.031
+PID: 0.027
+user-level: 0.014
+VMM: 0.011
+semantic: 0.009
+device: 0.007
+risc-v: 0.005
+boot: 0.003
+KVM: 0.003
+ppc: 0.003
+peripherals: 0.002
+vnc: 0.002
+graphic: 0.002
+x86: 0.002
+network: 0.002
+socket: 0.001
+i386: 0.001
+permissions: 0.001
+mistranslation: 0.001
+
+Qemu aarch64 tcg crashes when emulating an STXP instruction but only on a Windows host
+Description of problem:
+Qemu segfaults when trying to emulate an STXP instruction, but only when running natively on a windows host (msys2 build). This is not the same as https://gitlab.com/qemu-project/qemu/-/issues/1581.
+
+I've managed to git-bisect it to this change: https://github.com/qemu/qemu/commit/546789c7df8866c55cae8d3195e8e58328a35d51
+Sadly i cannot investigate it further and contribute a fix, but it seems like a problem with one of the I128 arguments to `helper_atomic_cmpxchgo_le `
+
+UPD: Issue is also in master (as of `caa9cbd566877b34e9abcc04d936116fc5e0ab28`)
+Steps to reproduce:
+N/A
+Additional information:
+```
+Thread 9 received signal SIGSEGV, Segmentation fault.
+0x00007ff67efc32dc in helper_atomic_cmpxchgo_le (env=0x24796b08c10, addr=18446684150325987376, oldv=46236672343829145701101521005152, newv=2595395441251766838621186119693696, oi=3650) at ../accel/tcg/atomic_common.c.inc:60
+60      CMPXCHG_HELPER(cmpxchgo_le, Int128)
+(gdb) bt
+#0  0x00007ff67efc32dc in helper_atomic_cmpxchgo_le (env=0x24796b08c10,
+    addr=18446684150325987376, oldv=46236672343829145701101521005152,
+    newv=2595395441251766838621186119693696, oi=3650) at ../accel/tcg/atomic_common.c.inc:60
+#1  0x00000247a124f73d in ?? ()
+
+```
diff --git a/results/classifier/118/architecture/1790 b/results/classifier/118/architecture/1790
new file mode 100644
index 000000000..647ca44c2
--- /dev/null
+++ b/results/classifier/118/architecture/1790
@@ -0,0 +1,89 @@
+architecture: 0.981
+register: 0.894
+performance: 0.860
+graphic: 0.821
+boot: 0.809
+semantic: 0.738
+device: 0.730
+TCG: 0.709
+arm: 0.707
+debug: 0.680
+mistranslation: 0.585
+assembly: 0.543
+ppc: 0.530
+network: 0.505
+vnc: 0.500
+x86: 0.499
+PID: 0.491
+files: 0.488
+risc-v: 0.474
+VMM: 0.455
+i386: 0.438
+peripherals: 0.433
+socket: 0.425
+user-level: 0.405
+permissions: 0.396
+virtual: 0.366
+hypervisor: 0.216
+kernel: 0.162
+KVM: 0.068
+--------------------
+arm: 0.958
+TCG: 0.864
+boot: 0.835
+debug: 0.762
+kernel: 0.489
+architecture: 0.476
+assembly: 0.220
+files: 0.161
+register: 0.111
+semantic: 0.089
+performance: 0.024
+user-level: 0.021
+PID: 0.019
+hypervisor: 0.017
+device: 0.015
+VMM: 0.010
+KVM: 0.008
+virtual: 0.008
+risc-v: 0.007
+socket: 0.005
+vnc: 0.004
+ppc: 0.004
+peripherals: 0.003
+permissions: 0.002
+network: 0.002
+graphic: 0.001
+x86: 0.001
+mistranslation: 0.001
+i386: 0.001
+
+[AARCH64] STGP instruction is not writing the value of the second register to memory
+Description of problem:
+My application is built with Clang 16 and the option -fsanitize=memtag-stack.
+It means the the MTE protection is activated for the stack.
+The local variables are tagged and the compiler is often using the STGP instruction "Store Allocation Tag and Pair of registers" in order to transfer the value of two 64-bit registers to memory.
+The following instruction was not working as expected:
+   18004: 69000895     	stgp	x21, x2, [x4]
+The value of the second register x2 is not transferred to the memory.
+Only x21 is written.
+
+I think that the issue is in trans_STGP().
+We don't call finalize_memop_pair() like we do for in the general trans_STP().
+
+```
+diff --git a/target/arm/tcg/translate-a64.c b/target/arm/tcg/translate-a64.c
+index 7d0c8f79a7..f599f3e136 100644
+--- a/target/arm/tcg/translate-a64.c
++++ b/target/arm/tcg/translate-a64.c
+@@ -3034,6 +3034,8 @@ static bool trans_STGP(DisasContext *s, arg_ldstpair *a)
+ 
+     tcg_rt = cpu_reg(s, a->rt);
+     tcg_rt2 = cpu_reg(s, a->rt2);
++    mop = a->sz + 1;
++    mop = finalize_memop_pair(s, mop);
+ 
+     assert(a->sz == 3);
+```
+
+With this fix, my OS (Kinibi) is now able to boot.
diff --git a/results/classifier/118/architecture/1813305 b/results/classifier/118/architecture/1813305
new file mode 100644
index 000000000..15a514d95
--- /dev/null
+++ b/results/classifier/118/architecture/1813305
@@ -0,0 +1,122 @@
+architecture: 0.868
+semantic: 0.858
+performance: 0.846
+kernel: 0.835
+mistranslation: 0.826
+hypervisor: 0.814
+user-level: 0.802
+register: 0.798
+device: 0.796
+files: 0.781
+arm: 0.772
+permissions: 0.760
+ppc: 0.758
+PID: 0.757
+VMM: 0.748
+socket: 0.735
+KVM: 0.735
+risc-v: 0.734
+peripherals: 0.717
+vnc: 0.713
+x86: 0.710
+boot: 0.707
+network: 0.686
+assembly: 0.657
+i386: 0.643
+TCG: 0.638
+debug: 0.597
+graphic: 0.566
+virtual: 0.439
+--------------------
+user-level: 0.968
+arm: 0.911
+register: 0.353
+hypervisor: 0.279
+TCG: 0.273
+kernel: 0.266
+files: 0.188
+device: 0.113
+VMM: 0.109
+socket: 0.108
+debug: 0.104
+performance: 0.076
+PID: 0.071
+network: 0.071
+KVM: 0.062
+virtual: 0.051
+semantic: 0.047
+risc-v: 0.042
+architecture: 0.030
+boot: 0.029
+vnc: 0.024
+peripherals: 0.022
+ppc: 0.021
+permissions: 0.018
+x86: 0.014
+i386: 0.008
+assembly: 0.003
+graphic: 0.002
+mistranslation: 0.001
+
+trace-root.h is not regerenerated after re-configure
+
+Hi,
+
+I've just realized that after I reconfigured my qemu with
+../configure --target-list=arm-softmmu,arm-linux-user,aarch64-softmmu,aarch64-linux-user --enable-trace-backends=simple
+
+$ make
+did rebuild some stuff for the 'simple' trace, but it did not update trace-root.h until after I
+$ make clean
+
+
+I took me while to understand why I didn't get the traces I wanted (my trace-root.h still thought it was configured for the default 'log').
+
+I didn't check how easy it is to fix this in the build system.
+
+Thanks
+
+On Fri, Jan 25, 2019 at 02:03:39PM -0000, Christophe Lyon wrote:
+> I've just realized that after I reconfigured my qemu with
+> ../configure --target-list=arm-softmmu,arm-linux-user,aarch64-softmmu,aarch64-linux-user --enable-trace-backends=simple
+> 
+> $ make
+> did rebuild some stuff for the 'simple' trace, but it did not update trace-root.h until after I
+> $ make clean
+> 
+> 
+> I took me while to understand why I didn't get the traces I wanted (my trace-root.h still thought it was configured for the default 'log').
+> 
+> I didn't check how easy it is to fix this in the build system.
+
+Thank you for reporting this.  I have sent a patch to fix the makefile.
+
+Stefan
+
+
+On Tue, 29 Jan 2019 at 03:55, Stefan Hajnoczi <email address hidden> wrote:
+>
+> On Fri, Jan 25, 2019 at 02:03:39PM -0000, Christophe Lyon wrote:
+> > I've just realized that after I reconfigured my qemu with
+> > ../configure --target-list=arm-softmmu,arm-linux-user,aarch64-softmmu,aarch64-linux-user --enable-trace-backends=simple
+> >
+> > $ make
+> > did rebuild some stuff for the 'simple' trace, but it did not update trace-root.h until after I
+> > $ make clean
+> >
+> >
+> > I took me while to understand why I didn't get the traces I wanted (my trace-root.h still thought it was configured for the default 'log').
+> >
+> > I didn't check how easy it is to fix this in the build system.
+>
+> Thank you for reporting this.  I have sent a patch to fix the makefile.
+>
+
+Thanks for the quick patch.
+
+> Stefan
+
+
+This was fixed by commit 57b7bdf426445d83561, which will be in the 4.0 release.
+
+
diff --git a/results/classifier/118/architecture/1892441 b/results/classifier/118/architecture/1892441
new file mode 100644
index 000000000..68da7c03a
--- /dev/null
+++ b/results/classifier/118/architecture/1892441
@@ -0,0 +1,104 @@
+architecture: 0.889
+graphic: 0.778
+boot: 0.744
+ppc: 0.735
+device: 0.729
+user-level: 0.724
+performance: 0.715
+peripherals: 0.702
+virtual: 0.677
+PID: 0.665
+assembly: 0.657
+x86: 0.644
+vnc: 0.621
+semantic: 0.592
+files: 0.579
+permissions: 0.579
+VMM: 0.575
+kernel: 0.564
+mistranslation: 0.553
+hypervisor: 0.514
+register: 0.498
+socket: 0.490
+debug: 0.487
+network: 0.482
+TCG: 0.440
+risc-v: 0.427
+arm: 0.379
+i386: 0.316
+KVM: 0.284
+--------------------
+virtual: 0.952
+user-level: 0.878
+hypervisor: 0.121
+architecture: 0.106
+boot: 0.091
+TCG: 0.081
+files: 0.056
+register: 0.056
+debug: 0.053
+VMM: 0.053
+PID: 0.034
+network: 0.026
+kernel: 0.022
+socket: 0.020
+device: 0.019
+semantic: 0.017
+permissions: 0.004
+performance: 0.004
+risc-v: 0.004
+graphic: 0.004
+peripherals: 0.003
+assembly: 0.003
+KVM: 0.003
+vnc: 0.002
+mistranslation: 0.001
+ppc: 0.001
+x86: 0.001
+i386: 0.000
+arm: 0.000
+
+"No zIPL section in IPL2 record" error when emulating Debian 10.5.0 on s390x
+
+Hi,
+
+I want to emulate Debian 10.5.0 for the s390x architecture. 
+The Debian image is downloaded from the following link:
+https://cdimage.debian.org/debian-cd/current/s390x/iso-cd/debian-10.5.0-s390x-netinst.iso 
+
+Using the latest QEMU version 5.1.0, running the debian image using the given command:
+qemu-system-s390x -boot d -m 4096 -hda debian.qcow -cdrom debian-10.5.0-s390x-netinst.iso -nographic
+
+causes the error output below:
+
+LOADPARM=[        ]
+Using virtio-blk.
+Using guessed DASD geometry.
+Using ECKD scheme (block size  4096), CDL
+
+! No zIPL section in IPL2 record. !
+
+As far as I know, the Debian CD ISO images are not bootable on s390x (they do not contain boot information according to the El-Torrito standard). Please open a bug against Debian instead if you want to have that changed. So far, you have to boot here manually instead (see http://people.redhat.com/~thuth/blog/qemu/2017/12/19/install-fedora.html for some more information).
+
+
+Yes. For booting Debian images using QEMU (<= 5.0.0) I use this recipe:
+
+machine_args="-M s390-ccw-virtio -m 512"
+disk_args="-drive file=debian86.img,if=none,format=raw,id=hd0 -device virtio-blk-ccw,drive=hd0"
+net_args=""
+display_args="-display gtk -monitor stdio"
+common_args="$machine_args $disk_args $net_args $display_args"
+
+Pull kernel and initrd from the ftp server:
+mkdir boot-for-install
+(cd boot-for-install
+ wget ftp://ftp.de.debian.org/pub/debian/dists/jessie/main/installer-s390x/current/images/generic/kernel.debian
+ wget ftp://ftp.de.debian.org/pub/debian/dists/jessie/main/installer-s390x/current/images/generic/initrd.debian)
+
+Then, for running the installer:
+qemu-system-s390x $common_args -kernel boot-for-install/kernel.debian -initrd boot-for-install/initrd.debian
+
+For booting from disk:
+qemu-system-s390x $common_args -kernel boot/vmlinuz -initrd boot/initrd.img -append "root=/dev/vda2"
+
+
diff --git a/results/classifier/118/architecture/1906156 b/results/classifier/118/architecture/1906156
new file mode 100644
index 000000000..f7ca850ca
--- /dev/null
+++ b/results/classifier/118/architecture/1906156
@@ -0,0 +1,115 @@
+architecture: 0.836
+semantic: 0.830
+virtual: 0.811
+peripherals: 0.795
+debug: 0.758
+PID: 0.755
+performance: 0.745
+hypervisor: 0.739
+permissions: 0.732
+device: 0.730
+boot: 0.689
+user-level: 0.684
+ppc: 0.674
+graphic: 0.635
+x86: 0.632
+mistranslation: 0.615
+arm: 0.609
+socket: 0.607
+register: 0.595
+files: 0.559
+risc-v: 0.557
+assembly: 0.533
+vnc: 0.531
+KVM: 0.521
+TCG: 0.440
+network: 0.423
+VMM: 0.401
+i386: 0.255
+kernel: 0.148
+--------------------
+virtual: 0.975
+user-level: 0.913
+x86: 0.622
+debug: 0.293
+TCG: 0.240
+hypervisor: 0.100
+VMM: 0.052
+socket: 0.034
+files: 0.029
+register: 0.027
+PID: 0.026
+kernel: 0.026
+boot: 0.016
+network: 0.011
+risc-v: 0.010
+semantic: 0.007
+vnc: 0.007
+device: 0.007
+performance: 0.005
+arm: 0.004
+architecture: 0.003
+ppc: 0.002
+peripherals: 0.002
+KVM: 0.002
+graphic: 0.001
+assembly: 0.001
+permissions: 0.001
+mistranslation: 0.001
+i386: 0.001
+
+Host OS Reboot Required, for Guest kext to Load (Fully)
+
+Hi,
+
+Finding this one a bit odd, but I am loading a driver (kext) in a macOS guest ... and it works, on the first VM (domain) startup after a full / clean host OS boot (or reboot). However, if I even reboot the guest OS, then the driver load fails => can be "corrected" by a full host OS reboot (which seems very extreme).
+
+Is this a known issue, and/or is there a workaround?
+
+FYI, running,
+QEMU emulator version 5.0.0 (Debian 1:5.0-5ubuntu9.1)
+Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
+
+This is for a macOS guest, on a Linux host.
+
+Thanks!
+
+Hi! Seems like you're using the QEMU from your distro, so should this be a bug report against Ubuntu's QEMU instead? Otherwise, can you please try again with the latest upstream version of QEMU (currently an RC of v5.2)? You certainly also need to provide more information, e.g. what kind of error message do you see, how often did you try (maybe it's just an intermittent problem and it sometimes also works without rebooting the host), etc.
+
+Sure, will do (upstream version). Is there a preferred way to do it? Meaning ... build locally, or install from some repository?
+
+Thanks!
+
+The QEMU project only provides the source tarballs, so builing locally is certainly the preferred way to test.
+
+That makes sense, no issue at all. So I cloned from git (v5.2.0-rc3), built, installed. All good so far :-). But then I tried to modify the "emulator" in virt-manager, point to this build => I get the error,
+
+Error changing VM configuration: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt:  error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied
+
+Thoughts? I have run into this before (without finding a fix sadly) - thinking it's apparmor related somehow?
+
+Thanks!
+
+Sorry for the delay on updating this - but pulling my hair out (and I'm short enough of that already ... LOL). I can't get Ubuntu to let me run the custom qemu executable. Really is looking like apparmor. Fighting with that, but struggling to have it let me run it :-(.
+
+Thanks.
+
+My apologies, but I'm somewhat stuck here :-(. Trying to run the latest (upstream) version of QEMU, but no luck getting it to execute. I even tried setting securit_driver = "none", as captured here,
+https://gitlab.com/apparmor/apparmor/-/wikis/Libvirt
+
+But no luck. Open to any suggestions.
+
+Thanks!
+
+OK, found my issue! :-). Still a bit odd, but virt-manager complaints about the custom QEMU executable => but virsh still works. So I did get the VM running, with,
+QEMU emulator version 5.1.93 (v5.2.0-rc3)
+Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
+
+But it still performed the same. I also checked the xml file (VM definition), and made sure to change the machine to the most current version (pc-q35-5.2), but also no improvement.
+
+Other things to try?
+
+Thanks!
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/118/architecture/2066 b/results/classifier/118/architecture/2066
new file mode 100644
index 000000000..31d48ee0b
--- /dev/null
+++ b/results/classifier/118/architecture/2066
@@ -0,0 +1,61 @@
+architecture: 0.942
+peripherals: 0.768
+device: 0.763
+hypervisor: 0.683
+arm: 0.670
+virtual: 0.612
+network: 0.471
+VMM: 0.333
+performance: 0.300
+boot: 0.299
+risc-v: 0.280
+vnc: 0.248
+register: 0.226
+socket: 0.215
+semantic: 0.204
+graphic: 0.197
+mistranslation: 0.167
+debug: 0.160
+files: 0.133
+permissions: 0.125
+PID: 0.120
+ppc: 0.113
+kernel: 0.093
+TCG: 0.078
+assembly: 0.034
+user-level: 0.023
+x86: 0.007
+i386: 0.006
+KVM: 0.003
+--------------------
+user-level: 0.894
+peripherals: 0.883
+arm: 0.817
+virtual: 0.797
+hypervisor: 0.723
+VMM: 0.639
+register: 0.371
+assembly: 0.034
+TCG: 0.025
+device: 0.023
+files: 0.020
+kernel: 0.013
+architecture: 0.012
+semantic: 0.011
+socket: 0.008
+debug: 0.005
+risc-v: 0.004
+permissions: 0.001
+graphic: 0.001
+boot: 0.001
+KVM: 0.001
+network: 0.001
+ppc: 0.000
+vnc: 0.000
+PID: 0.000
+performance: 0.000
+x86: 0.000
+mistranslation: 0.000
+i386: 0.000
+
+Feature Request: UART 8250 Support in QEMU Virt Machine for aarch64
diff --git a/results/classifier/118/architecture/2098 b/results/classifier/118/architecture/2098
new file mode 100644
index 000000000..53fdbe0ce
--- /dev/null
+++ b/results/classifier/118/architecture/2098
@@ -0,0 +1,61 @@
+architecture: 0.972
+arm: 0.793
+device: 0.589
+network: 0.538
+virtual: 0.506
+semantic: 0.459
+performance: 0.417
+mistranslation: 0.373
+graphic: 0.298
+peripherals: 0.290
+kernel: 0.237
+user-level: 0.224
+socket: 0.211
+register: 0.188
+debug: 0.187
+boot: 0.185
+assembly: 0.159
+ppc: 0.148
+TCG: 0.147
+hypervisor: 0.135
+risc-v: 0.095
+permissions: 0.091
+i386: 0.080
+files: 0.070
+PID: 0.065
+KVM: 0.039
+x86: 0.035
+VMM: 0.014
+vnc: 0.011
+--------------------
+arm: 0.996
+architecture: 0.977
+semantic: 0.131
+device: 0.069
+kernel: 0.024
+virtual: 0.024
+assembly: 0.015
+TCG: 0.012
+register: 0.011
+performance: 0.010
+socket: 0.009
+files: 0.008
+permissions: 0.006
+VMM: 0.005
+boot: 0.004
+debug: 0.004
+hypervisor: 0.003
+PID: 0.003
+user-level: 0.003
+risc-v: 0.003
+peripherals: 0.002
+graphic: 0.001
+KVM: 0.001
+vnc: 0.001
+mistranslation: 0.001
+ppc: 0.001
+network: 0.000
+i386: 0.000
+x86: 0.000
+
+AArch32 Arm CPUs no longer support the 'vfp' property
diff --git a/results/classifier/118/architecture/2112 b/results/classifier/118/architecture/2112
new file mode 100644
index 000000000..6dd1ae70f
--- /dev/null
+++ b/results/classifier/118/architecture/2112
@@ -0,0 +1,86 @@
+architecture: 0.862
+device: 0.833
+semantic: 0.790
+socket: 0.714
+vnc: 0.686
+ppc: 0.684
+network: 0.639
+files: 0.621
+debug: 0.613
+kernel: 0.605
+arm: 0.599
+graphic: 0.599
+user-level: 0.585
+hypervisor: 0.560
+PID: 0.552
+performance: 0.550
+x86: 0.544
+risc-v: 0.535
+register: 0.483
+i386: 0.480
+permissions: 0.467
+VMM: 0.464
+boot: 0.456
+TCG: 0.446
+virtual: 0.418
+KVM: 0.378
+peripherals: 0.363
+assembly: 0.257
+mistranslation: 0.218
+--------------------
+user-level: 0.993
+debug: 0.719
+TCG: 0.308
+virtual: 0.190
+PID: 0.087
+architecture: 0.084
+semantic: 0.067
+register: 0.050
+files: 0.034
+network: 0.027
+performance: 0.016
+kernel: 0.012
+hypervisor: 0.010
+device: 0.009
+VMM: 0.009
+vnc: 0.005
+peripherals: 0.005
+assembly: 0.004
+risc-v: 0.004
+permissions: 0.004
+boot: 0.003
+socket: 0.003
+graphic: 0.003
+x86: 0.002
+KVM: 0.001
+arm: 0.001
+ppc: 0.001
+i386: 0.001
+mistranslation: 0.001
+
+Limited Support for MIPS clone syscall in QEMU User Mode
+Description of problem:
+Hello,
+
+I have been working with QEMU user mode to run programs based on the MIPS architecture and have encountered a limitation regarding the support for the MIPS clone syscall in the current implementation of QEMU user mode. Specifically, when invoking the clone syscall with certain flags, it results in the error "errno=22 (Invalid argument)" due to the absence of corresponding handling code in QEMU.
+
+Upon further investigation, I pinpointed the probable cause. QEMU user mode appears to check if the flags for the clone syscall include all the flags defined in CLONE_THREAD_FLAGS. If there is a mismatch, it returns "-TARGET_EINVAL".
+
+[source code](https://gitlab.com/qemu-project/qemu/-/blob/master/linux-user/syscall.c?ref_type=heads#L6564)
+
+The current CLONE_THREAD_FLAGS in QEMU are set to include: (CLONE_VM | CLONE_FS | CLONE_FILES | CLONE_SIGHAND | CLONE_THREAD | CLONE_SYSVSEM).
+
+However, in my MIPS program, the flags are only: (CLONE_VM | CLONE_FS | CLONE_FILES | CLONE_SIGHAND).
+
+Aligning my MIPS program to include all the flags as per CLONE_THREAD_FLAGS alters the clone syscall's behavior, deviating from the original semantics required by my MIPS program.
+
+I am seeking guidance on whether there is a way in QEMU user mode's MIPS syscall handling to exclusively use the flags (CLONE_VM | CLONE_FS | CLONE_FILES | CLONE_SIGHAND). Alternatively, I am interested in any possible approach to enable support for the MIPS architecture's clone syscall in QEMU user mode.
+
+Thank you for your time and assistance.
+Steps to reproduce:
+1. Write a C program that utilizes the clone function, specifying the flags as: CLONE_VM | CLONE_FS | CLONE_FILES | CLONE_SIGHAND.
+
+strace output: 
+```
+clone(CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND,child_stack=0x009359a8,parent_tidptr=0x00000f00,tls=0x00000003,child_tidptr=0x2b36d510) = -1 errno=22 (Invalid argument)
+```
diff --git a/results/classifier/118/architecture/2163 b/results/classifier/118/architecture/2163
new file mode 100644
index 000000000..1f90c0b06
--- /dev/null
+++ b/results/classifier/118/architecture/2163
@@ -0,0 +1,61 @@
+architecture: 0.975
+semantic: 0.801
+performance: 0.712
+debug: 0.679
+mistranslation: 0.607
+graphic: 0.548
+device: 0.447
+boot: 0.322
+virtual: 0.199
+permissions: 0.195
+assembly: 0.123
+VMM: 0.084
+risc-v: 0.067
+peripherals: 0.063
+arm: 0.059
+PID: 0.053
+hypervisor: 0.046
+register: 0.041
+vnc: 0.032
+TCG: 0.025
+ppc: 0.016
+files: 0.013
+network: 0.010
+socket: 0.004
+kernel: 0.003
+user-level: 0.002
+i386: 0.001
+x86: 0.001
+KVM: 0.001
+--------------------
+architecture: 0.891
+kernel: 0.305
+assembly: 0.199
+VMM: 0.097
+PID: 0.087
+files: 0.069
+semantic: 0.041
+performance: 0.039
+device: 0.039
+TCG: 0.033
+KVM: 0.017
+socket: 0.017
+debug: 0.013
+register: 0.012
+virtual: 0.010
+risc-v: 0.006
+hypervisor: 0.005
+graphic: 0.003
+boot: 0.002
+peripherals: 0.002
+user-level: 0.001
+vnc: 0.001
+mistranslation: 0.001
+ppc: 0.001
+network: 0.000
+permissions: 0.000
+arm: 0.000
+x86: 0.000
+i386: 0.000
+
+Move architecture specific interruption code around SPARC CPUs from hw/sparc/ to target/sparc/
diff --git a/results/classifier/118/architecture/2270 b/results/classifier/118/architecture/2270
new file mode 100644
index 000000000..a7bb9e293
--- /dev/null
+++ b/results/classifier/118/architecture/2270
@@ -0,0 +1,61 @@
+architecture: 0.971
+device: 0.604
+performance: 0.471
+graphic: 0.460
+boot: 0.351
+risc-v: 0.321
+arm: 0.294
+TCG: 0.279
+vnc: 0.252
+ppc: 0.204
+debug: 0.170
+mistranslation: 0.148
+PID: 0.134
+register: 0.106
+VMM: 0.092
+permissions: 0.062
+x86: 0.055
+virtual: 0.049
+socket: 0.028
+semantic: 0.021
+network: 0.011
+kernel: 0.009
+user-level: 0.005
+files: 0.004
+hypervisor: 0.004
+assembly: 0.004
+KVM: 0.003
+i386: 0.002
+peripherals: 0.001
+--------------------
+architecture: 0.929
+x86: 0.579
+device: 0.232
+PID: 0.133
+TCG: 0.121
+register: 0.072
+VMM: 0.058
+socket: 0.047
+risc-v: 0.041
+debug: 0.032
+virtual: 0.028
+ppc: 0.022
+kernel: 0.021
+files: 0.018
+user-level: 0.017
+semantic: 0.016
+graphic: 0.014
+KVM: 0.009
+assembly: 0.005
+performance: 0.005
+boot: 0.003
+hypervisor: 0.003
+arm: 0.003
+i386: 0.003
+network: 0.002
+peripherals: 0.002
+vnc: 0.002
+permissions: 0.001
+mistranslation: 0.000
+
+CPU topology recognition for Ryzen 9 7950X3D
diff --git a/results/classifier/118/architecture/2506 b/results/classifier/118/architecture/2506
new file mode 100644
index 000000000..f3292cc1c
--- /dev/null
+++ b/results/classifier/118/architecture/2506
@@ -0,0 +1,118 @@
+architecture: 0.966
+graphic: 0.910
+user-level: 0.909
+performance: 0.889
+permissions: 0.885
+files: 0.856
+device: 0.822
+risc-v: 0.798
+network: 0.784
+hypervisor: 0.782
+ppc: 0.764
+PID: 0.753
+kernel: 0.740
+peripherals: 0.730
+vnc: 0.723
+x86: 0.716
+socket: 0.668
+VMM: 0.666
+KVM: 0.656
+i386: 0.655
+TCG: 0.644
+semantic: 0.641
+arm: 0.634
+boot: 0.565
+mistranslation: 0.538
+debug: 0.510
+assembly: 0.498
+register: 0.474
+virtual: 0.307
+--------------------
+user-level: 0.965
+hypervisor: 0.843
+debug: 0.485
+TCG: 0.207
+files: 0.122
+arm: 0.097
+kernel: 0.090
+virtual: 0.050
+register: 0.036
+PID: 0.023
+architecture: 0.012
+semantic: 0.010
+device: 0.009
+ppc: 0.007
+performance: 0.006
+VMM: 0.006
+network: 0.005
+boot: 0.004
+assembly: 0.004
+socket: 0.003
+risc-v: 0.003
+x86: 0.003
+KVM: 0.003
+peripherals: 0.003
+permissions: 0.002
+graphic: 0.002
+i386: 0.001
+vnc: 0.001
+mistranslation: 0.001
+
+LC_RPATH stripped despite setting INSTALL_REMOVE_ENVIRONMENT_RPATH=FALSE
+Description of problem:
+When I try to run qemu, I get the following output:
+> dyld[93165]: Library not loaded: @rpath/libjpeg.62.dylib
+>   Referenced from: <85BC1FBA-CA2E-3CAC-9ABF-E5330AC86CAF> /Users/mj/local/bin/qemu-system-aarch64
+>   Reason: no LC_RPATH's found
+Steps to reproduce:
+If the qemu-9.0.2 folder is present, remove it:
+```
+$ rm -rf qemu-9.0.2
+```
+Create the source folder:
+```
+$ tar xzf qemu-9.0.2.tar.xz
+$ cd qemu-9.0.2
+```
+
+Make sure the following environment variables are set:
+```
+$ export CC=clang
+$ export LDFLAGS="-rpath $HOME/local/lib"
+$ export INSTALL_REMOVE_ENVIRONMENT_RPATH=FALSE
+```
+
+Configure as follows:
+```
+$ ./configure --prefix=$HOME/local --disable-sdl --enable-slirp --enable-fdt=internal --enable-spice
+```
+
+Build
+```
+$ make -j 10
+```
+
+Note there are a large number of linker warnings like this:
+> ld: warning: duplicate -rpath '/Users/mj/local/lib' ignored
+
+Execute this:
+```
+$ otool -l build/qemu-system-aarch64 | grep LC_RPATH -A2
+```
+
+See this output
+>          cmd LC_RPATH
+>      cmdsize 32
+>         path /Users/mj/local/lib (offset 12) 
+
+Change directory to $HOME/local/bin & execute:
+```
+$ otool -l qemu-system-aarch64 | grep LC_RPATH -A2
+```
+
+The output is now empty - the LC_RPATH has been stripped by the install.  This results in the failure to execute the resulting binary.  Note, I tried using install_name_tool to add the RPATH, but it warned me this changed the signature of the file, and it would not run.
+
+Executing qemu-system-aarch64 produces the following:
+>  dyld[93165]: Library not loaded: @rpath/libjpeg.62.dylib
+>    Referenced from: <85BC1FBA-CA2E-3CAC-9ABF-E5330AC86CAF> /Users/mj/local/bin/qemu-system-aarch64
+>    Reason: no LC_RPATH's found
diff --git a/results/classifier/118/architecture/2568 b/results/classifier/118/architecture/2568
new file mode 100644
index 000000000..6f0910589
--- /dev/null
+++ b/results/classifier/118/architecture/2568
@@ -0,0 +1,61 @@
+architecture: 0.944
+device: 0.630
+network: 0.603
+peripherals: 0.515
+permissions: 0.444
+hypervisor: 0.421
+arm: 0.420
+graphic: 0.371
+files: 0.351
+performance: 0.333
+semantic: 0.293
+socket: 0.178
+register: 0.177
+kernel: 0.152
+debug: 0.136
+assembly: 0.125
+boot: 0.114
+mistranslation: 0.104
+virtual: 0.102
+ppc: 0.089
+vnc: 0.067
+user-level: 0.059
+risc-v: 0.044
+VMM: 0.033
+PID: 0.030
+TCG: 0.024
+x86: 0.017
+KVM: 0.013
+i386: 0.008
+--------------------
+arm: 0.979
+architecture: 0.967
+kernel: 0.367
+assembly: 0.302
+hypervisor: 0.290
+permissions: 0.257
+debug: 0.192
+device: 0.179
+files: 0.132
+semantic: 0.033
+peripherals: 0.031
+virtual: 0.028
+register: 0.014
+risc-v: 0.012
+TCG: 0.008
+network: 0.006
+performance: 0.006
+user-level: 0.006
+boot: 0.005
+socket: 0.004
+VMM: 0.003
+PID: 0.002
+graphic: 0.002
+KVM: 0.002
+ppc: 0.001
+vnc: 0.001
+mistranslation: 0.001
+i386: 0.000
+x86: 0.000
+
+[AARCH64] HPFAR_EL2.NS not set for non secure read in S-EL1
diff --git a/results/classifier/118/architecture/263 b/results/classifier/118/architecture/263
new file mode 100644
index 000000000..2f1db5993
--- /dev/null
+++ b/results/classifier/118/architecture/263
@@ -0,0 +1,61 @@
+architecture: 0.841
+device: 0.824
+performance: 0.773
+user-level: 0.749
+arm: 0.648
+network: 0.601
+files: 0.372
+graphic: 0.316
+socket: 0.277
+PID: 0.253
+semantic: 0.233
+boot: 0.221
+debug: 0.218
+TCG: 0.209
+vnc: 0.193
+risc-v: 0.189
+peripherals: 0.140
+register: 0.129
+virtual: 0.122
+i386: 0.113
+mistranslation: 0.107
+x86: 0.090
+permissions: 0.062
+VMM: 0.054
+kernel: 0.050
+assembly: 0.039
+ppc: 0.017
+hypervisor: 0.011
+KVM: 0.009
+--------------------
+user-level: 0.948
+files: 0.894
+i386: 0.890
+virtual: 0.856
+x86: 0.794
+hypervisor: 0.556
+performance: 0.082
+debug: 0.069
+architecture: 0.027
+ppc: 0.024
+TCG: 0.016
+KVM: 0.015
+kernel: 0.011
+register: 0.008
+semantic: 0.007
+VMM: 0.006
+device: 0.006
+assembly: 0.005
+arm: 0.002
+risc-v: 0.001
+graphic: 0.001
+peripherals: 0.001
+PID: 0.001
+boot: 0.001
+network: 0.000
+socket: 0.000
+mistranslation: 0.000
+vnc: 0.000
+permissions: 0.000
+
+readdir() returns NULL (errno=EOVERFLOW) for 32-bit user-static qemu on 64-bit host
diff --git a/results/classifier/118/architecture/2652 b/results/classifier/118/architecture/2652
new file mode 100644
index 000000000..f6de7457e
--- /dev/null
+++ b/results/classifier/118/architecture/2652
@@ -0,0 +1,61 @@
+architecture: 0.976
+user-level: 0.922
+permissions: 0.916
+device: 0.801
+performance: 0.740
+arm: 0.548
+boot: 0.420
+graphic: 0.393
+semantic: 0.375
+mistranslation: 0.339
+register: 0.256
+VMM: 0.253
+debug: 0.209
+PID: 0.209
+virtual: 0.151
+TCG: 0.109
+vnc: 0.100
+ppc: 0.077
+risc-v: 0.062
+hypervisor: 0.044
+kernel: 0.039
+files: 0.033
+socket: 0.033
+network: 0.029
+assembly: 0.028
+KVM: 0.014
+peripherals: 0.007
+x86: 0.004
+i386: 0.003
+--------------------
+virtual: 0.982
+user-level: 0.981
+permissions: 0.931
+hypervisor: 0.922
+architecture: 0.761
+KVM: 0.058
+semantic: 0.020
+TCG: 0.010
+register: 0.009
+device: 0.008
+arm: 0.007
+boot: 0.006
+files: 0.005
+VMM: 0.004
+kernel: 0.003
+PID: 0.003
+debug: 0.002
+assembly: 0.002
+performance: 0.001
+graphic: 0.001
+risc-v: 0.001
+socket: 0.001
+mistranslation: 0.000
+ppc: 0.000
+peripherals: 0.000
+i386: 0.000
+x86: 0.000
+network: 0.000
+vnc: 0.000
+
+qemu-user please allow to emulate aarch64 cpu in 32bits mode
diff --git a/results/classifier/118/architecture/2715 b/results/classifier/118/architecture/2715
new file mode 100644
index 000000000..98bb948a7
--- /dev/null
+++ b/results/classifier/118/architecture/2715
@@ -0,0 +1,61 @@
+architecture: 0.967
+device: 0.834
+network: 0.697
+arm: 0.652
+boot: 0.485
+performance: 0.451
+hypervisor: 0.413
+register: 0.400
+socket: 0.393
+files: 0.381
+mistranslation: 0.378
+risc-v: 0.355
+kernel: 0.305
+graphic: 0.304
+permissions: 0.288
+semantic: 0.245
+vnc: 0.236
+VMM: 0.206
+PID: 0.193
+peripherals: 0.188
+ppc: 0.182
+TCG: 0.179
+virtual: 0.124
+debug: 0.105
+assembly: 0.089
+user-level: 0.055
+KVM: 0.024
+x86: 0.021
+i386: 0.015
+--------------------
+architecture: 0.936
+virtual: 0.930
+hypervisor: 0.903
+kernel: 0.046
+semantic: 0.034
+user-level: 0.031
+device: 0.024
+assembly: 0.021
+arm: 0.017
+register: 0.011
+boot: 0.008
+TCG: 0.007
+files: 0.006
+debug: 0.005
+permissions: 0.003
+PID: 0.002
+performance: 0.001
+graphic: 0.001
+network: 0.001
+socket: 0.001
+VMM: 0.001
+peripherals: 0.001
+risc-v: 0.001
+mistranslation: 0.000
+x86: 0.000
+vnc: 0.000
+KVM: 0.000
+ppc: 0.000
+i386: 0.000
+
+QEMU AARCH64 only supports canonical addresses running on x64.
diff --git a/results/classifier/118/architecture/2760 b/results/classifier/118/architecture/2760
new file mode 100644
index 000000000..4245457b6
--- /dev/null
+++ b/results/classifier/118/architecture/2760
@@ -0,0 +1,61 @@
+architecture: 0.936
+register: 0.662
+device: 0.571
+arm: 0.566
+semantic: 0.446
+kernel: 0.382
+risc-v: 0.372
+debug: 0.353
+permissions: 0.346
+network: 0.327
+peripherals: 0.321
+performance: 0.319
+PID: 0.291
+graphic: 0.289
+boot: 0.270
+VMM: 0.254
+ppc: 0.245
+user-level: 0.221
+vnc: 0.198
+TCG: 0.186
+virtual: 0.185
+socket: 0.167
+mistranslation: 0.149
+hypervisor: 0.146
+assembly: 0.108
+files: 0.045
+KVM: 0.022
+i386: 0.003
+x86: 0.002
+--------------------
+register: 0.926
+architecture: 0.917
+debug: 0.863
+arm: 0.815
+assembly: 0.057
+semantic: 0.048
+virtual: 0.040
+user-level: 0.021
+kernel: 0.019
+TCG: 0.007
+files: 0.007
+performance: 0.004
+device: 0.004
+VMM: 0.003
+boot: 0.002
+graphic: 0.002
+PID: 0.001
+risc-v: 0.001
+vnc: 0.001
+hypervisor: 0.001
+peripherals: 0.001
+KVM: 0.001
+mistranslation: 0.001
+permissions: 0.001
+socket: 0.001
+network: 0.000
+ppc: 0.000
+i386: 0.000
+x86: 0.000
+
+Some Aarch64 system registers not available via the debugger
diff --git a/results/classifier/118/architecture/2808 b/results/classifier/118/architecture/2808
new file mode 100644
index 000000000..aefec63ec
--- /dev/null
+++ b/results/classifier/118/architecture/2808
@@ -0,0 +1,61 @@
+architecture: 0.854
+risc-v: 0.583
+device: 0.526
+mistranslation: 0.498
+arm: 0.484
+register: 0.354
+network: 0.321
+semantic: 0.304
+socket: 0.299
+boot: 0.243
+virtual: 0.239
+graphic: 0.233
+permissions: 0.214
+performance: 0.194
+VMM: 0.176
+PID: 0.165
+debug: 0.152
+files: 0.144
+vnc: 0.137
+peripherals: 0.134
+hypervisor: 0.130
+i386: 0.124
+ppc: 0.122
+kernel: 0.109
+x86: 0.103
+TCG: 0.090
+user-level: 0.078
+assembly: 0.050
+KVM: 0.026
+--------------------
+architecture: 0.972
+risc-v: 0.964
+network: 0.293
+kernel: 0.062
+files: 0.062
+virtual: 0.034
+semantic: 0.030
+register: 0.020
+TCG: 0.018
+user-level: 0.017
+hypervisor: 0.016
+debug: 0.013
+peripherals: 0.008
+boot: 0.007
+device: 0.007
+PID: 0.003
+VMM: 0.002
+socket: 0.001
+performance: 0.001
+permissions: 0.001
+vnc: 0.001
+assembly: 0.001
+graphic: 0.001
+KVM: 0.000
+arm: 0.000
+mistranslation: 0.000
+ppc: 0.000
+x86: 0.000
+i386: 0.000
+
+Links to the RISC-V IOMMU Architecture Specification are broken in the docs
diff --git a/results/classifier/118/architecture/2871 b/results/classifier/118/architecture/2871
new file mode 100644
index 000000000..d0bf5ca21
--- /dev/null
+++ b/results/classifier/118/architecture/2871
@@ -0,0 +1,61 @@
+architecture: 0.966
+register: 0.889
+assembly: 0.834
+device: 0.776
+performance: 0.704
+debug: 0.690
+mistranslation: 0.637
+graphic: 0.488
+arm: 0.457
+peripherals: 0.408
+permissions: 0.397
+semantic: 0.394
+files: 0.375
+network: 0.353
+boot: 0.187
+kernel: 0.165
+virtual: 0.143
+user-level: 0.085
+vnc: 0.064
+ppc: 0.054
+hypervisor: 0.045
+KVM: 0.042
+TCG: 0.041
+socket: 0.034
+VMM: 0.026
+PID: 0.013
+risc-v: 0.012
+i386: 0.005
+x86: 0.005
+--------------------
+assembly: 0.993
+register: 0.989
+debug: 0.299
+architecture: 0.238
+virtual: 0.074
+kernel: 0.054
+files: 0.021
+boot: 0.020
+semantic: 0.016
+user-level: 0.015
+hypervisor: 0.006
+KVM: 0.005
+x86: 0.004
+device: 0.003
+VMM: 0.003
+arm: 0.003
+performance: 0.003
+TCG: 0.002
+ppc: 0.002
+permissions: 0.001
+peripherals: 0.001
+PID: 0.001
+network: 0.001
+graphic: 0.001
+mistranslation: 0.001
+risc-v: 0.001
+socket: 0.001
+vnc: 0.000
+i386: 0.000
+
+loongarch64: unknown register name 'f0' in asm
diff --git a/results/classifier/118/architecture/510 b/results/classifier/118/architecture/510
new file mode 100644
index 000000000..2e97f3dfa
--- /dev/null
+++ b/results/classifier/118/architecture/510
@@ -0,0 +1,61 @@
+architecture: 0.928
+device: 0.875
+register: 0.760
+network: 0.685
+performance: 0.633
+risc-v: 0.585
+arm: 0.577
+boot: 0.475
+hypervisor: 0.411
+vnc: 0.409
+PID: 0.377
+graphic: 0.361
+semantic: 0.333
+debug: 0.326
+peripherals: 0.320
+permissions: 0.320
+kernel: 0.299
+socket: 0.282
+assembly: 0.249
+files: 0.231
+virtual: 0.216
+VMM: 0.163
+ppc: 0.159
+TCG: 0.142
+mistranslation: 0.139
+user-level: 0.115
+x86: 0.106
+i386: 0.010
+KVM: 0.007
+--------------------
+register: 0.988
+hypervisor: 0.971
+architecture: 0.957
+virtual: 0.942
+user-level: 0.281
+assembly: 0.239
+semantic: 0.063
+device: 0.012
+kernel: 0.009
+files: 0.009
+boot: 0.006
+debug: 0.004
+graphic: 0.004
+peripherals: 0.003
+TCG: 0.003
+performance: 0.002
+PID: 0.002
+VMM: 0.002
+permissions: 0.001
+socket: 0.001
+KVM: 0.001
+risc-v: 0.001
+x86: 0.000
+mistranslation: 0.000
+network: 0.000
+vnc: 0.000
+ppc: 0.000
+arm: 0.000
+i386: 0.000
+
+QEMU registers support on x64
diff --git a/results/classifier/118/architecture/555 b/results/classifier/118/architecture/555
new file mode 100644
index 000000000..ed5c29563
--- /dev/null
+++ b/results/classifier/118/architecture/555
@@ -0,0 +1,61 @@
+architecture: 0.853
+device: 0.837
+performance: 0.781
+user-level: 0.706
+arm: 0.526
+graphic: 0.455
+debug: 0.439
+network: 0.408
+files: 0.240
+boot: 0.230
+semantic: 0.229
+permissions: 0.223
+PID: 0.213
+register: 0.162
+socket: 0.158
+mistranslation: 0.130
+risc-v: 0.119
+VMM: 0.112
+virtual: 0.102
+peripherals: 0.094
+hypervisor: 0.077
+ppc: 0.074
+kernel: 0.071
+TCG: 0.049
+vnc: 0.046
+assembly: 0.031
+x86: 0.005
+i386: 0.004
+KVM: 0.001
+--------------------
+user-level: 0.970
+virtual: 0.932
+hypervisor: 0.878
+architecture: 0.241
+debug: 0.111
+KVM: 0.016
+arm: 0.015
+boot: 0.014
+TCG: 0.010
+semantic: 0.010
+kernel: 0.010
+VMM: 0.009
+PID: 0.008
+assembly: 0.008
+performance: 0.007
+files: 0.005
+device: 0.005
+graphic: 0.001
+risc-v: 0.001
+register: 0.001
+peripherals: 0.000
+permissions: 0.000
+mistranslation: 0.000
+socket: 0.000
+vnc: 0.000
+network: 0.000
+ppc: 0.000
+x86: 0.000
+i386: 0.000
+
+qemu user aarch64 crashes when giving the dynamic loader as argument
diff --git a/results/classifier/118/architecture/695 b/results/classifier/118/architecture/695
new file mode 100644
index 000000000..93c65cfe0
--- /dev/null
+++ b/results/classifier/118/architecture/695
@@ -0,0 +1,61 @@
+architecture: 0.903
+device: 0.871
+performance: 0.799
+graphic: 0.520
+semantic: 0.420
+arm: 0.417
+virtual: 0.386
+debug: 0.382
+mistranslation: 0.382
+permissions: 0.337
+boot: 0.290
+peripherals: 0.289
+user-level: 0.242
+assembly: 0.234
+register: 0.225
+network: 0.207
+files: 0.189
+risc-v: 0.142
+socket: 0.133
+hypervisor: 0.122
+ppc: 0.033
+vnc: 0.031
+VMM: 0.027
+kernel: 0.023
+TCG: 0.021
+PID: 0.014
+i386: 0.013
+KVM: 0.004
+x86: 0.003
+--------------------
+architecture: 0.938
+device: 0.461
+semantic: 0.048
+virtual: 0.044
+register: 0.029
+assembly: 0.027
+files: 0.023
+kernel: 0.022
+peripherals: 0.019
+boot: 0.010
+socket: 0.008
+TCG: 0.007
+performance: 0.006
+user-level: 0.006
+PID: 0.005
+mistranslation: 0.004
+debug: 0.003
+VMM: 0.002
+permissions: 0.002
+graphic: 0.002
+hypervisor: 0.001
+vnc: 0.001
+ppc: 0.001
+risc-v: 0.001
+network: 0.001
+arm: 0.001
+KVM: 0.001
+i386: 0.000
+x86: 0.000
+
+MIPS: nanomips p32 ABI not supported
diff --git a/results/classifier/118/architecture/911 b/results/classifier/118/architecture/911
new file mode 100644
index 000000000..0c586cd8c
--- /dev/null
+++ b/results/classifier/118/architecture/911
@@ -0,0 +1,77 @@
+architecture: 0.974
+user-level: 0.895
+graphic: 0.831
+device: 0.781
+files: 0.755
+semantic: 0.696
+x86: 0.618
+performance: 0.600
+PID: 0.567
+network: 0.556
+register: 0.541
+ppc: 0.527
+socket: 0.522
+permissions: 0.489
+vnc: 0.485
+boot: 0.466
+debug: 0.462
+i386: 0.428
+risc-v: 0.422
+hypervisor: 0.406
+arm: 0.387
+VMM: 0.358
+peripherals: 0.335
+TCG: 0.317
+kernel: 0.313
+mistranslation: 0.231
+virtual: 0.215
+KVM: 0.177
+assembly: 0.144
+--------------------
+user-level: 0.904
+debug: 0.490
+virtual: 0.479
+x86: 0.375
+files: 0.155
+TCG: 0.053
+performance: 0.048
+PID: 0.043
+ppc: 0.033
+i386: 0.025
+register: 0.021
+semantic: 0.017
+architecture: 0.016
+hypervisor: 0.016
+arm: 0.015
+kernel: 0.011
+VMM: 0.006
+network: 0.003
+assembly: 0.003
+device: 0.003
+permissions: 0.002
+risc-v: 0.002
+KVM: 0.001
+boot: 0.001
+graphic: 0.001
+socket: 0.001
+peripherals: 0.001
+vnc: 0.001
+mistranslation: 0.000
+
+Unable to strace execve calls in mipsel user mode
+Description of problem:
+Used 6.2.0 ZIP and git to build, configured with 
+```
+./configure --target-list=mipsel-linux-user --static --disable-system --enable-linux-user
+```
+
+When trying to strace a mipsel-arch application, I cannot see traces for the `execve` syscall. It looks like the call to `safe_execve` is not returning, so the strace printout is never completed. I'm assuming this has to do with `execve` syscall not returning on success, but older versions appeared to be able to do it. I tried it with QEMU 4.2.1 from the package manager on Ubuntu and I saw the `execve` syscall (see qemu-4.2.1.log).
+Steps to reproduce:
+1. Build mipsel app: ` mipsel-linux-gnu-gcc -o test.mipsel test.c` (Test code is attached as `test.c`)
+2. Run qemu-mipsel: `./build/qemu-mipsel -L /usr/mipsel-linux-gnu/ -strace ../test.mipsel`
+3. Note that even though the app uses both `system` and `popen` to create subprocesses, no `execve` syscall is shown in the strace output.
+Additional information:
+[qemu-6.2.90.log](/uploads/ca03e6f40b3b0ea79a042786a123760a/qemu-6.2.90.log)
+[qemu-6.2.0.log](/uploads/ca15057398377d49b396e9e77a5cb639/qemu-6.2.0.log)
+[qemu-4.2.1.log](/uploads/1087250dd9fc4d8d106d2cbc58c2b14a/qemu-4.2.1.log)
+[test.c](/uploads/9d242a724b10b296cfd7a945ae4d6c4d/test.c)