| commit | cc6b1c0e31e1f639d3c5e161039c24edb41c4537 | |
| author | Kumar Gala <galak@kernel.crashing.org> | |
| Sat, 6 Oct 2007 21:36:26 +0000 (6 23:36 +0200) | ||
| committer | Adrian Bunk <bunk@kernel.org> | |
| Sat, 6 Oct 2007 21:36:26 +0000 (6 23:36 +0200) | ||
| tree | b2bc173f09d43759d20b4574f065dbc099a4c5f9 | treesnapshot (tar.gz zip) |
| parent | bffb5afd17f7f791f627ef65425f3c4cb9e43095 | commitdiff |
[POWERPC] Flush registers to proper task context
When we flush register state for FP, Altivec, or SPE in flush_*_to_thread
we need to respect the task_struct that the caller has passed to us.
Most cases we are called with current, however sometimes (ptrace) we may
be passed a different task_struct.
This showed up when using gdbserver debugging a simple program that used
floating point. When gdb tried to show the FP regs they all showed up as 0,
because the child's FP registers were never properly flushed to memory.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Adrian Bunk <bunk@kernel.org>
When we flush register state for FP, Altivec, or SPE in flush_*_to_thread
we need to respect the task_struct that the caller has passed to us.
Most cases we are called with current, however sometimes (ptrace) we may
be passed a different task_struct.
This showed up when using gdbserver debugging a simple program that used
floating point. When gdb tried to show the FP regs they all showed up as 0,
because the child's FP registers were never properly flushed to memory.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Adrian Bunk <bunk@kernel.org>
| arch/powerpc/kernel/process.c | diffblobblamehistory |