From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Markus Armbruster <armbru@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: [Qemu-devel] QAPI Merge Plans
Date: Sun, 06 Mar 2011 14:54:53 -0600 [thread overview]
Message-ID: <4D73F49D.9010001@codemonkey.ws> (raw)
Hi,
I've gotten my QAPI branch now functionally complete so I'm ready to
start working on merging. I thought I'd send a note about my plans as
both a heads up and to see if anyone had any suggestions.
My plan is to split everything up into three rounds. The first round
will just be core infrastructure--the code generator, the new QMP
server, the signal infrastructure, etc. This round will introduce a new
command line option to expose the new QMP server (still chardev based).
Round two will consist of all of the 0.14 commands. Some new commands
are also needed because some of the 0.14 commands are untestable without
new QMP commands :-/
Finally, round three will include some of the new and potentially
controversial bits like the new non-chardev based QMP server, default
session and discovery, qsh tool, etc.
After these three rounds are merged, I'll then work on adding all of the
new QMP commands to support a full HMP session.
I've tried to put a ton of information on the wiki that hopefully will
give a good amount of background along with current status.
I expect the first round of patches to be on list this week.
http://wiki.qemu.org/Features/QAPI
Regards,
Anthony Liguori
next reply other threads:[~2011-03-06 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 20:54 Anthony Liguori [this message]
2011-03-08 23:18 ` [Qemu-devel] Re: QAPI Merge Plans Luiz Capitulino
2011-03-08 23:44 ` Anthony Liguori
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=4D73F49D.9010001@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).