Displaying 3 results from an estimated 3 matches for "xstate_fp".
Did you mean:
xstate_bv
2013 Nov 19
6
[PATCH 2/5] X86 architecture instruction set extension definiation
...in_size += XSTATE_YMM_SIZE;
- BUG_ON(ecx < min_size);
-
/*
* Set CR4_OSXSAVE and run "cpuid" to get xsave_cntxt_size.
*/
@@ -327,14 +321,33 @@ unsigned int xstate_ctxt_size(u64 xcr0)
return ebx;
}
+static bool_t valid_xcr0(u64 xcr0)
+{
+ if ( !(xcr0 & XSTATE_FP) )
+ return 0;
+
+ if ( (xcr0 & XSTATE_YMM) && !(xcr0 & XSTATE_SSE) )
+ return 0;
+
+ if ( xcr0 & (XSTATE_OPMASK | XSTATE_ZMM | XSTATE_HI_ZMM) )
+ {
+ if ( !(xcr0 & XSTATE_YMM) )
+ return 0;
+
+ if ( ~xcr0 & (XSTATE_OPMASK...
2013 Nov 25
0
[PATCH 2/4 V2] X86: enable support for new ISA extensions
...< min_size);
-
/*
* Set CR4_OSXSAVE and run "cpuid" to get xsave_cntxt_size.
*/
@@ -327,14 +321,38 @@ unsigned int xstate_ctxt_size(u64 xcr0)
return ebx;
}
+static bool_t valid_xcr0(u64 xcr0)
+{
+ /* FP must be unconditionally set. */
+ if ( !(xcr0 & XSTATE_FP) )
+ return 0;
+
+ /* YMM depends on SSE. */
+ if ( (xcr0 & XSTATE_YMM) && !(xcr0 & XSTATE_SSE) )
+ return 0;
+
+ if ( xcr0 & (XSTATE_OPMASK | XSTATE_ZMM | XSTATE_HI_ZMM) )
+ {
+ /* OPMASK, ZMM, and HI_ZMM require YMM. */
+ if ( !(xcr0 &am...
2013 Jun 04
12
[PATCH 0/4] XSA-52..54 follow-up
The first patch really isn''t as much of a follow-up than what triggered
the security issues to be noticed in the first place.
1: x86: preserve FPU selectors for 32-bit guest code
2: x86: fix XCR0 handling
3: x86/xsave: adjust state management
4: x86/fxsave: bring in line with recent xsave adjustments
The first two I would see as candidates for 4.3 (as well as
subsequent backporting,