diff options
| author | Steven Rostedt <rostedt@goodmis.org> | 2008-10-06 21:24:18 -0400 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-10-20 18:31:37 +0200 |
| commit | 81520a1b0649d0701205b818714a8c1e1cfbbb5b (patch) | |
| tree | a455ec060f28371b17374db2f934fc66dc7067ef /arch/x86 | |
| parent | 3ce83aea86bf46fd1bff59d2e6d16f48fdce22fc (diff) | |
| download | kernel_samsung_espresso10-81520a1b0649d0701205b818714a8c1e1cfbbb5b.zip kernel_samsung_espresso10-81520a1b0649d0701205b818714a8c1e1cfbbb5b.tar.gz kernel_samsung_espresso10-81520a1b0649d0701205b818714a8c1e1cfbbb5b.tar.bz2 | |
ftrace: stack tracer only record when on stack
The stack trace API does not record if the stack is not on the current
task's stack. That is, if the stack is the interrupt stack or NMI stack,
the output does not show. Also, the size of those stacks are not
consistent with the size of the thread stack, this makes the calculation
of the stack size usually bogus.
This all confuses the stack tracer. I unfortunately do not have time to
fix all these problems, but this patch does record the worst stack when
the stack pointer is on the tasks stack (instead of bogus numbers).
The patch simply returns if the stack pointer is not on the task's stack.
Signed-off-by: Steven Rostedt <srostedt@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/x86')
0 files changed, 0 insertions, 0 deletions