From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Osier Yang <jyang@redhat.com>,
libvir-list@redhat.com, rjones@redhat.com,
qemu-devel <qemu-devel@nongnu.org>,
laine@redhat.com, anthony@codemonkey.ws,
Amos Kong <akong@redhat.com>
Subject: Re: [Qemu-devel] fix/re-do query-command-line-options
Date: Tue, 28 Jan 2014 13:05:35 +0100 [thread overview]
Message-ID: <52E79D0F.2080200@redhat.com> (raw)
In-Reply-To: <87iot4jp6r.fsf@blackfin.pond.sub.org>
Il 28/01/2014 12:55, Markus Armbruster ha scritto:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
>> Il 28/01/2014 10:36, Markus Armbruster ha scritto:
>>> I think the data you can usefully collect with this approach is
>>> approximately the data getopt_long()[*] gets: list of named command line
>>> options, and whether they take an argument.
>>>
>>> You can use this data to fill in options not covered by QemuOpts. This
>>> is a definite improvement.
>>>
>>> It still falls short of fully solving the command line introspection
>>> problem.
>>>
>>> However, I'm not into rejecting imperfect incremental improvements we
>>> can have now in favor of perfect solutions we can maybe have some day.
>>> Go right ahead with your incremental improvement!
>>
>> It depends. If we can agree on the following:
>>
>> (a) do not add non-QemuOpts options (we haven't for a while)
>
> That would mean we can't ever add an option that doesn't take an
> argument again.
We can add it under an existing QemuOpts group or invent a new one (like
we did for -rt or -msg).
> However, we need to somehow stuff those into QemuOpts anyway, so
> -readconfig / -writeconfig can cover them.
Yep.
>> (b) document the QemuOpts schema for -acpitable, -smbios, -netdev,
>> -net. These options validate the options with OptsVisitor, so we could
>> do without QemuOpts schema, but we know the schema won't bitrot
>> because we never remove suboptions.
>
> -device?
-device already provides its own introspection via "qom-list-types" and
"-device driver,?".
-object doesn't have an equivalent of "-device driver,?", but that's a
separate problem.
>> (a) there is no need to cover non-QemuOpts options in
>> query-command-line-options. libvirt can treat them as crystallized.
>
> Some options are undef #ifdef. That's actually a good idea, because it
> permits finding out which options are available via command line
> introspection.
>
> Now, what if a non-QemuOpts option is under #ifdef? I haven't
> checked... Even if there isn't one now, are we ready to give up the
> ability to do that for good?
There are some:
- legacy slirp options -tftp/-bootp/-redir/-smb
- -enable-fips is what triggered this discussion, but we found another
solution in Libvirt
- -tpmdev is enabled only if CONFIG_TPM, but its presence can be queried
via qom-list-types too.
>> (b) documenting the schemata is not harder than what Amos proposed.
>>
>> (c) schema inspection for objects remains a problem, but one that we
>> need to solve anyway so it doesn't affect query-command-line-options.
>
> As long as we don't have such schema inspection, I'm rather reluctant to
> reject alternative means to solve problems people have *now*.
Note the "doesn't affect query-command-line-options" part. Amos's patch
do not solve the problem of which classes can be instantiated with
-object, or of which properties can be used.
Paolo
>> Do you agree?
>
> It depends :)
>
next prev parent reply other threads:[~2014-01-28 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 2:19 [Qemu-devel] fix/re-do query-command-line-options Amos Kong
2014-01-27 10:24 ` [Qemu-devel] [resend] " Amos Kong
2014-01-27 16:27 ` [Qemu-devel] " Eric Blake
2014-01-28 9:36 ` Markus Armbruster
2014-01-28 10:01 ` Paolo Bonzini
2014-01-28 11:55 ` Markus Armbruster
2014-01-28 12:05 ` Paolo Bonzini [this message]
2014-01-28 13:16 ` Markus Armbruster
2014-01-28 13:35 ` Paolo Bonzini
2014-01-28 14:28 ` Markus Armbruster
2014-01-28 15:33 ` Paolo Bonzini
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=52E79D0F.2080200@redhat.com \
--to=pbonzini@redhat.com \
--cc=akong@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=jyang@redhat.com \
--cc=laine@redhat.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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 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).