user/sven/linux.git/include/linux/stacktrace.h, branch v2.6.31.2

stacktrace: add forward-declaration struct task_struct

2009-06-12T21:04:12Z

This is needed if the header is to be free-standing. Signed-off-by: Vegard Nossum

x86: add save_stack_trace_bp() for tracing from a specific stack frame

2009-06-12T21:01:05Z

This will help kmemcheck (and possibly other debugging tools) since we can now simply pass regs->bp to the stack tracer instead of specifying the number of stack frames to skip, which is unreliable if gcc decides to inline functions, etc. Note that this makes the API incomplete for other architectures, but I expect that those can be updated lazily, e.g. when they need it. Cc: Arjan van de Ven Signed-off-by: Vegard Nossum

tracing/stack-tracer: introduce CONFIG_USER_STACKTRACE_SUPPORT

2008-11-23T10:53:50Z

Impact: cleanup User stack tracing is just implemented for x86, but it is not x86 specific. Introduce a generic config flag, that is currently enabled only for x86. When other arches implement it, they will have to SELECT USER_STACKTRACE_SUPPORT. Signed-off-by: Török Edwin Signed-off-by: Ingo Molnar

tracing/stack-tracer: fix style issues

2008-11-23T10:53:48Z

Impact: cleanup Signed-off-by: Török Edwin Signed-off-by: Ingo Molnar

tracing: add support for userspace stacktraces in tracing/iter_ctrl

2008-11-23T08:25:15Z

Impact: add new (default-off) tracing visualization feature Usage example: mount -t debugfs nodev /sys/kernel/debug cd /sys/kernel/debug/tracing echo userstacktrace >iter_ctrl echo sched_switch >current_tracer echo 1 >tracing_enabled .... run application ... echo 0 >tracing_enabled Then read one of 'trace','latency_trace','trace_pipe'. To get the best output you can compile your userspace programs with frame pointers (at least glibc + the app you are tracing). Signed-off-by: Török Edwin Signed-off-by: Ingo Molnar

include/linux/stacktrace.h: declare struct task_struct

2008-10-04T01:22:18Z

include/linux/stacktrace.h:13: warning: 'struct task_struct' declared inside parameter list (This might be a hard error on sparc64, which uses this header and has -Werror) Reported-by: "Randy.Dunlap" Acked-by: Ingo Molnar Cc: Peter Zijlstra Cc: Arjan van de Ven Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

sched: latencytop support

2008-01-25T20:08:34Z

LatencyTOP kernel infrastructure; it measures latencies in the scheduler and tracks it system wide and per process. Signed-off-by: Arjan van de Ven Signed-off-by: Ingo Molnar

stacktrace: fix header file for !CONFIG_STACKTRACE

2007-07-19T17:04:49Z

The print_stack_trace macro in stacktrace.h has a wrong number of arguments, fix it. Signed-off-by: Johannes Berg Cc: Ingo Molnar Cc: Peter Zijlstra Cc: Arjan van de Ven Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

simplify the stacktrace code

2007-05-08T18:14:58Z

Simplify the stacktrace code: - remove the unused task argument to save_stack_trace, it's always current - remove the all_contexts flag, it's alwasy 0 Signed-off-by: Christoph Hellwig Cc: Paul Mundt Cc: Ralf Baechle Cc: Martin Schwidefsky Cc: "David S. Miller" Cc: Andi Kleen Cc: Akinobu Mita Acked-by: Ingo Molnar Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] x86: Some preparationary cleanup for stack trace

2006-09-26T08:52:34Z

- Remove unused all_contexts parameter No caller used it - Move skip argument into the structure (needed for followon patches) Cc: mingo@elte.hu Signed-off-by: Andi Kleen