From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/8]: QMP feature negotiation support
Date: Thu, 28 Jan 2010 11:42:52 -0200 [thread overview]
Message-ID: <1264686180-29845-1-git-send-email-lcapitulino@redhat.com> (raw)
Feature negotiation allows clients to enable new QMP capabilities they
support and thus allows QMP to envolve in a compatible way.
A capability is a new QMP feature and/or protocol change which is not part of
the core protocol as defined in the QMP spec.
Feature negotiation is implemented by, among other changes, adding
mode-oriented support to QMP, which comprehends the following:
o Two modes: handshake and operational
o All QMP Monitors start in handshake mode
o In handshake mode only commands to query/enable/disable QMP capabilities are
allowed (there are few exceptions)
o Clients can switch to the operational mode at any time
o In Operational mode most commands are allowed and QMP capabilities changes
made in handshake mode take effect
Please, note that we don't have any capability yet. So, the most visable
change in this series is that now Clients must switch to operational mode to
be able to issue 'regular' commands.
Session example:
"""
{"QMP": {"capabilities": []}}
{ "execute": "query-qmp-mode" }
{"return": {"mode": "handshake"}}
{ "execute": "stop" }
{"error": {"class": "CommandNotFound", "desc": "The command stop has not been found", "data": {"name": "stop"}}}
{ "execute": "qmp_capability_enable", "arguments": { "name": "foobar" } }
{"error": {"class": "InvalidParameter", "desc": "Invalid parameter name", "data": {"name": "name"}}}
{ "execute": "qmp_switch_mode", "arguments": { "mode": "operational" } }
{"return": {}}
{ "execute": "query-qmp-mode" }
{"return": {"mode": "operational"}}
{ "execute": "stop" }
{"return": {}}
"""
next reply other threads:[~2010-01-28 13:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 13:42 Luiz Capitulino [this message]
2010-01-28 13:42 ` [Qemu-devel] [PATCH 1/8] QMP: Initial mode-oriented support Luiz Capitulino
2010-02-01 17:08 ` Markus Armbruster
2010-01-28 13:42 ` [Qemu-devel] [PATCH 2/8] QMP: Introduce 'query-qmp-mode' command Luiz Capitulino
2010-01-28 13:42 ` [Qemu-devel] [PATCH 3/8] QError: Add QMP mode-oriented errors Luiz Capitulino
2010-01-28 22:49 ` Anthony Liguori
2010-01-29 0:38 ` Luiz Capitulino
2010-02-01 17:03 ` Markus Armbruster
2010-01-28 13:42 ` [Qemu-devel] [PATCH 4/8] QMP: Introduce qmp_switch_mode command Luiz Capitulino
2010-02-01 17:04 ` Markus Armbruster
2010-02-01 18:11 ` Luiz Capitulino
2010-01-28 13:42 ` [Qemu-devel] [PATCH 5/8] QMP: Introduce qmp_capability_enable/disable Luiz Capitulino
2010-01-28 13:42 ` [Qemu-devel] [PATCH 6/8] Monitor: Introduce find_info_cmd() Luiz Capitulino
2010-01-28 13:42 ` [Qemu-devel] [PATCH 7/8] QMP: Enable feature negotiation support Luiz Capitulino
2010-01-28 13:43 ` [Qemu-devel] [PATCH 8/8] QMP: spec: Feature negotiation related changes Luiz Capitulino
2010-02-01 17:08 ` [Qemu-devel] [PATCH 0/8]: QMP feature negotiation support Markus Armbruster
2010-02-01 18:22 ` Luiz Capitulino
2010-02-01 19:37 ` Markus Armbruster
2010-02-01 19:50 ` Luiz Capitulino
2010-02-02 8:03 ` Markus Armbruster
2010-02-02 12:12 ` Luiz Capitulino
2010-02-02 14:48 ` Markus Armbruster
2010-02-03 18:34 ` 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=1264686180-29845-1-git-send-email-lcapitulino@redhat.com \
--to=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).