All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: pbonzini@redhat.com, rth@twiddle.net, qemu-devel@nongnu.org,
	afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] target-i386: add a list of enforceable CPU models to the help output
Date: Wed, 26 Aug 2015 12:54:04 -0300	[thread overview]
Message-ID: <20150826155404.GH4230@thinpad.lan.raisama.net> (raw)
In-Reply-To: <1440407824-30037-1-git-send-email-pl@kamp.de>

On Mon, Aug 24, 2015 at 11:17:04AM +0200, 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>
[...]
> +/*
> + * Check if the CPU Definition is enforcable on the current host CPU
> + * and contains no unmigratable flags.
> + *
> + * Returns: true if the CPU can be enforced and migrated.
> + */
> +static bool x86_cpu_enforce_and_migratable(X86CPUDefinition *def)
> +{
> +    int i;
> +    for (i = 0; i < ARRAY_SIZE(feature_word_info); i++) {
> +        FeatureWordInfo *fw = &feature_word_info[i];
> +        uint32_t eax, ebx, ecx, edx, host;
> +        host_cpuid(fw->cpuid_eax, 0, &eax, &ebx, &ecx, &edx);

This isn't how you check if the CPU model can run in "enforce" mode.
Please read x86_cpu_filter_features().

Also, you can't tell if a CPU model is runnable in enforce mode unless
you know what's the accelerator being used (see
x86_cpu_filter_features()). How do you suggest we show
accelerator-specific information in help output?

-- 
Eduardo

  parent reply	other threads:[~2015-08-26 15:54 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
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 [this message]
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=20150826155404.GH4230@thinpad.lan.raisama.net \
    --to=ehabkost@redhat.com \
    --cc=afaerber@suse.de \
    --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 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.