From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Daniel Berrange <berrange@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
John Snow <jsnow@redhat.com>
Subject: Re: KVM call for agenda for 2020-10-06
Date: Wed, 7 Oct 2020 19:50:20 +0200 [thread overview]
Message-ID: <8fce8f99-56bd-6a87-9789-325d6ffff54d@redhat.com> (raw)
In-Reply-To: <CAJSP0QVZcEQueXG1gjwuLszdUtXWi1tgB5muLL6QHJjNTOmyfQ@mail.gmail.com>
On 06/10/20 20:21, Stefan Hajnoczi wrote:
> * Does command-line order matter?
> * Two options: allow any order OR left-to-right ordering
> * Andrea Bolognani: Most users expect left-to-right ordering,
> why allow any order?
> * Eduardo Habkost: Can we enforce left-to-right ordering or do
> we need to follow the deprecation process?
> * Daniel Berrange: Solve compability by introducing new
> binaries without the burden of backwards compability
I think "new binaries" shouldn't even have a command line; all
configuration should happen through QMP commands. Those are naturally
time-ordered, which is equivalent to left-to-right, and therefore the
question is sidestepped. Perhaps even having a command line in
qemu-storage-daemon was a mistake.
For "old binaries" we are not adding too many options, so apart from the
nasty distinction between early and late objects we're at least not
making it worse.
The big question to me is whether the configuration should be
QAPI-based, that is based on QAPI structs, or QMP-based. If the latter,
"object-add" (and to a lesser extent "device-add") are fine mechanisms
for configuration. There is still need for better QOM introspection,
but it would be much simpler than doing QOM object creation via QAPI
struct, if at all possible.
Paolo
next prev parent reply other threads:[~2020-10-07 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 9:09 KVM call for agenda for 2020-10-06 Juan Quintela
2020-10-02 15:16 ` John Snow
2020-10-05 14:46 ` Stefan Hajnoczi
2020-10-06 18:21 ` Stefan Hajnoczi
2020-10-07 17:50 ` Paolo Bonzini [this message]
2020-10-07 18:04 ` Daniel P. Berrangé
2020-10-08 11:25 ` Markus Armbruster
2020-10-08 14:15 ` Paolo Bonzini
2020-10-08 8:03 ` Kevin Wolf
2020-10-09 16:45 ` Eduardo Habkost
2020-10-10 4:41 ` 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=8fce8f99-56bd-6a87-9789-325d6ffff54d@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).