From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Amos Kong <akong@redhat.com>,
qemu-devel@nongnu.org, aliguori@amazon.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v2] update names in option tables to match with actual command-line spelling
Date: Mon, 17 Mar 2014 14:36:59 +0100 [thread overview]
Message-ID: <5326FA7B.2080902@redhat.com> (raw)
In-Reply-To: <87fvmh80ox.fsf@blackfin.pond.sub.org>
Il 17/03/2014 13:33, Markus Armbruster ha scritto:
> This patch changes:
>
> from to introduced in
> acpi acpitable 0c764a9 v1.5.0
> boot-opts boot 3d3b830 v1.0
> smp-opts smp 12b7f57 v1.6.0
>
> All three have calcified into ABI already.
What has calcified into ABI is only what has likely been used as ABI.
The other is an ABI that won't be nice to break, but it is not calcified
yet.
There are two aspects of this:
1) QMP queries. Did any of the above conversions introduce new
sub-options? Or was any suboption introduced after that point? If not,
there's hardly a reason for anyone to query for acpi/boot-opts/smp-opts
QemuOpts
2) readconfig. I think readconfig is not practically usable until at
least memory will be part of it. For this reason, -readconfig is not a
worry; not yet at least: it will be in 2.1 once -m is converted.
>> > I'm for including this patch in 2.0.
> Not without explaining the ABI breakage in the commit message. We
> should also make sure to cover it in the release notes[*].
I agree.
> Moreover, if exceptions from the rule "QemuOptsList name must match the
> name of the (non-sugared) command line option using it" are or will be
> permissible, then Amos's comment on QemuOptsList member name needs to be
> clarified.
I like your idea of -memory as a synonym for -m.
Paolo
prev parent reply other threads:[~2014-03-17 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 5:24 [Qemu-devel] [PATCH v2] update names in option tables to match with actual command-line spelling Amos Kong
2014-03-17 8:23 ` Markus Armbruster
2014-03-17 10:50 ` Paolo Bonzini
2014-03-17 12:33 ` Markus Armbruster
2014-03-17 13:36 ` Paolo Bonzini [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=5326FA7B.2080902@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=akong@redhat.com \
--cc=aliguori@amazon.com \
--cc=armbru@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).