All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pkrempa@redhat.com
Subject: Re: [PATCH v4 2/4] qapi: Add feature flags to commands in qapi
Date: Mon, 14 Oct 2019 14:23:57 +0200	[thread overview]
Message-ID: <87imor4isi.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20191011085027.28606-3-armbru@redhat.com> (Markus Armbruster's message of "Fri, 11 Oct 2019 10:50:25 +0200")

Markus Armbruster <armbru@redhat.com> writes:

> From: Peter Krempa <pkrempa@redhat.com>
>
> Similarly to features for struct types introduce the feature flags also
> for commands. This will allow notifying management layers of fixes and
> compatible changes in the behaviour of a command which may not be
> detectable any other way.
>
> The changes were heavily inspired by commit 6a8c0b51025.
>
> Signed-off-by: Peter Krempa <pkrempa@redhat.com>
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
>  docs/devel/qapi-code-gen.txt   |  7 ++++---
>  qapi/introspect.json           |  6 +++++-
>  scripts/qapi/commands.py       |  3 ++-
>  scripts/qapi/doc.py            |  3 ++-
>  scripts/qapi/expr.py           | 35 +++++++++++++++++++---------------
>  scripts/qapi/introspect.py     |  7 ++++++-
>  scripts/qapi/schema.py         | 22 +++++++++++++++++----
>  tests/qapi-schema/test-qapi.py |  3 ++-
>  8 files changed, 59 insertions(+), 27 deletions(-)
>
> diff --git a/docs/devel/qapi-code-gen.txt b/docs/devel/qapi-code-gen.txt
> index 64d9e4c6a9..637fa49977 100644
> --- a/docs/devel/qapi-code-gen.txt
> +++ b/docs/devel/qapi-code-gen.txt
> @@ -640,9 +640,10 @@ change in the QMP syntax (usually by allowing values or operations
>  that previously resulted in an error).  QMP clients may still need to
>  know whether the extension is available.
>  
> -For this purpose, a list of features can be specified for a struct type.
> -This is exposed to the client as a list of string, where each string
> -signals that this build of QEMU shows a certain behaviour.
> +For this purpose, a list of features can be specified for a command or
> +struct type.  This is exposed to the client as a list of strings,
> +where each string signals that this build of QEMU shows a certain
> +behaviour.
>  
>  Each member of the 'features' array defines a feature.  It can either
>  be { 'name': STRING, '*if': COND }, or STRING, which is shorthand for

Squashing in missing syntax update:

diff --git a/docs/devel/qapi-code-gen.txt b/docs/devel/qapi-code-gen.txt
index 637fa49977..45c93a43cc 100644
--- a/docs/devel/qapi-code-gen.txt
+++ b/docs/devel/qapi-code-gen.txt
@@ -457,7 +457,8 @@ Syntax:
                 '*gen': false,
                 '*allow-oob': true,
                 '*allow-preconfig': true,
-                '*if': COND }
+                '*if': COND,
+                '*features': FEATURES }
 
 Member 'command' names the command.

[...]


  reply	other threads:[~2019-10-14 12:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11  8:50 [PATCH v4 0/4] qapi: Add detection for the 'savevm' fix for blockdev Markus Armbruster
2019-10-11  8:50 ` [PATCH v4 1/4] tests/qapi-schema: Tidy up test output indentation Markus Armbruster
2019-10-11  9:07   ` Peter Krempa
2019-10-11  8:50 ` [PATCH v4 2/4] qapi: Add feature flags to commands in qapi Markus Armbruster
2019-10-14 12:23   ` Markus Armbruster [this message]
2019-10-11  8:50 ` [PATCH v4 3/4] tests: qapi: Test 'features' of commands Markus Armbruster
2019-10-15  6:51   ` Markus Armbruster
2019-10-11  8:50 ` [PATCH v4 4/4] qapi: Allow introspecting fix for savevm's cooperation with blockdev Markus Armbruster
2019-10-14 10:06   ` Kevin Wolf
2019-10-14 12:16     ` Markus Armbruster
2019-10-11  9:10 ` [PATCH v4 0/4] qapi: Add detection for the 'savevm' fix for blockdev Peter Krempa

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=87imor4isi.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pkrempa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.