x86/xsaves: Keep init_fpstate.xsave.header.xfeatures as zero for init optimization
PATCH 3/10 x86/xsaves: Keep init_fpstate.xsave.header.xfeatures as zero for init optimization
Keep init_fpstate.xsave.header.xfeatures as zero for init optimization. This is important for init optimization that is implemented in processor. If a bit corresponding to an xstate in xstate_bv is 0, it means the xstate is in init status and will not be read from memory to the processor during XRSTOR/XRSTORS instruction. This largely impacts context switch performance.
Signed-off-by Fenghua Yu <[email protected]>
Signed-off-by Yu-cheng Yu <[email protected]>
Reviewed-by Dave Hansen <[email protected]>
--- arch/x86/kernel/fpu/xstate.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
arch/x86/kernel/fpu/xstate.c +1 -3
@@ -311,10 +311,8 @@ static void __init setup_init_fpu_buf(void)setup_xstate_features ();print_xstate_features (); -if (cpu_has_xsaves) { +if (cpu_has_xsaves) init_fpstate.xsave.header.xcomp_bv = (u64 )1 <<63 | xfeatures_mask; - init_fpstate.xsave.header.xfeatures = xfeatures_mask; - }/* * Init all the features state with header_bv being 0x0
Signature · 1 line
1.9.1