From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] event_notifier: move to top-level directory
Date: Tue, 27 Sep 2011 18:39:05 +0200 [thread overview]
Message-ID: <4E81FC29.9090503@redhat.com> (raw)
In-Reply-To: <4E81F43B.1040708@codemonkey.ws>
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.
But the problem to be solved here is waking up qemu_aio_wait, and
scheduling bottom halves currently wakes up only the vl.c main loop.
> This can actually be made to work with sync I/O emulation too by
> having another GMainLoop in the sync I/O loop although I thought I
> recalled a patch series to remove that stuff.
... which stuff? :) Another GMainLoop in the sync I/O loop is
problematic for two reasons: 1) the sync I/O loop does not relinquish
the I/O thread mutex, which makes it very different from the outer loop;
2) a nested GMainLoop keeps polling all the file descriptors in the
outer loop, which requires you to cope with reentrancy in those monitor
commands that flush AIO.
Paolo
next prev parent reply other threads:[~2011-09-27 16:39 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 [this message]
2011-09-27 21:23 ` Anthony Liguori
2011-09-28 6:27 ` Paolo Bonzini
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=4E81FC29.9090503@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 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.