From: Peter Krempa <pkrempa@redhat.com>
To: Markus Armbruster <armbru@pond.sub.org>
Cc: libvir-list@redhat.com, Andrea Bolognani <abologna@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: query-command-line-options (was: [PATCH 1/7] qemu: capabilities: Introduce QEMU_CAPS_MACHINE_ACPI)
Date: Tue, 7 Mar 2023 15:28:46 +0100 [thread overview]
Message-ID: <ZAdKHkUIKjPLhFn7@angien.pipo.sk> (raw)
In-Reply-To: <87jzzsc320.fsf_-_@pond.sub.org>
On Tue, Mar 07, 2023 at 10:40:23 +0100, Markus Armbruster wrote:
> [Resent with cc: qemu-devel and adjusted subject, sorry for the noise]
>
> abologna at redhat.com (Andrea Bolognani) writes:
>
> > On Mon, Feb 27, 2023 at 06:25:23PM +0100, Peter Krempa wrote:
> >> On Mon, Feb 27, 2023 at 08:44:57 -0800, Andrea Bolognani wrote:
[...]
> > Another example I've found is "smp-opts", which seems to be used to
> > implement the -smp option. Once again, in the JSON we find "smp-opts"
> > instead of "smp".
> >
> > I think it would be worthwile to check with the QEMU developers and
> > make sure that they're aware of this behavior. Is it intended? Is it
> > documented anywhere? It certainly seems extremely confusing to me.
>
> query-command-line-options has... issues.
>
> First, it's generally[*] limited to options that use QemuOpts.
>
> Second, it reports configuration group names, which are often, but not
> always the same as the option name. The exceptions you just have to
> know. Group name "acpi" vs. option name "acpitable" is one.
Ah! so that's where 'acpi' comes from.
>
> Third, information on option parameters can be incomplete, or missing
> entirely.
>
> Fourth, even when it's there, it's often insufficiently detailed.
>
> These are design issues. I believe the command cannot be fixed, only
> replaced.
>
> See my talk "QEMU interface introspection: From hacks to
> solutions", KVM Forum 2015.
> Video at https://www.youtube.com/watch?v=IEa8Ao8_B9o
> Slides at http://www.linux-kvm.org/images/7/7a/02x05-Aspen-Markus_Armbruster-QEMU_interface_introspection.pdf
>
> Questions?
In the end I've dropped the patch detecting the presence of the 'acpi'
option of -machine as queried via query-command-line-options, as we need
to know it per-machine type. That is now reported by qemu in
query-machines, so we don't need to add more querying from
query-command-line options.
In fact I strive to eliminate it after your suggestions, but we can't
still detect the few outstanding flags from anywhere else.
List of currently outstanding queries using query-command-line-options:
{ "fsdev", "multidevs", QEMU_CAPS_FSDEV_MULTIDEVS },
{ "machine", "hpet", QEMU_CAPS_MACHINE_HPET },
{ "sandbox", NULL, QEMU_CAPS_SECCOMP_SANDBOX },
{ "spice", NULL, QEMU_CAPS_SPICE },
{ "spice", "gl", QEMU_CAPS_SPICE_GL },
{ "spice", "rendernode", QEMU_CAPS_SPICE_RENDERNODE },
{ "vnc", "power-control", QEMU_CAPS_VNC_POWER_CONTROL },
next prev parent reply other threads:[~2023-03-07 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1677511354.git.pkrempa@redhat.com>
[not found] ` <8718b22eda052662087087b4ce659b054974c9e0.1677511354.git.pkrempa@redhat.com>
[not found] ` <CABJz62PHsQHiyo06PtfcDeS1LddYyDw2pC_seObtZcLR5cPQyQ@mail.gmail.com>
[not found] ` <Y/zng8+7s05O0tRd@angien.pipo.sk>
[not found] ` <CABJz62OMWXAx_ExYqvvg1DvcHkiP+SkwNMQZ+56QwoHpsNBqGA@mail.gmail.com>
2023-03-07 9:40 ` query-command-line-options (was: [PATCH 1/7] qemu: capabilities: Introduce QEMU_CAPS_MACHINE_ACPI) Markus Armbruster
2023-03-07 14:28 ` Peter Krempa [this message]
2023-05-26 8:54 ` query-command-line-options Markus Armbruster
2023-05-26 11:07 ` query-command-line-options Ján Tomko
2023-05-26 12:10 ` query-command-line-options 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=ZAdKHkUIKjPLhFn7@angien.pipo.sk \
--to=pkrempa@redhat.com \
--cc=abologna@redhat.com \
--cc=armbru@pond.sub.org \
--cc=armbru@redhat.com \
--cc=libvir-list@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).