summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorRik van Riel <riel@redhat.com>2015-04-23 11:52:37 -0400
committerPaolo Bonzini <pbonzini@redhat.com>2015-05-07 11:29:45 +0200
commit653f52c316a49c5ee2701bc13b15879f20790662 (patch)
tree2e939ee44f04a4bd39f009f0a91c9a536b116b71 /include
parentd1ebdbf99a3ce90f3b886c2cf0dfd7da17703d2a (diff)
downloadlinux-653f52c316a49c5ee2701bc13b15879f20790662.tar.gz
linux-653f52c316a49c5ee2701bc13b15879f20790662.tar.bz2
linux-653f52c316a49c5ee2701bc13b15879f20790662.zip
kvm,x86: load guest FPU context more eagerly
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>
Diffstat (limited to 'include')
-rw-r--r--include/linux/kvm_host.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index efc16df1fc5d..b7a08cd6f4a8 100644
--- a/include/linux/kvm_host.h
+++ b/include/linux/kvm_host.h
@@ -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;