From: Avi Kivity <avi@redhat.com>
To: "Mao, Junjie" <junjie.mao@intel.com>
Cc: "'kvm@vger.kernel.org'" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: x86: Check INVPCID feature bit in EBX of leaf 7
Date: Tue, 04 Sep 2012 14:58:38 +0300 [thread overview]
Message-ID: <5045ECEE.60506@redhat.com> (raw)
In-Reply-To: <EF5A1D57CFBD5A4BA5EB3ED985B6DC6E0316CE65@SHSMSX101.ccr.corp.intel.com>
On 09/01/2012 11:12 AM, Mao, Junjie wrote:
> Checks and operations on the INVPCID feature bit should use EBX of CPUID leaf 7
> instead of ECX.
>
> Signed-off-by: Junjie Mao <junjie.mao@intel.com>
> ---
> arch/x86/kvm/vmx.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index c00f03d..002b4a5 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -6575,7 +6575,7 @@ static void vmx_cpuid_update(struct kvm_vcpu *vcpu)
> /* Exposing INVPCID only when PCID is exposed */
> best = kvm_find_cpuid_entry(vcpu, 0x7, 0);
> if (vmx_invpcid_supported() &&
> - best && (best->ecx & bit(X86_FEATURE_INVPCID)) &&
> + best && (best->ebx & bit(X86_FEATURE_INVPCID)) &&
> guest_cpuid_has_pcid(vcpu)) {
> exec_control |= SECONDARY_EXEC_ENABLE_INVPCID;
> vmcs_write32(SECONDARY_VM_EXEC_CONTROL,
> @@ -6585,7 +6585,7 @@ static void vmx_cpuid_update(struct kvm_vcpu *vcpu)
> vmcs_write32(SECONDARY_VM_EXEC_CONTROL,
> exec_control);
> if (best)
> - best->ecx &= ~bit(X86_FEATURE_INVPCID);
> + best->ebx &= ~bit(X86_FEATURE_INVPCID);
> }
> }
>
Patch is whitespace damaged, please fix.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-09-04 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 8:12 [PATCH] KVM: x86: Check INVPCID feature bit in EBX of leaf 7 Mao, Junjie
2012-09-04 11:58 ` Avi Kivity [this message]
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=5045ECEE.60506@redhat.com \
--to=avi@redhat.com \
--cc=junjie.mao@intel.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 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.