From: Stefan Weil <sw@weilnetz.de>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
gabriel@kerneis.info, qemu-devel@nongnu.org,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] coroutine: add ./configure --disable-coroutine-pool
Date: Tue, 01 Oct 2013 07:51:24 +0200 [thread overview]
Message-ID: <524A62DC.1070408@weilnetz.de> (raw)
In-Reply-To: <20130930090627.GE16558@stefanha-thinkpad.redhat.com>
Am 30.09.2013 11:06, schrieb Stefan Hajnoczi:
> On Fri, Sep 27, 2013 at 06:49:18PM +0200, Stefan Weil wrote:
>> Am 27.09.2013 11:11, schrieb Stefan Hajnoczi:
>>> On Fri, Sep 27, 2013 at 07:20:21AM +0200, Stefan Weil wrote:
>>>> Am 11.09.2013 16:42, schrieb Stefan Hajnoczi:
>>>>> The 'gthread' coroutine backend was written before the freelist (aka
>>>>> pool) existed in qemu-coroutine.c.
>>>>>
>>>>> This means that every thread is expected to exit when its coroutine
>>>>> terminates. It is not possible to reuse threads from a pool.
>>>>>
>>>>> This patch automatically disables the pool when 'gthread' is used. This
>>>>> allows the 'gthread' backend to work again (for example,
>>>>> tests/test-coroutine completes successfully instead of hanging).
>>>>>
>>>>> I considered implementing thread reuse but I don't want quirks like CPU
>>>>> affinity differences due to coroutine threads being recycled. The
>>>>> 'gthread' backend is a reference backend and it's therefore okay to skip
>>>>> the pool optimization.
>>>>>
>>>>> Note this patch also makes it easy to toggle the pool for benchmarking
>>>>> purposes:
>>>>>
>>>>> ./configure --with-coroutine-backend=ucontext \
>>>>> --disable-coroutine-pool
>>>>>
>>>>> Reported-by: Gabriel Kerneis <gabriel@kerneis.info>
>>>>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>>>>> ---
>>>>> configure | 24 ++++++++++++++++++++++++
>>>>> qemu-coroutine.c | 34 +++++++++++++++++++---------------
>>>>> 2 files changed, 43 insertions(+), 15 deletions(-)
>>>>>
>>>> This patch is important for QEMU 1.5 as well, but needs some
>>>> modifications there.
>>>> A recent bug report for MinGW shows that the win32 coroutine needs it, too.
>>> coroutine-win32.c is designed to support reuse:
>>>
>>> static void CALLBACK coroutine_trampoline(void *co_)
>>> {
>>> Coroutine *co = co_;
>>>
>>> while (true) {
>>> co->entry(co->entry_arg);
>>> qemu_coroutine_switch(co, co->caller, COROUTINE_TERMINATE);
>>> }
>>> }
>>>
>>> We return from qemu_coroutine_switch() when the fiber is reused and
>>> simply run another iteration of the while loop.
>>>
>>> Why do you say win32 coroutines should disable the pool?
>>>
>>> Stefan
>> QEMU MinGW binaries with coroutine pool simply crash, and disabling the
>> pool helps
>> for the moment until we have a better fix. That's a regression which was
>> introduced
>> with a patch which added the pool for win32.
>>
>> See this discussion thread for more details:
>> http://lists.nongnu.org/archive/html/qemu-devel/2013-09/msg04195.html
> I'd like to fix the win32 coroutine backend.
>
> In your email you said it can be reproduced under wine on Linux. I
> wasn't able to reproduce it with this command-line:
>
> $ wine qemu-system-x86_64.exe -m 1024 -vnc :1 -L ../pc-bios -hda ../test.img
>
> Stefan: Do you have a ./configure and QEMU command-line which reproduces
> the assertion failure under wine?
>
> Stefan
Here is my current test environment:
* Debian wheezy x86_64 host (running on a KVM server)
* latest QEMU sources
$ ./configure' '--cross-prefix=i686-w64-mingw32-'
'--enable-trace-backend=stderr' --target-list=i386-softmmu && make
# Get Debian installer CDROM mini.iso.
$ wine i386-softmmu/qemu-system-i386 -L pc-bios -cdrom /var/tmp/mini.iso
-sdl # or -vnc :1
=> Assertion in qemu-coroutine-lock.c:99.
I also tested a similar scenario on an ASUS netbook with Ubuntu some
days ago and got the same result.
Regards,
Stefan
next prev parent reply other threads:[~2013-10-01 5:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 14:42 [Qemu-devel] [PATCH] coroutine: add ./configure --disable-coroutine-pool Stefan Hajnoczi
2013-09-11 14:56 ` Gabriel Kerneis
2013-09-11 15:24 ` Kevin Wolf
2013-09-11 15:32 ` Gabriel Kerneis
2013-09-11 15:38 ` Kevin Wolf
2013-09-12 8:42 ` Stefan Hajnoczi
2013-09-27 5:20 ` Stefan Weil
2013-09-27 9:11 ` Stefan Hajnoczi
2013-09-27 16:49 ` Stefan Weil
2013-09-30 9:06 ` Stefan Hajnoczi
2013-10-01 5:51 ` Stefan Weil [this message]
2013-10-01 7:29 ` Gabriel Kerneis
2013-10-01 16:44 ` Stefan Weil
2013-10-02 8:54 ` Stefan Hajnoczi
2013-10-02 21:15 ` Stefan Weil
2013-10-04 7:30 ` Stefan Hajnoczi
2013-10-01 7:21 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524A62DC.1070408@weilnetz.de \
--to=sw@weilnetz.de \
--cc=gabriel@kerneis.info \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.