From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] -cpu check, rdtscp and AMD KVM
Date: Thu, 12 Nov 2015 16:58:37 +0100 [thread overview]
Message-ID: <5644B72D.8080807@redhat.com> (raw)
In-Reply-To: <20151112152510.GM4180@thinpad.lan.raisama.net>
On 12/11/2015 16:25, Eduardo Habkost wrote:
> On Thu, Nov 12, 2015 at 11:53:44AM +0100, Paolo Bonzini wrote:
>> Eduardo,
>>
>> running QEMU 2.5 on SVM causes a warning because rdtscp is not supported
>> by KVM. While I can fix it, that leaves a warning on all existing kernels.
>
> You mean when using Opteron_G2 or newer, right? qemu64 and kvm64
> don't have rdtscp enabled.
>
>> What do you think is the best way forward?
>
> To simply remove rdtscp from all Opteron_G* models?
Not sure this is the right thing to do... Real hardware has it, and
going forward KVM will provide it.
Paolo
next prev parent reply other threads:[~2015-11-12 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 10:53 [Qemu-devel] -cpu check, rdtscp and AMD KVM Paolo Bonzini
2015-11-12 15:25 ` Eduardo Habkost
2015-11-12 15:58 ` Paolo Bonzini [this message]
2015-11-12 16:27 ` Eduardo Habkost
2015-11-12 16:35 ` Paolo Bonzini
2015-11-12 16:48 ` 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=5644B72D.8080807@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).