From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Joey Carlini" <moocow1452@gmail.com>
Subject: Re: [Qemu-devel] ChrEMU - Virtualization in the Browser
Date: Mon, 07 Oct 2013 16:49:38 +0200 [thread overview]
Message-ID: <5252CA02.60903@redhat.com> (raw)
In-Reply-To: <CAJSP0QUF35jyvo_HTyW+wjXG_vrivH5RD-NsHL+_YesTXbW-8w@mail.gmail.com>
Il 25/09/2013 16:02, Stefan Hajnoczi ha scritto:
>>>> >>> I'm pretty sure coroutines would provide difficult to port too.
>>> >>
>>> >> The gthread backend should work since it doesn't use stack-switching.
>> >
>> > ...except that the gthread backend doesn't work for anything
>> > except some nebulous testing scenarios.
> If someone really needs the gthread backend, they can make it work.
>
> In a NaCl world, you don't have POSIX signals anyway so the signal
> mask issue with the gthread backend is moot.
If you don't have signals, you also don't have a way to interrupt the
VCPU thread. After all the work on making memory dispatch more
thread-friendly is completed, it shouldn't be _that_ hard to run the TCG
VCPU threads outside the big QEMU lock. But until that is done, you
need POSIX signals to interrupt the VCPU thread (Windows uses the debug
API instead, which is even worse and probably doesn't have a NaCl
equivalent either).
Paolo
prev parent reply other threads:[~2013-10-07 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 0:08 [Qemu-devel] ChrEMU - Virtualization in the Browser Joey Carlini
2013-09-23 13:39 ` Stefan Hajnoczi
2013-09-23 16:24 ` Alex Bennée
2013-09-23 18:48 ` Anthony Liguori
2013-09-25 8:59 ` Stefan Hajnoczi
2013-09-25 13:10 ` Peter Maydell
2013-09-25 14:02 ` Stefan Hajnoczi
2013-10-07 14:49 ` Paolo Bonzini [this message]
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=5252CA02.60903@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=anthony@codemonkey.ws \
--cc=moocow1452@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).