summary refs log tree commit diff stats
path: root/results/classifier/111/review/944628
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/111/review/944628')
-rw-r--r--results/classifier/111/review/94462847
1 files changed, 47 insertions, 0 deletions
diff --git a/results/classifier/111/review/944628 b/results/classifier/111/review/944628
new file mode 100644
index 00000000..4a9cfdaf
--- /dev/null
+++ b/results/classifier/111/review/944628
@@ -0,0 +1,47 @@
+device: 0.183
+semantic: 0.150
+other: 0.134
+graphic: 0.078
+files: 0.073
+debug: 0.064
+PID: 0.060
+network: 0.054
+socket: 0.043
+boot: 0.040
+permissions: 0.039
+performance: 0.032
+vnc: 0.030
+KVM: 0.019
+other: 0.188
+files: 0.142
+device: 0.133
+debug: 0.124
+semantic: 0.085
+PID: 0.058
+network: 0.053
+boot: 0.050
+socket: 0.038
+graphic: 0.030
+permissions: 0.030
+performance: 0.028
+vnc: 0.026
+KVM: 0.015
+
+Documentation for mtdblock, option-rom, and pflash is non-existent
+
+The options -mtdblock, -option-rom, and -pflash are severely under-documented.  For example:
+
+-mtdblock  -- It isn't at all clear what this does from --help or the documentation, and it's especially not clear that it's only implemented for ARM right now
+
+-option-rom is only implemented for a handful of architectures, including palm, pc, pci, and one or two others
+
+-pflash looks to be implemented for most if not all architectures, but there's nothing informing the user that it replaces the bios if -bios isn't used in tandem with -pflash, and it isn't clear whether the user could add multiple pflash roms
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'expired' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/89
+
+