| commit | fee40b38d938f8fc5dae006ed25259456c2cd7bc | |
| author | Kumar Gala <galak@kernel.crashing.org> | |
| Wed, 29 Aug 2007 02:15:53 +0000 (28 21:15 -0500) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Wed, 26 Sep 2007 17:54:38 +0000 (26 10:54 -0700) | ||
| tree | 2d26cc5e3a446d84ac76fdefa0bdc6862f427d83 | treesnapshot (tar.gz zip) |
| parent | 51718d505589b59a4bb4dc2a6de5ae2402972a17 | commitdiff |
POWERPC: Flush registers to proper task context
commit 0ee6c15e7ba7b36a217cdadb292eeaf32a057a59 in mainline.
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: Greg Kroah-Hartman <gregkh@suse.de>
commit 0ee6c15e7ba7b36a217cdadb292eeaf32a057a59 in mainline.
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: Greg Kroah-Hartman <gregkh@suse.de>
| arch/powerpc/kernel/process.c | diffblobblamehistory |