kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xiaoyao Li <xiaoyao.li@intel.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
	kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] KVM: CPUID: Check limit first when emulating CPUID instruction
Date: Tue, 10 Sep 2019 17:52:23 +0800	[thread overview]
Message-ID: <f636f8063742ceb6f802f26f218b90e4b9b7fcc7.camel@intel.com> (raw)
In-Reply-To: <20190910082442.142702-2-xiaoyao.li@intel.com>

On Tue, 2019-09-10 at 16:24 +0800, Xiaoyao Li wrote:
> When limit checking is required, it should be executed first, which is
> consistent with the CPUID specification.
> 
> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
> ---
>  arch/x86/kvm/cpuid.c | 50 +++++++++++++++++++++++++-------------------
>  1 file changed, 28 insertions(+), 22 deletions(-)
> 
> diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
> index 22c2720cd948..866546b4d834 100644
> --- a/arch/x86/kvm/cpuid.c
> +++ b/arch/x86/kvm/cpuid.c
> @@ -952,23 +952,33 @@ struct kvm_cpuid_entry2 *kvm_find_cpuid_entry(struct
> kvm_vcpu *vcpu,
>  EXPORT_SYMBOL_GPL(kvm_find_cpuid_entry);
>  
>  /*
> - * If no match is found, check whether we exceed the vCPU's limit
> - * and return the content of the highest valid _standard_ leaf instead.
> - * This is to satisfy the CPUID specification.
> + * Based on CPUID specification, if leaf number exceeds the vCPU's limit,
> + * it should return the content of the highest valid _standard_ leaf instead.
> + * Note: *found is set true only means the queried leaf number doesn't exceed
> + * the maximum leaf number of basic or extented leaf.
>   */
> -static struct kvm_cpuid_entry2* check_cpuid_limit(struct kvm_vcpu *vcpu,
> -                                                  u32 function, u32 index)
> +static struct kvm_cpuid_entry2* cpuid_check_limit(struct kvm_vcpu *vcpu,
> +                                                  u32 function, u32 index,
> +						  bool *found)
>  {
>  	struct kvm_cpuid_entry2 *maxlevel;
>  
>  	maxlevel = kvm_find_cpuid_entry(vcpu, function & 0x80000000, 0);
> -	if (!maxlevel || maxlevel->eax >= function)
> +	if (!maxlevel)
>  		return NULL;
> -	if (function & 0x80000000) {
> -		maxlevel = kvm_find_cpuid_entry(vcpu, 0, 0);
> -		if (!maxlevel)
> -			return NULL;
> +
> +	if (maxlevel->eax >= function) {
> +		if (found)
> +			*found = true;
> +		return kvm_find_cpuid_entry(vcpu, function, index);
>  	}
> +
> +	if (function & 0x80000000)
> +		maxlevel = kvm_find_cpuid_entry(vcpu, 0, 0);
> +
> +	if (!maxlevel)
> +		return NULL;
> +
>  	return kvm_find_cpuid_entry(vcpu, maxlevel->eax, index);
>  }
>  
> @@ -977,26 +987,22 @@ bool kvm_cpuid(struct kvm_vcpu *vcpu, u32 *eax, u32
> *ebx,
>  {
>  	u32 function = *eax, index = *ecx;
>  	struct kvm_cpuid_entry2 *best;
> -	bool entry_found = true;
> +	bool entry_found = false;
>  
> -	best = kvm_find_cpuid_entry(vcpu, function, index);
> +	if (check_limit)
> +		best = cpuid_check_limit(vcpu, function, index, &entry_found);
> +	else
> +		best = kvm_find_cpuid_entry(vcpu, function, index);
>  
> -	if (!best) {
> -		entry_found = false;
> -		if (!check_limit)
> -			goto out;
> -
> -		best = check_cpuid_limit(vcpu, function, index);
> -	}
> -
> -out:
>  	if (best) {
>  		*eax = best->eax;
>  		*ebx = best->ebx;
>  		*ecx = best->ecx;
>  		*edx = best->edx;
> -	} else
> +	} else {
> +		entry_found = false;
>  		*eax = *ebx = *ecx = *edx = 0;
> +	}
>  	trace_kvm_cpuid(function, *eax, *ebx, *ecx, *edx, entry_found);
>  	return entry_found;
>  }

Just realise the entry_found is not set true if found in no limit checking case.
Will send v2. 


  reply	other threads:[~2019-09-10  9:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10  8:24 [PATCH 0/2] KVM: CPUID: CPUID emulation flow adjustment and one minor refinement when updating maxphyaddr Xiaoyao Li
2019-09-10  8:24 ` [PATCH 1/2] KVM: CPUID: Check limit first when emulating CPUID instruction Xiaoyao Li
2019-09-10  9:52   ` Xiaoyao Li [this message]
2019-09-10  8:24 ` [PATCH 2/2] KVM: CPUID: Put maxphyaddr updating together with virtual address width checking Xiaoyao Li

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=f636f8063742ceb6f802f26f218b90e4b9b7fcc7.camel@intel.com \
    --to=xiaoyao.li@intel.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=sean.j.christopherson@intel.com \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    /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).