From: Markus Armbruster <armbru@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] qapi: add query-display-options command
Date: Tue, 27 Nov 2018 10:05:03 +0100 [thread overview]
Message-ID: <87d0qquc00.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20181127065808.ph7pv6brnaeuyqix@sirius.home.kraxel.org> (Gerd Hoffmann's message of "Tue, 27 Nov 2018 07:58:08 +0100")
Gerd Hoffmann <kraxel@redhat.com> writes:
> Hi,
>
>> If it's not too much trouble, please tweak the commit message to be a
>> bit more explicit. Perhaps:
>>
>> Add query-display-options command, which allows querying the qemu
>> display configuration. This isn't particularly useful, except it
>> exposes QAPI type DisplayOptions in query-qmp-schema, so that
>> libvirt can discover recently added -display parameter rendernode
>> (commit d4dc4ab133b). Works around lack of sufficiently powerful
>> command line introspection.
>
> Done, pull req with this and other 3.1 fixes sent.
>
>> This should give me a fighting chance to remember deprecating the
>> command once we got sufficiently powerful command line introspection.
>
> I'm wondering how difficuilt it would be to add that when limiting that
> to the command line switches which already use qapi parsers (-blockdev
> and -display as far I know). Might increase the motivation of others to
> help moving parsers from whatever they do today (QemuOpts, ...) to qapi
> to get introspection support ;)
I like the idea. The clean way to do it would be a partial QAPIfication
of the command line. I'm wary of partial "we'll finish this eventually"
conversions. That said, the complete job may well be too large to
tackle in one go, giving us no choice.
prev parent reply other threads:[~2018-11-27 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 7:16 [Qemu-devel] [PATCH v3] qapi: add query-display-options command Gerd Hoffmann
2018-11-22 14:58 ` Erik Skultety
2018-11-23 6:26 ` Gerd Hoffmann
2018-11-26 14:01 ` Markus Armbruster
2018-11-26 15:13 ` Gerd Hoffmann
2018-11-26 16:58 ` Markus Armbruster
2018-11-27 6:58 ` Gerd Hoffmann
2018-11-27 9:05 ` Markus Armbruster [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=87d0qquc00.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@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.