From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>, Avi Kivity <avi@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] event_notifier: move to top-level directory
Date: Wed, 28 Sep 2011 08:27:22 +0200 [thread overview]
Message-ID: <4E82BE4A.3040904@redhat.com> (raw)
In-Reply-To: <4E823EEE.3030807@codemonkey.ws>
On 09/27/2011 11:23 PM, Anthony Liguori wrote:
> On 09/27/2011 11:39 AM, Paolo Bonzini wrote:
>> On 09/27/2011 06:05 PM, Anthony Liguori wrote:
>>> Actually, for posix-aio, we can just switch to using g_idle_add().
>>> g_idle_add() uses g_source_attach which is thread safe. g_idle_add()
>>> gives you a thread safe mechanism to defer a piece of work to the
>>> main loop which is really what we want here.
>>
>> For that, a bottom half would also do (apart that I am not sure it is
>> async-safe with TCG). In fact, that would make sense since all of
>> posix_aio_process_queue could become a bottom half.
>
> Bottom halves are signal safe, not thread safe.
>
> To make bottom halves thread safe, you would (in the very least) have to
> add some barriers when reading/writing the scheduling flag.
You can probably assume that qemu_notify_event (and dually the read in
the main loop) are resp. write/read memory barriers. Or even full.
If we switch entirely to GSources, it would be nice to use them. But
since we aren't, and our main loop functionality is quite different from
glib's (it doesn't rely on abstractions for file descriptors, for
example), it is just a painful incomplete transition to use glib's idle
sources to do the exact same thing that is done by bottom halves (which
are already in our toolbox).
Paolo
next prev parent reply other threads:[~2011-09-28 6:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 14:26 [Qemu-devel] [PATCH] event_notifier: move to top-level directory Avi Kivity
2011-09-27 15:17 ` Stefan Hajnoczi
2011-09-27 15:28 ` Jan Kiszka
2011-09-27 16:05 ` Anthony Liguori
2011-09-27 16:39 ` Paolo Bonzini
2011-09-27 21:23 ` Anthony Liguori
2011-09-28 6:27 ` Paolo Bonzini [this message]
2011-09-28 7:52 ` Jan Kiszka
2011-09-28 8:00 ` Paolo Bonzini
2011-09-28 9:12 ` Stefan Hajnoczi
2011-11-01 22:18 ` Anthony Liguori
2011-11-02 18:10 ` Alexander Graf
2011-11-02 17:12 ` Avi Kivity
2011-11-02 17:13 ` Avi Kivity
2011-11-02 18:23 ` Alexander Graf
2011-11-02 17:22 ` Avi Kivity
2011-11-02 17:27 ` Alexander Graf
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=4E82BE4A.3040904@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kwolf@redhat.com \
--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).