From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
Anthony Liguori <aliguori@us.ibm.com>,
"Richard W.M. Jones" <rjones@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option
Date: Mon, 25 Jul 2011 07:23:26 -0500 [thread overview]
Message-ID: <4E2D603E.8050908@codemonkey.ws> (raw)
In-Reply-To: <4E2D4CA1.1080504@siemens.com>
On 07/25/2011 05:59 AM, Jan Kiszka wrote:
> On 2011-07-25 12:45, Richard W.M. Jones wrote:
>> That's an excuse, not a practical solution. We have to be able to
>> work with any qemu. eg. the qemu in current Fedora Rawhide which
>> supports only -machine accel=, or qemu in other distros which are also
>> branched from arbitrary git releases, or qemu that people compile
>> themselves.
>
> In principle, this is first of all a Rawhide problem. Upstream really
> can't babysit every distro doing crazy things with arbitrary devel
> snapshots. These patches were public, and the maintainers had a fair
> chance to realize that the interface was not yet set in stone.
>
>>
>> Parsing -help output and guesswork isn't scalable, and this is not
>> exactly the first time that people have complained about this.
>
> I agree. That's why we try hard to release stable interfaces and then
> maintain them.
>
>>
>> (Yes, libvirt and libguestfs do allow callers to mechanically query
>> their respective APIs for capabilities.)
>
> Maybe Anthony's (Liguori) rework of the QEMU config interfaces will
> provide a better reflections, haven't checked. But for now you need to
> stick with this model, specifically when you want to maintain all the
> distro forks.
Yes, it will, but it doesn't fix this particular. Problem. Until we do
a release, we reserve the right to change the syntax of newly introduced
command line options.
I don't think any level of introspection changes this.
Regards,
Anthony Liguori
>
> Jan
>
next prev parent reply other threads:[~2011-07-25 12:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 10:38 [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option Jan Kiszka
2011-07-23 10:39 ` [Qemu-devel] [RESEND][PATCH 2/2] Deprecate -M command line options Jan Kiszka
2011-07-23 15:43 ` [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option Anthony Liguori
2011-07-25 9:41 ` Richard W.M. Jones
2011-07-25 10:33 ` Jan Kiszka
2011-07-25 10:45 ` Richard W.M. Jones
2011-07-25 10:59 ` Jan Kiszka
2011-07-25 11:39 ` Markus Armbruster
2011-07-25 11:48 ` Jan Kiszka
2011-07-25 16:11 ` [Qemu-devel] [PATCH] Allow to leave type on default in -machine Jan Kiszka
2011-07-25 16:21 ` Richard W.M. Jones
2011-07-25 16:33 ` Alexander Graf
2011-07-29 14:37 ` Anthony Liguori
2011-07-25 12:23 ` Anthony Liguori [this message]
2011-07-25 11:48 ` [Qemu-devel] [RESEND][PATCH v3] Generalize -machine command line option Peter Maydell
2011-07-25 12:05 ` Peter Maydell
2011-07-25 12:18 ` Jan Kiszka
2011-07-25 12:22 ` Peter Maydell
2011-07-25 12:27 ` Jan Kiszka
2011-07-25 12:44 ` Alexander Graf
2011-07-25 12:47 ` Anthony Liguori
2011-07-25 12:49 ` Richard W.M. Jones
2011-07-25 12:53 ` Alexander Graf
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=4E2D603E.8050908@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Ian.Campbell@eu.citrix.com \
--cc=aliguori@us.ibm.com \
--cc=anthony.perard@citrix.com \
--cc=jan.kiszka@siemens.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 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.