From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-3.0] qapi: Make 'allow-oob' optional in SchemaInfoCommand
Date: Mon, 23 Jul 2018 10:14:12 -0500 [thread overview]
Message-ID: <d551df25-5f8b-0148-b8d7-8a5f1e25bfeb@redhat.com> (raw)
In-Reply-To: <20180718090557.17248-1-armbru@redhat.com>
On 07/18/2018 04:05 AM, Markus Armbruster wrote:
> Making 'allow-oob' optional in SchemaInfoCommand permits omitting it
> in the common case. Shrinks query-qmp-schema's output from 122.1KiB
> to 118.6KiB for me.
>
> Note that out-of-band execution is still experimental (you have to
> configure the monitor with x-oob=on to use it).
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
I see you have already posted the pull request, but the idea makes sense
to me. In general, making what was previously always output now be
optional can risk confusing a client that depends on the value being
present; but since allow-oob has not always been present, and since it
is still gated by x-oob=on, any sane client using OOB can easily be
coded to treat an absent indication as not allowing oob for that
particular command.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-07-23 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 9:05 [Qemu-devel] [PATCH for-3.0] qapi: Make 'allow-oob' optional in SchemaInfoCommand Markus Armbruster
2018-07-18 9:14 ` Peter Xu
2018-07-23 15:14 ` Eric Blake [this message]
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=d551df25-5f8b-0148-b8d7-8a5f1e25bfeb@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=peterx@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.