From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 4/4] dont trim the guest's hypervisor CPUID bit in KVM if the guest requests it
Date: Wed, 24 Jun 2009 14:28:20 +0300 [thread overview]
Message-ID: <4A420DD4.4020905@redhat.com> (raw)
In-Reply-To: <1245840276-12702-4-git-send-email-andre.przywara@amd.com>
On 06/24/2009 01:44 PM, Andre Przywara wrote:
> Signed-off-by: Andre Przywara<andre.przywara@amd.com>
> ---
> arch/x86/kvm/x86.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index e6e61ee..6ad0f93 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -1415,7 +1415,7 @@ static void do_cpuid_ent(struct kvm_cpuid_entry2 *entry, u32 function,
> 0 /* Reserved */ | F(CX16) | 0 /* xTPR Update, PDCM */ |
> 0 /* Reserved, DCA */ | F(XMM4_1) |
> F(XMM4_2) | 0 /* x2APIC */ | F(MOVBE) | F(POPCNT) |
> - 0 /* Reserved, XSAVE, OSXSAVE */;
> + 0 /* Reserved, XSAVE, OSXSAVE */ | F(HYPERVISOR);
>
I think this should be handled in qemu, since it isn't really a cpu bit.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-24 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 10:44 [PATCH 1/4] ignore AMDs HWCR register access to set the FFDIS bit Andre Przywara
2009-06-24 10:44 ` [PATCH 2/4] ignore reads from AMDs C1E enabled MSR Andre Przywara
2009-06-24 10:44 ` [PATCH 3/4] ignore PCI ECS I/O enablement Andre Przywara
2009-06-24 10:44 ` [PATCH 4/4] dont trim the guest's hypervisor CPUID bit in KVM if the guest requests it Andre Przywara
2009-06-24 11:28 ` Avi Kivity [this message]
2009-06-24 12:28 ` Andre Przywara
2009-06-24 13:28 ` Andre Przywara
2009-06-24 11:31 ` [PATCH 3/4] ignore PCI ECS I/O enablement Avi Kivity
2009-06-24 13:37 ` Andre Przywara
2009-07-01 9:50 ` Avi Kivity
2009-06-24 11:37 ` [PATCH 1/4] ignore AMDs HWCR register access to set the FFDIS bit Avi Kivity
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=4A420DD4.4020905@redhat.com \
--to=avi@redhat.com \
--cc=andre.przywara@amd.com \
--cc=kvm@vger.kernel.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