[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH] nestedsvm: fix lazy fpu switching causing a triple fault
Fix FPU switching uncovered with Hyper-V: Do FPU switching always on the n1 vmcb rather doing it on the current active vmcb. The FPU state between n1 and n2 vmcb is already synced in the vmrun and vmexit emulation. This fixes the situation where the n2 vmcb had the #NM intercept bit set but the virtual vmcb did not. That means it was believed the l1 guest can handle an #NM intercept but was actually wrong. The result were three #GP's with error code 0x11 in the l1 guest. Signed-off-by: Christoph Egger <Christoph.Egger@xxxxxxx> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85689 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632 Attachment:
xen_nh_fpu.diff _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |