switch_to(), flush_thread() write the task's PKRU value eagerly so the PKRU
value of current is always valid in the hardware.
That means there is no point in restoring PKRU on exit to user or when
reactivating the task's FPU registers in the signal frame setup path.
This allows to remove all the xstate buffer updates with PKRU values once
the PKRU state is stored in thread struct while a task is scheduled out.
Signed-off-by: Thomas Gleixner <[email protected]>
---
arch/x86/include/asm/fpu/internal.h | 12 +++++++++++-
arch/x86/include/asm/fpu/xstate.h | 19 +++++++++++++++++++
arch/x86/kernel/fpu/core.c | 2 +-
3 files changed, 31 insertions(+), 2 deletions(-)
--- a/arch/x86/include/asm/fpu/internal.h
+++ b/arch/x86/include/asm/fpu/internal.h
@@ -455,7 +455,17 @@ static inline void fpregs_restore_userre
return;
if (!fpregs_state_valid(fpu, cpu)) {
- restore_fpregs_from_fpstate(&fpu->state);
+ /*
+ * This restores _all_ xstate which has not been
+ * established yet.
+ *
+ * If PKRU is enabled, then the PKRU value is already
+ * correct because it was either set in switch_to() or in
+ * flush_thread(). So it is excluded because it might be
+ * not up to date in current->thread.fpu.xsave state.
+ */
+ __restore_fpregs_from_fpstate(&fpu->state,
+ xfeatures_mask_restore_user());
fpregs_activate(fpu);
fpu->last_cpu = cpu;
}
--- a/arch/x86/include/asm/fpu/xstate.h
+++ b/arch/x86/include/asm/fpu/xstate.h
@@ -35,6 +35,14 @@
XFEATURE_MASK_BNDREGS | \
XFEATURE_MASK_BNDCSR)
+/*
+ * Features which are restored when returning to user space.
+ * PKRU is not restored on return to user space because PKRU
+ * is switched eagerly in switch_to() and flush_thread()
+ */
+#define XFEATURE_MASK_USER_RESTORE \
+ (XFEATURE_MASK_USER_SUPPORTED & ~XFEATURE_MASK_PKRU)
+
/* All currently supported supervisor features */
#define XFEATURE_MASK_SUPERVISOR_SUPPORTED (XFEATURE_MASK_PASID)
@@ -92,6 +100,17 @@ static inline u64 xfeatures_mask_uabi(vo
return xfeatures_mask_all & XFEATURE_MASK_USER_SUPPORTED;
}
+/*
+ * The xfeatures which are restored by the kernel when returning to user
+ * mode. This is not necessarily the same as xfeatures_mask_uabi() as the
+ * kernel does not manage all XCR0 enabled features via xsave/xrstor as
+ * some of them have to be switched eagerly on context switch and exec().
+ */
+static inline u64 xfeatures_mask_restore_user(void)
+{
+ return xfeatures_mask_all & XFEATURE_MASK_USER_RESTORE;
+}
+
static inline u64 xfeatures_mask_independent(void)
{
if (!boot_cpu_has(X86_FEATURE_ARCH_LBR))
--- a/arch/x86/kernel/fpu/core.c
+++ b/arch/x86/kernel/fpu/core.c
@@ -470,7 +470,7 @@ void fpu__clear_user_states(struct fpu *
}
/* Reset user states in registers. */
- load_fpregs_from_init_fpstate(xfeatures_mask_uabi());
+ load_fpregs_from_init_fpstate(xfeatures_mask_restore_user());
/*
* Now all FPU registers have their desired values. Inform the FPU
On 6/14/2021 8:44 AM, Thomas Gleixner wrote:
> switch_to(), flush_thread() write the task's PKRU value eagerly so the PKRU
> value of current is always valid in the hardware.
>
> That means there is no point in restoring PKRU on exit to user or when
> reactivating the task's FPU registers in the signal frame setup path.
>
> This allows to remove all the xstate buffer updates with PKRU values once
> the PKRU state is stored in thread struct while a task is scheduled out.
>
> Signed-off-by: Thomas Gleixner <[email protected]>
> ---
> arch/x86/include/asm/fpu/internal.h | 12 +++++++++++-
> arch/x86/include/asm/fpu/xstate.h | 19 +++++++++++++++++++
> arch/x86/kernel/fpu/core.c | 2 +-
> 3 files changed, 31 insertions(+), 2 deletions(-)
>
> --- a/arch/x86/include/asm/fpu/internal.h
> +++ b/arch/x86/include/asm/fpu/internal.h
> @@ -455,7 +455,17 @@ static inline void fpregs_restore_userre
> return;
>
> if (!fpregs_state_valid(fpu, cpu)) {
> - restore_fpregs_from_fpstate(&fpu->state);
> + /*
> + * This restores _all_ xstate which has not been
> + * established yet.
> + *
> + * If PKRU is enabled, then the PKRU value is already
> + * correct because it was either set in switch_to() or in
> + * flush_thread(). So it is excluded because it might be
> + * not up to date in current->thread.fpu.xsave state.
> + */
> + __restore_fpregs_from_fpstate(&fpu->state,
> + xfeatures_mask_restore_user());
This needs to be xfeatures_mask_restore_user() |
xfeatures_mask_supervisor().
> fpregs_activate(fpu);
> fpu->last_cpu = cpu;
> }
[...]
On Tue, Jun 15 2021 at 17:52, Yu-cheng Yu wrote:
> On 6/14/2021 8:44 AM, Thomas Gleixner wrote:
>> + * If PKRU is enabled, then the PKRU value is already
>> + * correct because it was either set in switch_to() or in
>> + * flush_thread(). So it is excluded because it might be
>> + * not up to date in current->thread.fpu.xsave state.
>> + */
>> + __restore_fpregs_from_fpstate(&fpu->state,
>> + xfeatures_mask_restore_user());
>
> This needs to be xfeatures_mask_restore_user() |
> xfeatures_mask_supervisor().
Indeed. Good catch!
Thanks,
tglx