summaryrefslogtreecommitdiffstats
path: root/arch/xtensa/mm
diff options
context:
space:
mode:
authorJohannes Weiner <jw@emlix.com>2009-03-04 16:21:29 +0100
committerChris Zankel <chris@zankel.net>2009-04-02 23:38:57 -0700
commit28a0ce7f642f503dde866f763e8144a517fdf74a (patch)
treee898e20dd046957a1598da24802c1d8630f21146 /arch/xtensa/mm
parent35f9cd083b350ad4eb3b5f159c7738fa9ddff40a (diff)
downloadop-kernel-dev-28a0ce7f642f503dde866f763e8144a517fdf74a.zip
op-kernel-dev-28a0ce7f642f503dde866f763e8144a517fdf74a.tar.gz
xtensa: use correct stack pointer for stack traces
Right now, the xtensa stacktrace code reads the _current_ kernel stack pointer if nothing is supplied. With debugging facilities like sysrq this means that the backtrace of the sysrq-handler is printed instead of a trace of the given task's stack. When no stack pointer is specified in show_trace() and show_stack(), use the stack pointer that comes with the handed in task descriptor to make stack traces more useful. Signed-off-by: Johannes Weiner <jw@emlix.com> Signed-off-by: Chris Zankel <chris@zankel.net>
Diffstat (limited to 'arch/xtensa/mm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud