On 2012-11-22 16:16, Paolo Bonzini wrote:
> Il 22/11/2012 14:34, Jan Kiszka ha scritto:
>>
>> =>0 0xf77c242e __kernel_vsyscall+0xe() in [vdso].so (0x0519df88)
>> 1 0xf761f10b __libc_read+0x4a() in libpthread.so.0 (0x0519df88)
>> 2 0x7bc78c98 in ntdll (+0x68c97) (0x0519df88)
>> 3 0x7bc7b0a3 in
Il 22/11/2012 14:34, Jan Kiszka ha scritto:
>
> =>0 0xf77c242e __kernel_vsyscall+0xe() in [vdso].so (0x0519df88)
> 1 0xf761f10b __libc_read+0x4a() in libpthread.so.0 (0x0519df88)
> 2 0x7bc78c98 in ntdll (+0x68c97) (0x0519df88)
> 3 0x7bc7b0a3 in ntdll (+0x6b0a2) (0x0519e1b8)
> 4 0x7bc7b195
On 2012-11-21 14:38, Jan Kiszka wrote:
> On 2012-11-21 14:33, Paolo Bonzini wrote:
>> Il 21/11/2012 14:27, Jan Kiszka ha scritto:
>>> Are there any patches flying around that are supposed to resolve this?
>
> No. Is this with aio=native or aio=threads?
>>> aio= - whatever that is on wi
On 2012-11-21 14:33, Paolo Bonzini wrote:
> Il 21/11/2012 14:27, Jan Kiszka ha scritto:
>> Are there any patches flying around that are supposed to resolve this?
No. Is this with aio=native or aio=threads?
>> aio= - whatever that is on win32.
>
> That's aio=threads, just like POSIX.
Il 21/11/2012 14:27, Jan Kiszka ha scritto:
>>> >> Are there any patches flying around that are supposed to resolve this?
>> >
>> > No. Is this with aio=native or aio=threads?
> aio= - whatever that is on win32.
That's aio=threads, just like POSIX. I'm curious (but not too
optimistic) whether a
On 2012-11-21 14:25, Paolo Bonzini wrote:
> Il 21/11/2012 14:20, Jan Kiszka ha scritto:
>> I'm seeing a regression with this patch when cross-compiling with
>> mingw32 for Win7. QEMU is stuck while booting a versatilepb guest that
>> accesses the block layer via pflash. Enabling tracing "fixes" the
Il 21/11/2012 14:20, Jan Kiszka ha scritto:
> I'm seeing a regression with this patch when cross-compiling with
> mingw32 for Win7. QEMU is stuck while booting a versatilepb guest that
> accesses the block layer via pflash. Enabling tracing "fixes" the issue,
> of course...
>
> Are there any patch
On 2012-10-31 16:30, Paolo Bonzini wrote:
> With the new support for EventNotifiers in the AIO event loop, we
> can hook a completion port to every opened file and use asynchronous
> I/O on them.
>
> Wine's support is extremely inefficient, also because it really does
> the I/O synchronously on re
With the new support for EventNotifiers in the AIO event loop, we
can hook a completion port to every opened file and use asynchronous
I/O on them.
Wine's support is extremely inefficient, also because it really does
the I/O synchronously on regular files. (!) But it works, and it is
good to keep
