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
File | Mode | Size |
---|---|---|
Kconfig | -rw-r--r-- | 4.1 KB |
Makefile | -rw-r--r-- | 253 bytes |
cache.c | -rw-r--r-- | 8.5 KB |
dir.c | -rw-r--r-- | 34.1 KB |
fat.h | -rw-r--r-- | 12.3 KB |
fatent.c | -rw-r--r-- | 16.6 KB |
file.c | -rw-r--r-- | 10.9 KB |
inode.c | -rw-r--r-- | 41.1 KB |
misc.c | -rw-r--r-- | 7.5 KB |
namei_msdos.c | -rw-r--r-- | 16.5 KB |
namei_vfat.c | -rw-r--r-- | 25.4 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...