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>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 0/3] target-i386: Don't trigger "check" warnings by default in KVM mode
Date: Mon, 2 Nov 2015 12:37:24 +0100 [thread overview]
Message-ID: <56374AF4.5070406@redhat.com> (raw)
In-Reply-To: <20151030191323.GA20436@thinpad.lan.raisama.net>
On 30/10/2015 20:13, Eduardo Habkost wrote:
> On Fri, Oct 30, 2015 at 05:00:57PM -0200, Eduardo Habkost wrote:
>> The x86 change to make "check" mode be enabled by default made QEMU print a
>> warning 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]
>>
>> Fix this by not enabling sse4a in qemu64 when in KVM mode.
>>
>> The long term solution will probably involve creating separate "tcg64" and
>> "kvm64" CPU models as defaults, so we can finally choose completely diffferent
>> defaults in the KVM- and TCG-specific models without making the
>> kvm_default_props list grow too mcuh.
>
> Note that we can have a much simpler solution to this: disabling SSE4A
> on qemu64 completely, even on TCG. This way we can use PC_COMPAT_2_4
> instead of the kvm_default_props compat hack.
>
> We can reenable SSE4A for TCG later (more exactly, we could enable
> everything from TCG_*_FEATURES) when we implement the kvm64/tcg64
> solution.
>
> What do you think?
I would prefer that to this series.
Another possibility (even more of a hack, but perhaps acceptable) is to
disable SSE4A in x86_cpu_load_def if kvm_enabled() and the host vendor
is not AMD. This is effectively what was already happening in 2.4 and
earlier.
Paolo
next prev parent reply other threads:[~2015-11-02 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 19:00 [Qemu-devel] [PATCH 0/3] target-i386: Don't trigger "check" warnings by default in KVM mode Eduardo Habkost
2015-10-30 19:00 ` [Qemu-devel] [PATCH 1/3] target-i386: Add optional class name to kvm_default_props Eduardo Habkost
2015-10-30 19:00 ` [Qemu-devel] [PATCH 2/3] pc: Create pc_compat_2_4() function Eduardo Habkost
2015-10-30 19:01 ` [Qemu-devel] [PATCH 3/3] target-i386: Don't enable SSE4A by default with KVM Eduardo Habkost
2015-10-30 19:13 ` [Qemu-devel] [PATCH 0/3] target-i386: Don't trigger "check" warnings by default in KVM mode Eduardo Habkost
2015-11-02 11:37 ` Paolo Bonzini [this message]
2015-11-03 16:41 ` Eduardo Habkost
2015-11-03 17:21 ` Paolo Bonzini
2015-11-03 17:54 ` Eduardo Habkost
2015-11-03 17:41 ` Eduardo Habkost
2015-11-03 17:49 ` Paolo Bonzini
2015-11-03 17:56 ` Eduardo Habkost
2015-11-03 19:53 ` 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=56374AF4.5070406@redhat.com \
--to=pbonzini@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).