From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>, qemu-ppc <qemu-ppc@nongnu.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [Qemu-devel] [PATCH] kvm: Add a new machine property kvm_type
Date: Mon, 04 Nov 2013 18:57:22 +0100 [thread overview]
Message-ID: <5277E002.5060008@redhat.com> (raw)
In-Reply-To: <5277DC2D.1090004@suse.de>
Il 04/11/2013 18:41, Andreas Färber ha scritto:
>> > I agree that we need some way to programmatically list all machine options.
> I wonder if it would make sense to mirror all -machine options as
> dynamic properties on /machine? :)
> Their addition could still be driven by the declarative format.
> We could then easily not only list but also inspect the values of those
> options at runtime.
Yes, I agree. Perhaps not all of them however; probably not accel= and
probably not kvm_type too. In fact, what I don't like about this patch
is that it doesn't really feel "right" to put it in -machine. On the
other hand we definitely do not want to split it further to -accel. Oh
well, it seems like designing the right command-line interface is the
hardest part of doing QEMU.
Paolo
> It wouldn't immediately solve Jan's documentation problem, but that's
> more general than just -machine, isn't it?
>
> CC'ing Anthony and Paolo.
next prev parent reply other threads:[~2013-11-04 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 16:53 [Qemu-devel] [PATCH] kvm: Add a new machine property kvm_type Aneesh Kumar K.V
2013-11-04 12:28 ` Alexander Graf
2013-11-04 13:28 ` Jan Kiszka
2013-11-04 13:30 ` Alexander Graf
2013-11-04 13:32 ` Jan Kiszka
2013-11-04 13:55 ` Alexander Graf
2013-11-04 17:41 ` Andreas Färber
2013-11-04 17:57 ` Paolo Bonzini [this message]
2013-11-06 15:08 ` Aneesh Kumar K.V
2013-11-07 7:27 ` Jan Kiszka
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=5277E002.5060008@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=paulus@samba.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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.