Home
last modified time | relevance | path

Searched hist:b0dc553cfc9d3bc2c7b8672b0b2fcf0edf0c3b6e (Results 1 – 2 of 2) sorted by relevance

/openbmc/linux/arch/x86/include/asm/
H A Defi.hdiff b0dc553cfc9d3bc2c7b8672b0b2fcf0edf0c3b6e Wed Jan 20 23:09:50 CST 2021 Andy Lutomirski <luto@kernel.org> x86/fpu: Make the EFI FPU calling convention explicit

EFI uses kernel_fpu_begin() to conform to the UEFI calling convention.
This specifically requires initializing FCW (FPU Control Word), whereas
no sane 64-bit kernel code should use legacy 387 operations that
reference FCW.

This should allow to safely change the default semantics of
kernel_fpu_begin() to stop initializing FCW on 64-bit kernels.

[ bp: Massage commit message a little. ]

Signed-off-by: Andy Lutomirski <luto@kernel.org>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lkml.kernel.org/r/25d392fff64680e0f4bb8cf0b1003314dc29eafe.1611205691.git.luto@kernel.org
/openbmc/linux/arch/x86/platform/efi/
H A Defi_64.cdiff b0dc553cfc9d3bc2c7b8672b0b2fcf0edf0c3b6e Wed Jan 20 23:09:50 CST 2021 Andy Lutomirski <luto@kernel.org> x86/fpu: Make the EFI FPU calling convention explicit

EFI uses kernel_fpu_begin() to conform to the UEFI calling convention.
This specifically requires initializing FCW (FPU Control Word), whereas
no sane 64-bit kernel code should use legacy 387 operations that
reference FCW.

This should allow to safely change the default semantics of
kernel_fpu_begin() to stop initializing FCW on 64-bit kernels.

[ bp: Massage commit message a little. ]

Signed-off-by: Andy Lutomirski <luto@kernel.org>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lkml.kernel.org/r/25d392fff64680e0f4bb8cf0b1003314dc29eafe.1611205691.git.luto@kernel.org