From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <shajnocz@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Fam Zheng <famz@redhat.com>,
Juan Quintela <quintela@redhat.com>,
mdroth@linux.vnet.ibm.com, Eric Blake <eblake@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
marcandre.lureau@redhat.com
Subject: Re: [Qemu-devel] [RFC v5 12/26] qmp: negociate QMP capabilities
Date: Tue, 12 Dec 2017 17:39:04 +0000 [thread overview]
Message-ID: <20171212173904.GI2409@work-vm> (raw)
In-Reply-To: <20171205055200.16305-13-peterx@redhat.com>
* Peter Xu (peterx@redhat.com) wrote:
> After this patch, we will allow QMP clients to enable QMP capabilities
> when sending the first "qmp_capabilities" command. Originally we are
> starting QMP session with no arguments like:
>
> { "execute": "qmp_capabilities" }
>
> Now we can enable some QMP capabilities using (take OOB as example,
> which is the only one capability that we support):
>
> { "execute": "qmp_capabilities",
> "argument": { "enable": [ "oob" ] } }
>
> When the "argument" key is not provided, no capability is enabled.
>
> For capability "oob", the monitor needs to be run on dedicated IO
> thread, otherwise the command will fail. For example, trying to enable
> OOB on a MUXed typed QMP monitor will fail.
>
> One thing to mention is that, QMP capabilities are per-monitor, and also
> when the connection is closed due to some reason, the capabilities will
> be reset.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Typo in the title nego*t*iate, other than that.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> monitor.c | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> qapi-schema.json | 15 ++++++++++++---
> 2 files changed, 68 insertions(+), 4 deletions(-)
>
> diff --git a/monitor.c b/monitor.c
> index bad6ee8dd1..097312e65f 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -167,6 +167,7 @@ typedef struct {
> * mode.
> */
> QmpCommandList *commands;
> + bool qmp_caps[QMP_CAPABILITY__MAX];
> } MonitorQMP;
>
> /*
> @@ -1037,8 +1038,42 @@ static void monitor_init_qmp_commands(void)
> qmp_marshal_qmp_capabilities, QCO_NO_OPTIONS);
> }
>
> -void qmp_qmp_capabilities(Error **errp)
> +static void qmp_caps_check(Monitor *mon, QMPCapabilityList *list,
> + Error **errp)
> +{
> + for (; list; list = list->next) {
> + assert(list->value < QMP_CAPABILITY__MAX);
> + switch (list->value) {
> + case QMP_CAPABILITY_OOB:
> + if (!mon->use_io_thr) {
> + /*
> + * Out-Of-Band only works with monitors that are
> + * running on dedicated IOThread.
> + */
> + error_setg(errp, "This monitor does not support "
> + "Out-Of-Band (OOB)");
> + return;
> + }
> + break;
> + default:
> + break;
> + }
> + }
> +}
> +
> +/* This function should only be called after capabilities are checked. */
> +static void qmp_caps_apply(Monitor *mon, QMPCapabilityList *list)
> +{
> + for (; list; list = list->next) {
> + mon->qmp.qmp_caps[list->value] = true;
> + }
> +}
> +
> +void qmp_qmp_capabilities(bool has_enable, QMPCapabilityList *enable,
> + Error **errp)
> {
> + Error *local_err = NULL;
> +
> if (cur_mon->qmp.commands == &qmp_commands) {
> error_set(errp, ERROR_CLASS_COMMAND_NOT_FOUND,
> "Capabilities negotiation is already complete, command "
> @@ -1046,6 +1081,20 @@ void qmp_qmp_capabilities(Error **errp)
> return;
> }
>
> + /* Enable QMP capabilities provided by the guest if applicable. */
> + if (has_enable) {
> + qmp_caps_check(cur_mon, enable, &local_err);
> + if (local_err) {
> + /*
> + * Failed check on either of the capabilities will fail
> + * the apply of all.
> + */
> + error_propagate(errp, local_err);
> + return;
> + }
> + qmp_caps_apply(cur_mon, enable);
> + }
> +
> cur_mon->qmp.commands = &qmp_commands;
> }
>
> @@ -3963,6 +4012,11 @@ static QObject *get_qmp_greeting(void)
> return QOBJECT(result);
> }
>
> +static void monitor_qmp_caps_reset(Monitor *mon)
> +{
> + memset(mon->qmp.qmp_caps, 0, sizeof(mon->qmp.qmp_caps));
> +}
> +
> static void monitor_qmp_event(void *opaque, int event)
> {
> QObject *data;
> @@ -3971,6 +4025,7 @@ static void monitor_qmp_event(void *opaque, int event)
> switch (event) {
> case CHR_EVENT_OPENED:
> mon->qmp.commands = &qmp_cap_negotiation_commands;
> + monitor_qmp_caps_reset(mon);
> data = get_qmp_greeting();
> monitor_json_emitter(mon, data);
> qobject_decref(data);
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 03201578b4..531fd4c0db 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -102,21 +102,30 @@
> #
> # Enable QMP capabilities.
> #
> -# Arguments: None.
> +# Arguments:
> +#
> +# @enable: List of QMPCapabilities to enable, which is optional.
> +# If not provided, it means no QMP capabilities will be
> +# enabled. (since 2.12)
> #
> # Example:
> #
> -# -> { "execute": "qmp_capabilities" }
> +# -> { "execute": "qmp_capabilities",
> +# "arguments": { "enable": [ "oob" ] } }
> # <- { "return": {} }
> #
> # Notes: This command is valid exactly when first connecting: it must be
> # issued before any other command will be accepted, and will fail once the
> # monitor is accepting other commands. (see qemu docs/interop/qmp-spec.txt)
> #
> +# QMP client needs to explicitly enable QMP capabilities, otherwise
> +# all the QMP capabilities will be turned off by default.
> +#
> # Since: 0.13
> #
> ##
> -{ 'command': 'qmp_capabilities' }
> +{ 'command': 'qmp_capabilities',
> + 'data': { '*enable': [ 'QMPCapability' ] } }
>
> ##
> # @QMPCapability:
> --
> 2.14.3
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-12-12 17:39 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 5:51 [Qemu-devel] [RFC v5 00/26] QMP: out-of-band (OOB) execution support Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 01/26] qobject: introduce qstring_get_try_str() Peter Xu
2017-12-13 15:25 ` Stefan Hajnoczi
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 02/26] qobject: introduce qobject_get_try_str() Peter Xu
2017-12-13 15:25 ` Stefan Hajnoczi
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 03/26] qobject: let object_property_get_str() use new API Peter Xu
2017-12-13 15:27 ` Stefan Hajnoczi
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 04/26] monitor: move skip_flush into monitor_data_init Peter Xu
2017-12-13 15:28 ` Stefan Hajnoczi
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 05/26] qjson: add "opaque" field to JSONMessageParser Peter Xu
2017-12-13 15:37 ` Stefan Hajnoczi
2017-12-15 7:55 ` Peter Xu
2017-12-15 12:45 ` Stefan Hajnoczi
2017-12-16 3:28 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 06/26] monitor: move the cur_mon hack deeper for QMP Peter Xu
2017-12-13 15:41 ` Stefan Hajnoczi
2017-12-15 8:02 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 07/26] monitor: unify global init Peter Xu
2017-12-13 15:48 ` Stefan Hajnoczi
2017-12-15 8:11 ` Peter Xu
2017-12-15 12:47 ` Stefan Hajnoczi
2017-12-16 3:52 ` Peter Xu
2017-12-16 9:01 ` Stefan Hajnoczi
2017-12-18 3:27 ` Peter Xu
2017-12-18 9:24 ` Stefan Hajnoczi
2017-12-18 10:10 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 08/26] monitor: let mon_list be tail queue Peter Xu
2017-12-13 15:49 ` Stefan Hajnoczi
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 09/26] monitor: create monitor dedicate iothread Peter Xu
2017-12-13 16:20 ` Stefan Hajnoczi
2017-12-15 8:31 ` Peter Xu
2017-12-15 13:21 ` Stefan Hajnoczi
2017-12-16 4:42 ` Peter Xu
2017-12-16 4:50 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 10/26] monitor: allow to use IO thread for parsing Peter Xu
2017-12-13 16:35 ` Stefan Hajnoczi
2017-12-15 8:50 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 11/26] qmp: introduce QMPCapability Peter Xu
2017-12-13 16:56 ` Stefan Hajnoczi
2017-12-15 9:14 ` Peter Xu
2017-12-15 9:38 ` Fam Zheng
2017-12-16 3:58 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 12/26] qmp: negociate QMP capabilities Peter Xu
2017-12-12 17:39 ` Dr. David Alan Gilbert [this message]
2017-12-13 17:19 ` Stefan Hajnoczi
2017-12-15 9:40 ` Fam Zheng
2017-12-15 13:26 ` Stefan Hajnoczi
2017-12-15 13:53 ` Fam Zheng
2017-12-16 5:34 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 13/26] qmp: introduce some capability helpers Peter Xu
2017-12-12 17:44 ` Dr. David Alan Gilbert
2017-12-13 17:20 ` Stefan Hajnoczi
2017-12-15 9:42 ` Fam Zheng
2017-12-16 5:45 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 14/26] monitor: introduce monitor_qmp_respond() Peter Xu
2017-12-13 17:35 ` Stefan Hajnoczi
2017-12-16 5:52 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 15/26] monitor: let suspend_cnt be thread safe Peter Xu
2017-12-13 18:43 ` Stefan Hajnoczi
2017-12-16 6:12 ` Peter Xu
2017-12-16 9:11 ` Stefan Hajnoczi
2017-12-18 5:16 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 16/26] monitor: separate QMP parser and dispatcher Peter Xu
2017-12-13 20:09 ` Stefan Hajnoczi
2017-12-16 6:37 ` Peter Xu
2017-12-16 6:46 ` Peter Xu
2017-12-16 9:23 ` Stefan Hajnoczi
2017-12-18 5:26 ` Peter Xu
2017-12-18 9:10 ` Stefan Hajnoczi
2017-12-18 10:03 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 17/26] qmp: add new event "request-dropped" Peter Xu
2017-12-14 11:16 ` Stefan Hajnoczi
2017-12-16 6:59 ` Peter Xu
2017-12-14 11:32 ` Stefan Hajnoczi
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 18/26] monitor: send event when request queue full Peter Xu
2017-12-14 11:41 ` Stefan Hajnoczi
2017-12-16 7:17 ` Peter Xu
2017-12-16 9:28 ` Stefan Hajnoczi
2017-12-18 5:32 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 19/26] qapi: introduce new cmd option "allow-oob" Peter Xu
2017-12-14 12:42 ` Stefan Hajnoczi
2017-12-15 9:51 ` Fam Zheng
2017-12-16 7:34 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 20/26] qmp: support out-of-band (oob) execution Peter Xu
2017-12-14 13:16 ` Stefan Hajnoczi
2017-12-18 5:37 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 21/26] qmp: isolate responses into io thread Peter Xu
2017-12-14 13:43 ` Stefan Hajnoczi
2017-12-18 5:52 ` Peter Xu
2017-12-18 7:32 ` Peter Xu
2017-12-18 8:40 ` Stefan Hajnoczi
2017-12-18 10:15 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 22/26] monitor: enable IO thread for (qmp & !mux) typed Peter Xu
2017-12-14 13:44 ` Stefan Hajnoczi
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 23/26] qmp: add command "x-oob-test" Peter Xu
2017-12-14 13:45 ` Stefan Hajnoczi
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 24/26] docs: update QMP documents for OOB commands Peter Xu
2017-12-14 14:30 ` Stefan Hajnoczi
2017-12-18 9:44 ` Peter Xu
2017-12-18 14:09 ` Stefan Hajnoczi
2017-12-19 3:18 ` Peter Xu
2017-12-05 5:51 ` [Qemu-devel] [RFC v5 25/26] tests: qmp-test: verify command batching Peter Xu
2017-12-14 14:39 ` Stefan Hajnoczi
2017-12-18 9:48 ` Peter Xu
2017-12-05 5:52 ` [Qemu-devel] [RFC v5 26/26] tests: qmp-test: add oob test Peter Xu
2017-12-14 14:47 ` Stefan Hajnoczi
2017-12-18 9:51 ` Peter Xu
2017-12-18 13:59 ` Stefan Hajnoczi
2017-12-14 14:52 ` [Qemu-devel] [RFC v5 00/26] QMP: out-of-band (OOB) execution support Stefan Hajnoczi
2017-12-19 6:05 ` Peter Xu
2017-12-15 10:41 ` Fam Zheng
2017-12-15 11:43 ` Dr. David Alan Gilbert
2017-12-15 13:30 ` Stefan Hajnoczi
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=20171212173904.GI2409@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=shajnocz@redhat.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).