From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, rth@twiddle.net, afaerber@suse.de,
ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH] target-i386: add a list of enforceable CPU models to the help output
Date: Mon, 24 Aug 2015 09:46:55 -0600 [thread overview]
Message-ID: <55DB3C6F.3010206@redhat.com> (raw)
In-Reply-To: <1440407824-30037-1-git-send-email-pl@kamp.de>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
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.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-08-24 15:47 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 ` Eric Blake [this message]
2015-08-24 19:36 ` [Qemu-devel] [PATCH] target-i386: add a list of enforceable CPU models to the help output Peter Lieven
2015-08-26 18:38 ` Eduardo Habkost
2015-08-26 18:46 ` Peter Lieven
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=55DB3C6F.3010206@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--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).