From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] i386: fix '-cpu ?' output for host cpu type
Date: Mon, 2 Jul 2018 18:05:24 +0100 [thread overview]
Message-ID: <20180702170524.GE6438@redhat.com> (raw)
In-Reply-To: <153055056654.212317.4697363278304826913.stgit@bahia.lan>
On Mon, Jul 02, 2018 at 06:56:06PM +0200, Greg Kurz wrote:
> Since commit d6dcc5583e7, '-cpu ?' shows the description of the
> X86_CPU_TYPE_NAME("max") for the host CPU model:
>
> Enables all features supported by the accelerator in the current host
>
> instead of the expected:
>
> KVM processor with all supported host features
>
> or
>
> HVF processor with all supported host features
>
> This is caused by the early use of kvm_enabled() and hvf_enabled() in
> a class_init function. Since the accelerator isn't configured yet, both
> helpers return false unconditionally.
>
> A QEMU binary will only be compiled with one of these accelerators, not
> both. The appropriate description can thus be decided at build time.
>
> Signed-off-by: Greg Kurz <groug@kaod.org>
> ---
> target/i386/cpu.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index 1e6a7d0a7504..e5da60b28973 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -2838,13 +2838,13 @@ static void host_x86_cpu_class_init(ObjectClass *oc, void *data)
Sigh, yet another case of relying on runtime state during class_init impls.
> xcc->host_cpuid_required = true;
> xcc->ordering = 8;
>
> - if (kvm_enabled()) {
> - xcc->model_description =
> - "KVM processor with all supported host features ";
> - } else if (hvf_enabled()) {
> - xcc->model_description =
> - "HVF processor with all supported host features ";
> - }
> +#if defined(CONFIG_KVM)
> + xcc->model_description =
> + "KVM processor with all supported host features ";
> +#elif defined(CONFIG_HVF)
> + xcc->model_description =
> + "HVF processor with all supported host features ";
> +#endif
> }
>
> static const TypeInfo host_x86_cpu_type_info = {
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-07-02 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 16:56 [Qemu-devel] [PATCH] i386: fix '-cpu ?' output for host cpu type Greg Kurz
2018-07-02 17:05 ` Daniel P. Berrangé [this message]
2018-07-02 17:35 ` Paolo Bonzini
2018-07-02 19:23 ` Eric Blake
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=20180702170524.GE6438@redhat.com \
--to=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=groug@kaod.org \
--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 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.