Re: [patch 3/3] x86/fpu/xsave: Optimize XSAVEC/S when XGETBV1 is supported

From: Dave Hansen
Date: Thu Apr 14 2022 - 13:24:47 EST


On 4/4/22 05:11, Thomas Gleixner wrote:
> A typical scenario is an active set of 0x202 (PKRU + SSE) out of the full
> supported set of 0x2FF. That means XSAVEC/S writes and XRSTOR[S] reads:

It might be worth reminding folks why PKRU is a special snowflake:

The default PKRU enforced by the kernel is its most restrictive possible
value (0xfffffffc). This means that PKRU defaults to being in its
non-init state even for tasks which do nothing protection-keys-related.


> which is suboptimal. Prefetch works better when the access is linear. But
> what's worse is that PKRU can be located in a different page which
> obviously affects dTLB.

The numbers don't lie, but I'm still surprised by this. Was this in a
VM that isn't backed with large pages? task_struct.thread.fpu is
kmem_cache_alloc()'d and is in the direct map, which should be 2M/1G
pages almost all the time.

> --- a/arch/x86/kernel/fpu/xstate.c
> +++ b/arch/x86/kernel/fpu/xstate.c
> @@ -86,6 +86,8 @@ static unsigned int xstate_flags[XFEATUR
> #define XSTATE_FLAG_SUPERVISOR BIT(0)
> #define XSTATE_FLAG_ALIGNED64 BIT(1)
>
> +DEFINE_STATIC_KEY_FALSE(__xsave_use_xgetbv1);
> +
> /*
> * Return whether the system supports a given xfeature.
> *
> @@ -1481,7 +1483,7 @@ void xfd_validate_state(struct fpstate *
> }
> #endif /* CONFIG_X86_DEBUG_FPU */
>
> -static int __init xfd_update_static_branch(void)
> +static int __init fpu_update_static_branches(void)
> {
> /*
> * If init_fpstate.xfd has bits set then dynamic features are
> @@ -1489,9 +1491,13 @@ static int __init xfd_update_static_bran
> */
> if (init_fpstate.xfd)
> static_branch_enable(&__fpu_state_size_dynamic);
> +
> + if (cpu_feature_enabled(X86_FEATURE_XGETBV1) &&
> + cpu_feature_enabled(X86_FEATURE_XCOMPACTED))
> + static_branch_enable(&__xsave_use_xgetbv1);
> return 0;
> }
> -arch_initcall(xfd_update_static_branch)
> +arch_initcall(fpu_update_static_branches)
>
> void fpstate_free(struct fpu *fpu)
> {
> --- a/arch/x86/kernel/fpu/xstate.h
> +++ b/arch/x86/kernel/fpu/xstate.h
> @@ -10,7 +10,12 @@
> DECLARE_PER_CPU(u64, xfd_state);
> #endif
>
> -static inline bool xsave_use_xgetbv1(void) { return false; }
> +DECLARE_STATIC_KEY_FALSE(__xsave_use_xgetbv1);
> +
> +static __always_inline __pure bool xsave_use_xgetbv1(void)
> +{
> + return static_branch_likely(&__xsave_use_xgetbv1);
> +}
>
> static inline void __xstate_init_xcomp_bv(struct xregs_state *xsave, u64 mask)
> {
> @@ -185,13 +190,18 @@ static inline int __xfd_enable_feature(u
> static inline void os_xsave(struct fpstate *fpstate)
> {
> u64 mask = fpstate->xfeatures;
> - u32 lmask = mask;
> - u32 hmask = mask >> 32;
> + u32 lmask, hmask;
> int err;
>
> WARN_ON_FPU(!alternatives_patched);
> xfd_validate_state(fpstate, mask, false);
>
> + if (xsave_use_xgetbv1())
> + mask &= xgetbv(1);

How about this comment for the masking operation:

/*
* Remove features in their init state from the mask. This
* makes the XSAVE{S,C} writes less sparse and quicker for
* the CPU.
*/

> + lmask = mask;
> + hmask = mask >> 32;
> +
> XSTATE_XSAVE(&fpstate->regs.xsave, lmask, hmask, err);
>
> /* We should never fault when copying to a kernel buffer: */