From: Alex Bligh <alex@alex.org.uk>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Ping Fan Liu <pingfank@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Cc: Alex Bligh <alex@alex.org.uk>
Subject: Re: [Qemu-devel] [RFC] Convert AioContext to Gsource sub classes
Date: Sat, 10 Aug 2013 11:15:20 +0100 [thread overview]
Message-ID: <79052A2505088F62663AEA17@nimrod.local> (raw)
In-Reply-To: <5205B251.2060907@linux.vnet.ibm.com>
--On 10 August 2013 11:24:01 +0800 Wenchao Xia <xiawenc@linux.vnet.ibm.com>
wrote:
> I'd like form a series which remove AioContext's concept and
> bind to glib's main loop more closely. Since changed place will be
> a bit much so want to know your opinion before real coding:
This may well clash with the aio / timers patch series. I think the
current direction is to introduce a dummy AioContext in place
of glib's main loop. That's the bit I have not done yet in the (just
posted) v9 of this patch (and your approach should work with the
v8 approach).
If we went this way we'd add a TimerListGroup to the the GSource
sub class I guess. This does seem a little less hacky. However
we'd have to make g_source timeouts work in nanoseconds rather
than milliseconds.
--
Alex Bligh
prev parent reply other threads:[~2013-08-10 10:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 3:24 [Qemu-devel] [RFC] Convert AioContext to Gsource sub classes Wenchao Xia
2013-08-10 8:03 ` Paolo Bonzini
2013-08-12 6:46 ` Wenchao Xia
2013-08-12 7:30 ` Paolo Bonzini
2013-08-12 17:01 ` Michael Roth
2013-08-13 8:44 ` Wenchao Xia
2013-08-15 15:23 ` Michael Roth
2013-08-15 16:32 ` Michael Roth
2013-08-16 7:15 ` Wenchao Xia
2013-08-16 8:12 ` Wenchao Xia
2013-08-20 9:59 ` Wenchao Xia
2013-08-20 17:54 ` Alex Bligh
2013-08-21 8:45 ` Stefan Hajnoczi
2013-08-21 9:33 ` Wenchao Xia
2013-08-22 11:40 ` Stefan Hajnoczi
2013-08-21 10:06 ` Alex Bligh
2013-08-10 10:15 ` Alex Bligh [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=79052A2505088F62663AEA17@nimrod.local \
--to=alex@alex.org.uk \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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).