diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2021-06-23 14:02:06 +0200 |
---|---|---|
committer | Borislav Petkov <bp@suse.de> | 2021-06-23 18:55:56 +0200 |
commit | b2681e791dbcee6acb1dca7a5076a0285109ac4c (patch) | |
tree | e6088e639d8357c09620ef2d0ddca4cb1dfc1a64 /arch/x86/kernel/fpu/xstate.c | |
parent | 784a46618f634973a17535b7d3d03cd4ebc0ccbd (diff) | |
download | lwn-b2681e791dbcee6acb1dca7a5076a0285109ac4c.tar.gz lwn-b2681e791dbcee6acb1dca7a5076a0285109ac4c.zip |
x86/fpu: Rename and sanitize fpu__save/copy()
Both function names are a misnomer.
fpu__save() is actually about synchronizing the hardware register state
into the task's memory state so that either coredump or a math exception
handler can inspect the state at the time where the problem happens.
The function guarantees to preserve the register state, while "save" is a
common terminology for saving the current state so it can be modified and
restored later. This is clearly not the case here.
Rename it to fpu_sync_fpstate().
fpu__copy() is used to clone the current task's FPU state when duplicating
task_struct. While the register state is a copy the rest of the FPU state
is not.
Name it accordingly and remove the really pointless @src argument along
with the warning which comes along with it.
Nothing can ever copy the FPU state of a non-current task. It's clearly
just a consequence of arch_dup_task_struct(), but it makes no sense to
proliferate that further.
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/20210623121455.196727450@linutronix.de
Diffstat (limited to 'arch/x86/kernel/fpu/xstate.c')
0 files changed, 0 insertions, 0 deletions