From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] coroutine: hung when using gthread backend
Date: Tue, 26 Mar 2013 17:21:10 +0100 [thread overview]
Message-ID: <20130326162110.GA3391@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <51517289.1020909@redhat.com>
On Tue, Mar 26, 2013 at 11:03:53AM +0100, Paolo Bonzini wrote:
> Il 26/03/2013 10:54, Stefan Hajnoczi ha scritto:
> > On Tue, Mar 26, 2013 at 08:03:50AM +0100, Paolo Bonzini wrote:
> >> Il 26/03/2013 03:50, Wenchao Xia ha scritto:
> >>> When I using tcg with coroutine backend = gthread,
> >>> x86_64-softmmu/qemu-system-x86_64 will hung. Any one
> >>> working on it?
> >>
> >> coroutine backend gthread hardly works for qemu, only qemu-io and qemu-img.
> >
> > Do you know why it doesn't work?
>
> Because it screws up the signals. Coroutines can start in a thread and
> later move to another. If you use the gthread backend, coroutines keep
> the signal mask of the thread where they were created.
>
> It is basically the same bug that was fixed in commit 6ab7e54 (Replace
> all setjmp()/longjmp() with sigsetjmp()/siglongjmp(), 2013-02-20).
That's interesting. Maybe it can be fixed if the gthread backend is
actually needed.
Stefan
next prev parent reply other threads:[~2013-03-26 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 2:50 [Qemu-devel] coroutine: hung when using gthread backend Wenchao Xia
2013-03-26 7:03 ` Paolo Bonzini
2013-03-26 9:54 ` Stefan Hajnoczi
2013-03-26 9:56 ` Peter Maydell
2013-03-27 2:11 ` Wenchao Xia
2013-03-26 10:03 ` Paolo Bonzini
2013-03-26 16:21 ` Stefan Hajnoczi [this message]
2013-03-27 2:10 ` Wenchao Xia
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=20130326162110.GA3391@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiawenc@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).