Searched hist:"2 ebe81c6d800576e1213f9d7cf0068017ae610c1" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/arch/x86/include/asm/fpu/ |
| H A D | xstate.h | diff 2ebe81c6d800576e1213f9d7cf0068017ae610c1 Wed Jun 23 07:02:17 CDT 2021 Thomas Gleixner <tglx@linutronix.de> x86/fpu: Dont restore PKRU in fpregs_restore_userspace()
switch_to() and 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 <tglx@linutronix.de>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Borislav Petkov <bp@suse.de>
Link: https://lkml.kernel.org/r/20210623121456.303919033@linutronix.de
|
| /openbmc/linux/arch/x86/kernel/fpu/ |
| H A D | core.c | diff 2ebe81c6d800576e1213f9d7cf0068017ae610c1 Wed Jun 23 07:02:17 CDT 2021 Thomas Gleixner <tglx@linutronix.de> x86/fpu: Dont restore PKRU in fpregs_restore_userspace()
switch_to() and 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 <tglx@linutronix.de>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Borislav Petkov <bp@suse.de>
Link: https://lkml.kernel.org/r/20210623121456.303919033@linutronix.de
|