[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-changelog] [xen stable-4.2] x86: consistently mask floating point exceptions



commit 483eb53f833e61d3462c19b36de35ad57e425f96
Author:     Jan Beulich <jbeulich@xxxxxxxx>
AuthorDate: Tue Feb 12 13:37:15 2013 +0100
Commit:     Jan Beulich <jbeulich@xxxxxxxx>
CommitDate: Tue Feb 12 13:37:15 2013 +0100

    x86: consistently mask floating point exceptions
    
    c/s 23142:f5e8d152a565 resulted in v->arch.fpu_ctxt to point into the
    save area allocated for xsave/xrstor (when they're available). The way
    vcpu_restore_fpu_lazy() works (using fpu_init() for an uninitialized
    vCPU only when there's no xsave support) causes this to load whatever
    arch_set_info_guest() put there, irrespective of whether the i387 state
    was specified to be valid in the respective input structure.
    
    Consequently, with a cleared (al zeroes) incoming FPU context, and with
    xsave available, one gets all exceptions unmasked (as opposed to to the
    legacy case, where FINIT and LDMXCSR get used, masking all exceptions).
    This causes e.g. para-virtualized NetWare to crash.
    
    The behavior of arch_set_info_guest() is thus being made more hardware-
    like for the FPU portion of it: Considering it to be similar to INIT,
    it will leave untouched all floating point state now. An alternative
    would be to make the behavior RESET-like, forcing all state to known
    values, albeit - taking into account legacy behavior - not to precisely
    the values RESET would enforce (which masks only SSE exceptions, but
    not x87 ones); that would come closest to mimicing FINIT behavior in
    the xsave case. Another option would be to continue copying whatever
    was provided, but override (at least) FCW and MXCSR if VGCF_I387_VALID
    isn't set.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    xen-unstable changeset: 26395:b4cbb83f9a1f
    xen-unstable date: Wed Jan 16 12:56:55 UTC 2013
---
 xen/arch/x86/domain.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/xen/arch/x86/domain.c b/xen/arch/x86/domain.c
index 655d95b..26a7f12 100644
--- a/xen/arch/x86/domain.c
+++ b/xen/arch/x86/domain.c
@@ -819,7 +819,9 @@ int arch_set_info_guest(
 
     v->arch.vgc_flags = flags;
 
-    memcpy(v->arch.fpu_ctxt, &c.nat->fpu_ctxt, sizeof(c.nat->fpu_ctxt));
+    if ( flags & VGCF_I387_VALID )
+        memcpy(v->arch.fpu_ctxt, &c.nat->fpu_ctxt, sizeof(c.nat->fpu_ctxt));
+
     if ( !compat )
     {
         memcpy(&v->arch.user_regs, &c.nat->user_regs, 
sizeof(c.nat->user_regs));
--
generated by git-patchbot for /home/xen/git/xen.git#stable-4.2

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.