Re: [Qemu-devel] [PATCH v7 10/23] qmp: introduce QMPCapability

2018-02-22 Thread Peter Xu
On Wed, Feb 21, 2018 at 04:17:18PM +, Stefan Hajnoczi wrote:
> On Wed, Jan 24, 2018 at 01:39:44PM +0800, Peter Xu wrote:
> > diff --git a/qapi-schema.json b/qapi-schema.json
> > index 5c06745c79..2490d5188e 100644
> > --- a/qapi-schema.json
> > +++ b/qapi-schema.json
> > @@ -102,21 +102,47 @@
> >  #
> >  # Enable QMP capabilities.
> >  #
> > -# Arguments: None.
> > +# Arguments:
> > +#
> > +# @enable:List of QMPCapabilities to enable, which is optional.
> > +# Client must not enable any capability that is not
> > +# mentioned in QMP greeting message.
> 
> qapi-schema.json uses full sentences so I've added missing articles to
> the text.  I also changed s/QMPCapabilities/QMPCapability values/ to
> avoid confusion about the type name:
> 
>   An optional list of QMPCapability values to enable.  The client must
>   not enable any capability that is not mentioned in the QMP greeting
>   message.
> 
> >  #
> >  # 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
> 
> s/QMP client/The QMP client/

Thanks;  Fixing them all.

-- 
Peter Xu



Re: [Qemu-devel] [PATCH v7 10/23] qmp: introduce QMPCapability

2018-02-21 Thread Stefan Hajnoczi
On Wed, Jan 24, 2018 at 01:39:44PM +0800, Peter Xu wrote:
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 5c06745c79..2490d5188e 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -102,21 +102,47 @@
>  #
>  # Enable QMP capabilities.
>  #
> -# Arguments: None.
> +# Arguments:
> +#
> +# @enable:List of QMPCapabilities to enable, which is optional.
> +# Client must not enable any capability that is not
> +# mentioned in QMP greeting message.

qapi-schema.json uses full sentences so I've added missing articles to
the text.  I also changed s/QMPCapabilities/QMPCapability values/ to
avoid confusion about the type name:

  An optional list of QMPCapability values to enable.  The client must
  not enable any capability that is not mentioned in the QMP greeting
  message.

>  #
>  # 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

s/QMP client/The QMP client/


signature.asc
Description: PGP signature


[Qemu-devel] [PATCH v7 10/23] qmp: introduce QMPCapability

2018-01-23 Thread Peter Xu
There were no QMP capabilities defined.  Define the first "oob" as
capability to allow out-of-band messages.

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.

Also, touch up qmp-test.c to test the new bits.

Signed-off-by: Peter Xu 
---
 monitor.c| 76 
 qapi-schema.json | 32 +---
 tests/qmp-test.c | 10 +++-
 3 files changed, 109 insertions(+), 9 deletions(-)

diff --git a/monitor.c b/monitor.c
index fd6e9a6d28..3e07798442 100644
--- a/monitor.c
+++ b/monitor.c
@@ -167,6 +167,7 @@ typedef struct {
  * mode.
  */
 QmpCommandList *commands;
+bool qmp_caps[QMP_CAPABILITY__MAX];
 } MonitorQMP;
 
 /*
@@ -1036,8 +1037,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 "
@@ -1045,6 +1080,21 @@ void qmp_qmp_capabilities(Error **errp)
 return;
 }
 
+/* Enable QMP capabilities provided by the client if applicable. */
+if (has_enable) {
+qmp_caps_check(cur_mon, enable, &local_err);
+if (local_err) {
+/*
+ * Failed check on any of the capabilities will fail the
+ * entire command (and thus not apply any of the other
+ * capabilities that were also requested).
+ */
+error_propagate(errp, local_err);
+return;
+}
+qmp_caps_apply(cur_mon, enable);
+}
+
 cur_mon->qmp.commands = &qmp_commands;
 }
 
@@ -3942,14 +3992,29 @@ void monitor_resume(Monitor *mon)
 readline_show_prompt(mon->rs);
 }
 
-static QObject *get_qmp_greeting(void)
+static QObject *get_qmp_greeting(Monitor *mon)
 {
+QList *cap_list = qlist_new();
 QObject *ver = NULL;
+QMPCapability cap;
 
 qmp_marshal_query_version(NULL, &ver, NULL);
 
-return qobject_from_jsonf("{'QMP': {'version': %p, 'capabilities': []}}",
-  ver);
+for (cap = 0; cap < QMP_CAPABILITY__MAX; cap++) {
+if (!mon->use_io_thr && cap == QMP_CAPABILITY_OOB) {
+/* Monitors that are not using IOThread won't support OOB */
+continue;
+}
+qlist_append(cap_list, qstring_from_str(QMPCapability_str(cap)));
+}
+
+return qobject_from_jsonf("{'QMP': {'version': %p, 'capabilities': %p}}",
+  ver, cap_list);
+}
+
+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)
@@ -3960,7 +4025,8 @@ static void monitor_qmp_event(void *opaque, int event)
 switch (event) {
 case CHR_EVENT_OPENED:
 mon->qmp.commands = &qmp_cap_negotiation_commands;
-data = get_qmp_greeting();
+monitor_qmp_caps_reset(mon);
+data = get_qmp_greeting(mon);
 monit