[Xen-changelog] [xen-unstable] Ensure CR0.TS is set for VMX domains regardless of the current

[Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User Steven Hand <steven@xxxxxxxxxxxxx>
# Date 1180972068 -3600
# Node ID 6f13c3be08fa4c044868144672783f7b1341999a
# Parent  c09dbe98e4d61d29138e8a2918d9ee8a85e1d6cf
Ensure CR0.TS is set for VMX domains regardless of the current
state of the real TS bit. This fixes a number of subtle FP
corruption issues within PV domains when running alongside VMX ones.

Signed-off-by: Steven Hand <steven@xxxxxxxxxxxxx>
---
 xen/arch/x86/hvm/vmx/vmcs.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -r c09dbe98e4d6 -r 6f13c3be08fa xen/arch/x86/hvm/vmx/vmcs.c
--- a/xen/arch/x86/hvm/vmx/vmcs.c       Mon Jun 04 15:41:32 2007 +0100
+++ b/xen/arch/x86/hvm/vmx/vmcs.c       Mon Jun 04 16:47:48 2007 +0100
@@ -337,7 +337,7 @@ static void construct_vmcs(struct vcpu *
 #endif
 
     /* Host control registers. */
-    __vmwrite(HOST_CR0, read_cr0());
+    __vmwrite(HOST_CR0, read_cr0() | X86_CR0_TS);
     __vmwrite(HOST_CR4, read_cr4());
 
     /* Host CS:RIP. */

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog