add 18th iteration of classifier

1 files changed, 63 insertions, 0 deletions

diff --git a/results/classifier/118/none/1657 b/results/classifier/118/none/1657
new file mode 100644
index 000000000..fdabfd209
--- /dev/null
+++ b/results/classifier/118/none/1657
@@ -0,0 +1,63 @@
+graphic: 0.744
+device: 0.664
+x86: 0.501
+peripherals: 0.476
+architecture: 0.438
+performance: 0.389
+socket: 0.375
+semantic: 0.338
+user-level: 0.329
+debug: 0.327
+kernel: 0.322
+i386: 0.320
+files: 0.319
+boot: 0.318
+ppc: 0.285
+network: 0.268
+mistranslation: 0.253
+arm: 0.247
+PID: 0.246
+VMM: 0.226
+permissions: 0.222
+vnc: 0.220
+register: 0.201
+risc-v: 0.185
+TCG: 0.176
+hypervisor: 0.144
+virtual: 0.137
+KVM: 0.091
+assembly: 0.072
+
+Unable to use ide hard drive when using xlnx-zcu102 board
+Description of problem:
+I have only recently started using qemu and am reading content related to ahci. When I started QEMU using the above command line (I did not specify the Linux kernel because I only wanted to see which devices were initialized on the motherboard), I found the following devices in the device tree:
+ ```
+dev: sysbus-ahci, id ""
+
+gpio-out "sysbus-irq" 1
+
+num-ports = 2 (0x2)
+
+mmio 00000000fd0c0000/0000000000001000
+
+bus: ide.1
+
+type IDE
+
+bus: ide.0
+
+type IDE
+ ```
+
+I think this is similar to the ICH9 ahci device, so I tried to mount an IDE hard drive（using command line：-drive file=./testide.img）but failed. QEMU shows
+ ```
+qemu-system-aarch64: -drive file=./ testide.img: machine type does not support if=ide,bus=0,unit=0
+ ```
+So if the ide bus generated by sysbus ahci cannot mount a hard drive, what device should it mount?
+It will be grateful if anyone can answer this question.
+Steps to reproduce:
+1.
+2.
+3.
+Additional information:
+