Revision 5f630401f9e98bd062733b5bbef096dbf2158066 authored by Tiejun Chen on 22 August 2012, 16:10:20 UTC, committed by Benjamin Herrenschmidt on 24 August 2012, 10:26:06 UTC
For powerpc BooKE and e200, singlestep is handled on the critical/dbg
exception stack. This causes current_thread_info() to fail for kgdb
internal, so previously We work around this issue by copying
the thread_info from the kernel stack before calling kgdb_handle_exception,
and copying it back afterwards.

But actually we don't do this properly. We should backup current_thread_info
then restore that when exit.

Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
1 parent 949616c
History
File Mode Size
BUGS -rw-r--r-- 235 bytes
Kbuild -rw-r--r-- 533 bytes
Kconfig -rw-r--r-- 323 bytes
Kconfig.ore -rw-r--r-- 461 bytes
common.h -rw-r--r-- 8.6 KB
dir.c -rw-r--r-- 16.8 KB
exofs.h -rw-r--r-- 8.0 KB
file.c -rw-r--r-- 2.5 KB
inode.c -rw-r--r-- 36.4 KB
namei.c -rw-r--r-- 7.2 KB
ore.c -rw-r--r-- 28.9 KB
ore_raid.c -rw-r--r-- 19.1 KB
ore_raid.h -rw-r--r-- 2.7 KB
super.c -rw-r--r-- 26.5 KB
symlink.c -rw-r--r-- 1.8 KB
sys.c -rw-r--r-- 5.2 KB

back to top