From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: [Qemu-devel] Re: [PATCH][STABLE] fix CPUID vendor override
Date: Sun, 11 Apr 2010 22:31:24 +0300 [thread overview]
Message-ID: <4BC2238C.2070009@redhat.com> (raw)
In-Reply-To: <1271013662-7640-1-git-send-email-andre.przywara@amd.com>
On 04/11/2010 10:21 PM, 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.
>
> Signed-off-by: Andre Przywara<andre.przywara@amd.com>
> ---
> target-i386/helper.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> I will send a refactoring patch including this fix for git HEAD later.
>
> Regards,
> Andre.
>
> diff --git a/target-i386/helper.c b/target-i386/helper.c
> index 9d7fec3..c17adc1 100644
> --- a/target-i386/helper.c
> +++ b/target-i386/helper.c
> @@ -1655,7 +1655,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);
> }
> }
>
Why is the original code wrong? I would say vendor_override means
overriding the qemu-picked vendor ID in favour of the host cpuid.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-04-11 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 19:21 [Qemu-devel] [PATCH][STABLE] fix CPUID vendor override Andre Przywara
2010-04-11 19:29 ` [Qemu-devel] " Avi Kivity
2010-04-11 19:42 ` Andre Przywara
2010-04-11 19:31 ` Avi Kivity [this message]
2010-04-11 19:49 ` Andre Przywara
2010-04-18 21:42 ` Aurelien Jarno
2010-04-18 22:48 ` Andre Przywara
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=4BC2238C.2070009@redhat.com \
--to=avi@redhat.com \
--cc=andre.przywara@amd.com \
--cc=aurelien@aurel32.net \
--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 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.