qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Igor Mammedov <imammedo@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] target-i386: Don't trigger CPUID warnings by default in KVM mode (in most hosts)
Date: Tue, 3 Nov 2015 21:22:30 +0100	[thread overview]
Message-ID: <56391786.5000808@redhat.com> (raw)
In-Reply-To: <1446580695-28525-1-git-send-email-ehabkost@redhat.com>



On 03/11/2015 20:58, Eduardo Habkost wrote:
> The x86 change to make "check" mode be enabled by default made QEMU print
> warnings in the default case if running in an Intel host:
> 
>   $ qemu-system-x86_64 -machine pc,accel=kvm
>   warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
> 
> There's also a warning when about missing the ABM feature if running on a Sandy
> Bridge or older host.
> 
> ABM is not available on Sandy Bridge and older, SSE4a is not available in any
> Intel host. We want to make the default CPU runnable in most hosts, so those
> features won't be enabled by default in KVM mode.
> 
> We should eventually have all features supported by TCG enabled by default in
> TCG mode, but as we don't have a good mechanism today to ensure we have
> different defaults in KVM and TCG mode, disable ABM and SSE4a in the qemu64 CPU
> model entirely.
> 
> Also, as we can't change the guest ABI in pc-*-2.4, disable "check" mode by
> default in pc-*-2.4 and older so we don't print spurious warnings.
> 
> Note that with this change, the qemu64 CPU model still requires a host
> supporting POPCNT (Nehalem or newer, and Opteron_G3 or newer).

Do we want to remove that one as well?

> Eduardo Habkost (3):
>   target-i386: Set "check=off" by default on pc-*-2.4 and older
>   target-i386: Remove SSE4a from qemu64 CPU model
>   target-i386: Remove ABM from qemu64 CPU model
> 
>  include/hw/i386/pc.h | 15 +++++++++++++++
>  target-i386/cpu.c    |  3 +--
>  2 files changed, 16 insertions(+), 2 deletions(-)
> 

In any case,

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

Paolo

  parent reply	other threads:[~2015-11-03 20:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 19:58 [Qemu-devel] [PATCH v2 0/3] target-i386: Don't trigger CPUID warnings by default in KVM mode (in most hosts) Eduardo Habkost
2015-11-03 19:58 ` [Qemu-devel] [PATCH v2 1/3] target-i386: Set "check=off" by default on pc-*-2.4 and older Eduardo Habkost
2015-11-03 19:58 ` [Qemu-devel] [PATCH v2 2/3] target-i386: Remove SSE4a from qemu64 CPU model Eduardo Habkost
2015-11-03 19:58 ` [Qemu-devel] [PATCH v2 3/3] target-i386: Remove ABM " Eduardo Habkost
2015-11-03 20:22 ` Paolo Bonzini [this message]
2015-11-03 22:54   ` [Qemu-devel] [PATCH v2 0/3] target-i386: Don't trigger CPUID warnings by default in KVM mode (in most hosts) Eduardo Habkost
2015-11-04 10:50     ` Paolo Bonzini

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=56391786.5000808@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mst@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).