aboutsummaryrefslogtreecommitdiffstats
path: root/arch/powerpc/configs/mpc834x_mds_defconfig
diff options
context:
space:
mode:
authorKumar Gala <galak@kernel.crashing.org>2007-08-28 21:15:53 -0500
committerKumar Gala <galak@kernel.crashing.org>2007-08-28 21:15:53 -0500
commit0ee6c15e7ba7b36a217cdadb292eeaf32a057a59 (patch)
tree7ce7ee5413086758ebdea9a00f4d5b7d7a8f45ba /arch/powerpc/configs/mpc834x_mds_defconfig
parentLinux 2.6.23-rc4 (diff)
downloadlinux-dev-0ee6c15e7ba7b36a217cdadb292eeaf32a057a59.tar.xz
linux-dev-0ee6c15e7ba7b36a217cdadb292eeaf32a057a59.zip
[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>
Diffstat (limited to 'arch/powerpc/configs/mpc834x_mds_defconfig')
0 files changed, 0 insertions, 0 deletions