diff options
| author |   Vincent Palatin <vpalatin@chromium.org> | 2012-11-30 12:15:32 -0800 |
|---|---|---|
| committer |   H. Peter Anvin <hpa@linux.intel.com> | 2012-11-30 13:48:05 -0800 |
| commit | 644c154186386bb1fa6446bc5e037b9ed098db46 (patch) | |
| tree | cffc45d54cd63fa1f255406e0759e7a1d8cc58ac /Makefile | |
| parent | x86-32: Unbreak booting on some 486 clones (diff) | |
| download | linux-dev-644c154186386bb1fa6446bc5e037b9ed098db46.tar.xz linux-dev-644c154186386bb1fa6446bc5e037b9ed098db46.zip | |
x86, fpu: Avoid FPU lazy restore after suspend
When a cpu enters S3 state, the FPU state is lost.
After resuming for S3, if we try to lazy restore the FPU for a process running
on the same CPU, this will result in a corrupted FPU context.
Ensure that "fpu_owner_task" is properly invalided when (re-)initializing a CPU,
so nobody will try to lazy restore a state which doesn't exist in the hardware.
Tested with a 64-bit kernel on a 4-core Ivybridge CPU with eagerfpu=off,
by doing thousands of suspend/resume cycles with 4 processes doing FPU
operations running. Without the patch, a process is killed after a
few hundreds cycles by a SIGFPE.
Cc: Duncan Laurie <dlaurie@chromium.org>
Cc: Olof Johansson <olofj@chromium.org>
Cc: <stable@kernel.org> v3.4+ # for 3.4 need to replace this_cpu_write by percpu_write
Signed-off-by: Vincent Palatin <vpalatin@chromium.org>
Link: http://lkml.kernel.org/r/1354306532-1014-1-git-send-email-vpalatin@chromium.org
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions