From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, dlaor@redhat.com, avi@redhat.com, armbru@redhat.com
Subject: [Qemu-devel] QMP forward compatibility support
Date: Mon, 11 Jan 2010 16:34:22 -0200 [thread overview]
Message-ID: <20100111163422.0d86d2bb@doriath> (raw)
Hi.
We (Markus and I) are working on getting QMP forward compatibility support,
supported. :)
We have a plan for it and I'd like to ask the CC'ed people to review it.
Needless to say, but the objective here is to add new commands, arguments,
async messages and protocol features w/o breaking existing clients.
General Plan
------------
1. QMP should describe itself, ie. it should dump all accepted commands,
their replies and arguments, async messages and protocol features. All in
JSON format
2. Protocol features are advertised by the (already existent) capabilities
array, but are _disabled_ by default. The exception is async messages,
which are _enabled_ by default
3. We should add command(s) to enable/disable protocol features
4. Proper feature negotiation is done in pause mode. That's, clients
interested in enabling new protocol features should start QEMU in
pause mode and enable the features they are interested in using
Work to do
----------
1. Markus is already working on getting QMP to describe itself, we
should get a status/proposal soon. This is the most important part,
as we may want to change query-commands output, query-events is
missing and hopefully we can generate user docs from this
2. We need to add commands to enable/disable features. Not high priority,
as the only existing feature is async messages which are enabled by
default
next reply other threads:[~2010-01-11 18:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 18:34 Luiz Capitulino [this message]
2010-01-11 18:57 ` [Qemu-devel] QMP forward compatibility support Anthony Liguori
2010-01-11 19:49 ` Daniel P. Berrange
2010-01-12 0:04 ` Luiz Capitulino
2010-01-12 0:24 ` Anthony Liguori
2010-01-12 8:16 ` Markus Armbruster
2010-01-12 12:19 ` Luiz Capitulino
2010-01-12 12:11 ` Luiz Capitulino
2010-01-13 16:53 ` Markus Armbruster
2010-01-13 17:06 ` Luiz Capitulino
2010-01-13 17:38 ` Markus Armbruster
2010-01-13 17:43 ` Luiz Capitulino
2010-01-14 0:01 ` Jamie Lokier
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=20100111163422.0d86d2bb@doriath \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=dlaor@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).