diff options
Diffstat (limited to 'results/classifier/014/files')
| -rw-r--r-- | results/classifier/014/files/64322995 | 81 |
1 files changed, 0 insertions, 81 deletions
diff --git a/results/classifier/014/files/64322995 b/results/classifier/014/files/64322995 deleted file mode 100644 index c8bb6bbb7..000000000 --- a/results/classifier/014/files/64322995 +++ /dev/null @@ -1,81 +0,0 @@ -files: 0.941 -performance: 0.939 -mistranslation: 0.936 -device: 0.915 -network: 0.914 -operating system: 0.910 -semantic: 0.906 -graphic: 0.904 -kernel: 0.879 -ppc: 0.878 -PID: 0.875 -socket: 0.866 -register: 0.858 -user-level: 0.853 -debug: 0.837 -peripherals: 0.836 -permissions: 0.835 -hypervisor: 0.830 -architecture: 0.823 -vnc: 0.801 -VMM: 0.800 -risc-v: 0.799 -boot: 0.780 -TCG: 0.769 -x86: 0.760 -virtual: 0.748 -KVM: 0.742 -i386: 0.741 -arm: 0.728 -assembly: 0.653 -alpha: 0.640 - -[Qemu-devel] [BUG] trace: QEMU hangs on initialization with the "simple" backend - -While starting the softmmu version of QEMU, the simple backend waits for the -writeout thread to signal a condition variable when initializing the output file -path. But since the writeout thread has not been created, it just waits forever. - -Thanks, - Lluis - -On Tue, Feb 09, 2016 at 09:24:04PM +0100, LluÃs Vilanova wrote: -> -While starting the softmmu version of QEMU, the simple backend waits for the -> -writeout thread to signal a condition variable when initializing the output -> -file -> -path. But since the writeout thread has not been created, it just waits -> -forever. -Denis Lunev posted a fix: -https://patchwork.ozlabs.org/patch/580968/ -Stefan -signature.asc -Description: -PGP signature - -Stefan Hajnoczi writes: - -> -On Tue, Feb 09, 2016 at 09:24:04PM +0100, LluÃs Vilanova wrote: -> -> While starting the softmmu version of QEMU, the simple backend waits for the -> -> writeout thread to signal a condition variable when initializing the output -> -> file -> -> path. But since the writeout thread has not been created, it just waits -> -> forever. -> -Denis Lunev posted a fix: -> -https://patchwork.ozlabs.org/patch/580968/ -Great, thanks. - -Lluis - |