From: Anthony Liguori <anthony@codemonkey.ws>
To: Andre Przywara <andre.przywara@amd.com>
Cc: qemu-devel@nongnu.org, aurelien@aurel32.net,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] resent: fix CPUID vendor override
Date: Mon, 24 May 2010 17:12:21 -0500 [thread overview]
Message-ID: <4BFAF9C5.403@codemonkey.ws> (raw)
In-Reply-To: <1274421493-9036-1-git-send-email-andre.przywara@amd.com>
On 05/21/2010 12:58 AM, Andre Przywara wrote:
> the meaning of vendor_override is actually the opposite of how it
> is currently used :-(
> Fix it to allow KVM to export the non-native CPUID vendor if
> explicitly requested by the user.
> The semantic is now as intended:
> - With TCG, the guest always sees the configured vendor.
> - With KVM, the default is to propagate the host's vendor
> - when explicitly requested via -cpu<base>,vendor=xxx obey this
> and use the specified vendor
>
> Signed-off-by: Andre Przywara<andre.przywara@amd.com>
>
This should go through uq/master. But I'm not sure that the new
behavior is really what's desired. It's certainly going to break
compatibility since -M pc-0.12 is going to show a different vendor_id by
default.
Regards,
Anthony Liguori
> ---
> target-i386/cpuid.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> Hi,
>
> this hasn't been picked up the last time I sent it out, are there any
> objections?
>
> Regards,
> Andre.
>
> diff --git a/target-i386/cpuid.c b/target-i386/cpuid.c
> index 56938e2..99d1f44 100644
> --- a/target-i386/cpuid.c
> +++ b/target-i386/cpuid.c
> @@ -962,7 +962,7 @@ static void get_cpuid_vendor(CPUX86State *env, uint32_t *ebx,
> * this if you want to use KVM's sysenter/syscall emulation
> * in compatibility mode and when doing cross vendor migration
> */
> - if (kvm_enabled()&& env->cpuid_vendor_override) {
> + if (kvm_enabled()&& ! env->cpuid_vendor_override) {
> host_cpuid(0, 0, NULL, ebx, ecx, edx);
> }
> }
>
parent reply other threads:[~2010-05-24 22:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1274421493-9036-1-git-send-email-andre.przywara@amd.com>]
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=4BFAF9C5.403@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=andre.przywara@amd.com \
--cc=aurelien@aurel32.net \
--cc=kvm@vger.kernel.org \
--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