From: Peter Lieven <pl@kamp.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Michael Mueller <mimu@linux.vnet.ibm.com>,
qemu-devel@nongnu.org,
David Hildenbrand <dahi@linux.vnet.ibm.com>,
pbonzini@redhat.com, Jiri Denemark <jdenemar@redhat.com>,
afaerber@suse.de, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] target-i386: add a list of enforceable CPU models to the help output
Date: Wed, 26 Aug 2015 20:46:42 +0200 [thread overview]
Message-ID: <55DE0992.70907@kamp.de> (raw)
In-Reply-To: <20150826183806.GA12239@thinpad.lan.raisama.net>
Am 26.08.2015 um 20:38 schrieb Eduardo Habkost:
> On Mon, Aug 24, 2015 at 09:36:23PM +0200, Peter Lieven wrote:
>> Am 24.08.2015 um 17:46 schrieb Eric Blake:
>>> On 08/24/2015 03:17 AM, Peter Lieven wrote:
>>>> this patch adds a probe that lists all enforceable and migrateable
>>>> CPU models to the -cpu help output. The idea is to know a priory
>>>> which CPU modules can be exposed to the user without loosing any
>>>> feature flags.
>>>>
>>>> Signed-off-by: Peter Lieven <pl@kamp.de>
>>>> ---
>>>> target-i386/cpu.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 1 file changed, 49 insertions(+)
>>> Is this same sort of listing available through QMP? Parsing '-cpu help'
>>> output is undesirable from libvirt point of view.
>>>
>> A good point. But is there a QMP command to list available CPU types?
>> In this case it should be easy to extend.
> Yes, that's query-cpu-definitions. See past discussion at:
> http://thread.gmane.org/gmane.comp.emulators.qemu/332554
>
> Some of the assumptions at that thread changed. See:
> http://thread.gmane.org/gmane.comp.emulators.qemu/342582/focus=346651
> That means runnability should depend only on the accelerator type, and
> not on the machine-type anymore.
Thanks for the pointer. But is it possible to query cpu definitions without
a running Qemu? Like passing a QMP command on the commandline and
receive the answer on stdout?
>
>> But, I wonder how to issue a QMP command before the vserver is actually
>> running? Is there a common way to do it?
> What's a vserver?
>
A Virtual Server.
Thanks,
Peter
next prev parent reply other threads:[~2015-08-26 18:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 9:17 [Qemu-devel] [PATCH] target-i386: add a list of enforceable CPU models to the help output Peter Lieven
2015-08-24 10:28 ` [Qemu-devel] CPU Model kvm64 and Windows2012R2 Peter Lieven
2015-08-24 11:50 ` Paolo Bonzini
2015-08-24 11:59 ` Peter Lieven
2015-08-24 11:51 ` Paolo Bonzini
2015-08-24 15:46 ` [Qemu-devel] [PATCH] target-i386: add a list of enforceable CPU models to the help output Eric Blake
2015-08-24 19:36 ` Peter Lieven
2015-08-26 18:38 ` Eduardo Habkost
2015-08-26 18:46 ` Peter Lieven [this message]
2015-08-26 19:00 ` Eduardo Habkost
2015-08-26 19:19 ` Peter Lieven
2015-08-24 20:22 ` Andreas Färber
2015-08-24 21:35 ` Peter Lieven
2015-08-26 15:54 ` Eduardo Habkost
2015-08-26 18:38 ` Peter Lieven
2015-08-26 19:12 ` Eduardo Habkost
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=55DE0992.70907@kamp.de \
--to=pl@kamp.de \
--cc=afaerber@suse.de \
--cc=dahi@linux.vnet.ibm.com \
--cc=ehabkost@redhat.com \
--cc=jdenemar@redhat.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).