add 18th iteration of classifier

1 files changed, 86 insertions, 0 deletions

diff --git a/results/classifier/118/graphic/1894617 b/results/classifier/118/graphic/1894617
new file mode 100644
index 000000000..077d9bac7
--- /dev/null
+++ b/results/classifier/118/graphic/1894617
@@ -0,0 +1,86 @@
+graphic: 0.926
+device: 0.910
+permissions: 0.903
+register: 0.891
+assembly: 0.885
+peripherals: 0.875
+semantic: 0.875
+i386: 0.866
+debug: 0.865
+architecture: 0.861
+socket: 0.859
+hypervisor: 0.856
+arm: 0.855
+user-level: 0.850
+PID: 0.828
+mistranslation: 0.823
+VMM: 0.821
+virtual: 0.818
+ppc: 0.807
+vnc: 0.806
+TCG: 0.787
+risc-v: 0.784
+network: 0.774
+files: 0.762
+performance: 0.755
+kernel: 0.745
+x86: 0.740
+KVM: 0.702
+boot: 0.557
+
+qemu-i386 mmap but offset greater than 32 bits
+
+I don't know if it's a problem, but I did, and it bothered me for a long time.
+When I use qemu-i386 and interact with the video card device,an error has occurred:
+
+18534 ioctl(4,DRM_IOCTL_MODE_GETENCODER,{39,0,0,0,0}) = 0 ({39,4,34,3,0})
+18534 ioctl(4,DRM_IOCTL_MODE_CREATE_DUMB,{1080,1920,32,0,0,0,0}) = 0 ({1080,1920,32,0,1,7680,8294400})
+18534 ioctl(4,DRM_IOCTL_MODE_ADDFB,{0,1920,1080,7680,32,24,1}) = 0 ({66,1920,1080,7680,32,24,1})
+18534 ioctl(4,DRM_IOCTL_MODE_MAP_DUMB,{1,0,0}) = 0 ({1,0,5543018496})
+18534 mmap2(NULL,8294400,PROT_READ|PROT_WRITE,MAP_SHARED,4,0x14a63c) = -1 errno=22 (Invalid argument)
+
+"5543018496" is the offset through ioctl() and it is "0x14a63c000".
+In qemu：
+ret = target_mmap(arg1, arg2, arg3,
+      target_to_host_bitmask(arg4, mmap_flags_tbl),
+      arg5, arg6 << MMAP_SHIFT);
+
+The type of "arg6" is ulong.When use qemu-i386, arg6 can't be set to "0x14a63c000".So it's wrong for my program.
+
+I want to find a good way to deal with this kind of problem, but I'm not very familiar with QEMU，
+so I came to ask how to deal with this problem.
+
+Thank you！
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+