All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, Gleb Natapov <gleb@redhat.com>,
	Ulrich Obergfell <uobergfe@redhat.com>
Subject: Re: KVM: x86: fix maintenance of guest/host xcr0 state
Date: Tue, 16 Apr 2013 09:22:26 +0200	[thread overview]
Message-ID: <516CFC32.5040606@redhat.com> (raw)
In-Reply-To: <20130416023013.GA3943@amt.cnet>

Il 16/04/2013 04:30, Marcelo Tosatti ha scritto:
> 
> ** Untested **.
> 
> Emulation of xcr0 writes zero guest_xcr0_loaded variable so that
> subsequent VM-entry reloads CPU's xcr0 with guests xcr0 value.
> 
> However, this is incorrect because guest_xcr0_loaded variable is 
> read to decide whether to reload hosts xcr0.
> 
> In case the vcpu thread is scheduled out after the guest_xcr0_loaded = 0
> assignment, and scheduler decides to preload FPU:
> 
> switch_to
> {
>   __switch_to
>     __math_state_restore
>       restore_fpu_checking
>         fpu_restore_checking
>           if (use_xsave())
>               fpu_xrstor_checking
> 		xrstor64 with CPU's xcr0 == guests xcr0
> 
> Fix by properly restoring hosts xcr0 during emulation of xcr0 writes.
> 
> Analyzed-by: Ulrich Obergfell <uobergfe@redhat.com>
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> 
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 999d124..222926a 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -555,6 +555,25 @@ void kvm_lmsw(struct kvm_vcpu *vcpu, unsigned long msw)
>  }
>  EXPORT_SYMBOL_GPL(kvm_lmsw);
>  
> +static void kvm_load_guest_xcr0(struct kvm_vcpu *vcpu)
> +{
> +	if (kvm_read_cr4_bits(vcpu, X86_CR4_OSXSAVE) &&
> +			!vcpu->guest_xcr0_loaded) {
> +		/* kvm_set_xcr() also depends on this */
> +		xsetbv(XCR_XFEATURE_ENABLED_MASK, vcpu->arch.xcr0);
> +		vcpu->guest_xcr0_loaded = 1;
> +	}
> +}
> +
> +static void kvm_put_guest_xcr0(struct kvm_vcpu *vcpu)
> +{
> +	if (vcpu->guest_xcr0_loaded) {
> +		if (vcpu->arch.xcr0 != host_xcr0)
> +			xsetbv(XCR_XFEATURE_ENABLED_MASK, host_xcr0);
> +		vcpu->guest_xcr0_loaded = 0;
> +	}
> +}
> +
>  int __kvm_set_xcr(struct kvm_vcpu *vcpu, u32 index, u64 xcr)
>  {
>  	u64 xcr0;

This is just code movement...

> @@ -571,8 +590,8 @@ int __kvm_set_xcr(struct kvm_vcpu *vcpu, u32 index, u64 xcr)
>  		return 1;
>  	if (xcr0 & ~host_xcr0)
>  		return 1;
> +	kvm_put_guest_xcr0(vcpu);
>  	vcpu->arch.xcr0 = xcr0;
> -	vcpu->guest_xcr0_loaded = 0;
>  	return 0;
>  }
>  

... and this is the bulk of the fix: never set guest_xcr0_loaded, always
go through kvm_load/put_guest_xcr0.

Pending test,

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

Paolo

> @@ -5600,25 +5619,6 @@ static void inject_pending_event(struct kvm_vcpu *vcpu)
>  	}
>  }
>  
> -static void kvm_load_guest_xcr0(struct kvm_vcpu *vcpu)
> -{
> -	if (kvm_read_cr4_bits(vcpu, X86_CR4_OSXSAVE) &&
> -			!vcpu->guest_xcr0_loaded) {
> -		/* kvm_set_xcr() also depends on this */
> -		xsetbv(XCR_XFEATURE_ENABLED_MASK, vcpu->arch.xcr0);
> -		vcpu->guest_xcr0_loaded = 1;
> -	}
> -}
> -
> -static void kvm_put_guest_xcr0(struct kvm_vcpu *vcpu)
> -{
> -	if (vcpu->guest_xcr0_loaded) {
> -		if (vcpu->arch.xcr0 != host_xcr0)
> -			xsetbv(XCR_XFEATURE_ENABLED_MASK, host_xcr0);
> -		vcpu->guest_xcr0_loaded = 0;
> -	}
> -}
> -
>  static void process_nmi(struct kvm_vcpu *vcpu)
>  {
>  	unsigned limit = 2;
> 


  reply	other threads:[~2013-04-16  7:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  2:30 KVM: x86: fix maintenance of guest/host xcr0 state Marcelo Tosatti
2013-04-16  7:22 ` Paolo Bonzini [this message]
2013-04-17 13:16 ` Gleb Natapov
2013-05-08 10:16 ` Gleb Natapov

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=516CFC32.5040606@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=uobergfe@redhat.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 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.