• Kan Liang's avatar
    x86/fpu/xstate: Fix an xstate size check warning with architectural LBRs · 76d10256
    Kan Liang authored
    An xstate size check warning is triggered on machines which support
    Architectural LBRs.
    
        XSAVE consistency problem, dumping leaves
        WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:649 fpu__init_system_xstate+0x4d4/0xd0e
        Modules linked in:
        CPU: 0 PID: 0 Comm: swapper Not tainted intel-arch_lbr+
        RIP: 0010:fpu__init_system_xstate+0x4d4/0xd0e
    
    The xstate size check routine, init_xstate_size(), compares the size
    retrieved from the hardware with the size of task->fpu, which is
    calculated by the software.
    
    The size from the hardware is the total size of the enabled xstates in
    XCR0 | IA32_XSS. Architectural LBR state is a dynamic supervisor
    feature, which sets the corresponding bit in the IA32_XSS at boot time.
    The size from the hardware includes the size of the Architectural LBR
    state.
    
    However, a dynamic supervisor feature doesn't allocate a buffer in the
    task->fpu. The size of task->fpu doesn't include the size of the
    Architectural LBR state. The mismatch will trigger the warning.
    
    Three options as below were considered to fix the issue:
    
    - Correct the size from the hardware by subtracting the size of the
      dynamic supervisor features.
      The purpose of the check is to compare the size CPU told with the size
      of the XSAVE buffer, which is calculated by the software. If the
      software mucks with the number from hardware, it removes the value of
      the check.
      This option is not a good option.
    
    - Prevent the hardware from counting the size of the dynamic supervisor
      feature by temporarily removing the corresponding bits in IA32_XSS.
      Two extra MSR writes are required to flip the IA32_XSS. The option is
      not pretty, but it is workable. The check is only called once at early
      boot time. The synchronization or context-switching doesn't need to be
      worried.
      This option is implemented here.
    
    - Remove the check entirely, because the check hasn't found any real
      problems. The option may be an alternative as option 2.
      This option is not implemented here.
    
    Add a new function, get_xsaves_size_no_dynamic(), which retrieves the
    total size without the dynamic supervisor features from the hardware.
    The size will be used to compare with the size of task->fpu.
    
    Fixes: f0dccc9d ("x86/fpu/xstate: Support dynamic supervisor feature for LBR")
    Reported-by: default avatarChang S. Bae <chang.seok.bae@intel.com>
    Signed-off-by: default avatarKan Liang <kan.liang@linux.intel.com>
    Signed-off-by: default avatarIngo Molnar <mingo@kernel.org>
    Reviewed-by: default avatarDave Hansen <dave.hansen@intel.com>
    Link: https://lore.kernel.org/r/1595253051-75374-1-git-send-email-kan.liang@linux.intel.com
    76d10256
xstate.c 39.8 KB