From: Markus Armbruster <armbru@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Peter Krempa <pkrempa@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qmp: add query-qemu-capabilities
Date: Tue, 26 Feb 2019 08:23:17 +0100 [thread overview]
Message-ID: <87r2bvm2sa.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20190225170646.GH379@stefanha-x1.localdomain> (Stefan Hajnoczi's message of "Mon, 25 Feb 2019 17:06:46 +0000")
Stefan Hajnoczi <stefanha@redhat.com> writes:
> On Mon, Feb 25, 2019 at 09:50:26AM +0100, Markus Armbruster wrote:
>> Stefan Hajnoczi <stefanha@redhat.com> writes:
>>
>> > QMP clients can usually detect the presence of features via schema
>> > introspection. There are rare features that do not involve schema
>> > changes and are therefore impossible to detect with schema
>> > introspection.
>> >
>> > This patch adds the query-qemu-capabilities command. It returns a list
>> > of capabilities that this QEMU supports.
>>
>> The name "capabilities" could be confusing, because we already have QMP
>> capabilities, complete with command qmp_capabilities. Would "features"
>> work?
>
> Sure, will fix.
>
>> > The decision to make this a command rather than something statically
>> > defined in the schema is intentional. It allows QEMU to decide which
>> > capabilities are available at runtime, if necessary.
>> >
>> > This new interface is necessary so that QMP clients can discover that
>> > migrating disk image files is safe with cache.direct=off on Linux.
>> > There is no other way to detect whether or not QEMU supports this.
>>
>> I think what's unsaid here is that we don't want to make a completely
>> arbitrary schema change just to carry this bit of information. We
>> could, but we don't want to. Correct?
>
> Yes, exactly.
Then let's rephrase a little:
QMP clients can usually detect the presence of features via schema
introspection. There are rare features that do not involve schema
changes. To make them detectable with schema introspection, we'd
have to make some arbitrary schema change. Annoying.
The new query-qemu-features command lets us avoid that. It returns
a list of features supported by this QEMU.
The decision to make this a command rather than something statically
defined in the schema is intentional. It allows QEMU to decide which
capabilities are available at runtime, if necessary.
Use the new command to declare migrating disk image files is safe
with cache.direct=off on Linux.
[...]
next prev parent reply other threads:[~2019-02-26 7:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 15:32 [Qemu-devel] [PATCH] qmp: add query-qemu-capabilities Stefan Hajnoczi
2019-02-25 8:50 ` Markus Armbruster
2019-02-25 9:28 ` Peter Krempa
2019-02-25 17:40 ` Stefan Hajnoczi
2019-02-26 7:44 ` Peter Krempa
2019-02-26 9:09 ` Markus Armbruster
2019-02-27 14:51 ` Stefan Hajnoczi
2019-02-27 19:25 ` Markus Armbruster
2019-02-27 15:15 ` Stefan Hajnoczi
2019-02-27 15:25 ` Daniel P. Berrangé
2019-02-27 17:12 ` Stefan Hajnoczi
2019-02-25 17:06 ` Stefan Hajnoczi
2019-02-26 7:23 ` Markus Armbruster [this message]
2019-03-08 10:35 ` Stefan Hajnoczi
2019-03-08 12:15 ` Markus Armbruster
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=87r2bvm2sa.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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.