kvm,x86: load guest FPU context more eagerly (653f52c3) · Commits · 戴 / test

Currently KVM will clear the FPU bits in CR0.TS in the VMCS, and trap to re-load them every time the guest accesses the FPU after a switch back into the guest from the host. This patch copies the x86 task switch semantics for FPU loading, with the FPU loaded eagerly after first use if the system uses eager fpu mode, or if the guest uses the FPU frequently. In the latter case, after loading the FPU for 255 times, the fpu_counter will roll over, and we will revert to loading the FPU on demand, until it has been established that the guest is still actively using the FPU. This mirrors the x86 task switch policy, which seems to work. Signed-off-by:

Rik van Riel <riel@redhat.com> Signed-off-by:

Paolo Bonzini <pbonzini@redhat.com>

arch/x86/kvm/x86.c

+13 −2

Original line number	Diff line number	Diff line
		@@ -7086,14 +7086,25 @@ void kvm_put_guest_fpu(struct kvm_vcpu *vcpu)
		{
		kvm_put_guest_xcr0(vcpu);

		if (!vcpu->guest_fpu_loaded)
		if (!vcpu->guest_fpu_loaded) {
		vcpu->fpu_counter = 0;
		return;
		}

		vcpu->guest_fpu_loaded = 0;
		fpu_save_init(&vcpu->arch.guest_fpu);
		__kernel_fpu_end();
		++vcpu->stat.fpu_reload;
		/*
		* If using eager FPU mode, or if the guest is a frequent user
		* of the FPU, just leave the FPU active for next time.
		* Every 255 times fpu_counter rolls over to 0; a guest that uses
		* the FPU in bursts will revert to loading it on demand.
		*/
		if (!use_eager_fpu()) {
		if (++vcpu->fpu_counter < 5)
		kvm_make_request(KVM_REQ_DEACTIVATE_FPU, vcpu);
		}
		trace_kvm_fpu(0);
		}

include/linux/kvm_host.h

+1 −0

Original line number	Diff line number	Diff line
		@@ -230,6 +230,7 @@ struct kvm_vcpu {

		int fpu_active;
		int guest_fpu_loaded, guest_xcr0_loaded;
		unsigned char fpu_counter;
		wait_queue_head_t wq;
		struct pid *pid;
		int sigset_active;

Admin message