linux-toradex.git/arch/x86/kernel/stacktrace.c, branch v2.6.29.3

tracing/stack-tracer: fix style issues

2008-11-23T10:53:48+00:00

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:15+00:00

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

stacktrace: fix modular build, export print_stack_trace and save_stack_trace

2008-06-30T07:20:55+00:00

fix:

ERROR: "print_stack_trace" [kernel/backtracetest.ko] undefined!
ERROR: "save_stack_trace" [kernel/backtracetest.ko] undefined!

Signed-off-by: Ingo Molnar 

and fix:

  Building modules, stage 2.
  MODPOST 376 modules
ERROR: "print_stack_trace" [kernel/backtracetest.ko] undefined!
make[1]: *** [__modpost] Error 1

Signed-off-by: Ingo Molnar

x86: don't save unreliable stack trace entries

2008-02-26T11:55:58+00:00

Currently, there is no way for print_stack_trace() to determine whether
a given stack trace entry was deemed reliable or not, simply because
save_stack_trace() does not record this information. (Perhaps needless
to say, this makes the saved stack traces A LOT harder to read, and
probably with no other benefits, since debugging features that use
save_stack_trace() most likely also require frame pointers, etc.)

This patch reverts to the old behaviour of only recording the reliable trace
entries for saved stack traces.

Signed-off-by: Vegard Nossum 
Acked-by: Arjan van de Ven 
Signed-off-by: Ingo Molnar

x86: remove unneded casts

2008-01-30T12:33:23+00:00

x86: remove unneeded casts

Signed-off-by: Jan Engelhardt 
Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner

x86: pull bp calculation earlier into the backtrace path

2008-01-30T12:33:07+00:00

Right now, we take the stack pointer early during the backtrace path, but
only calculate bp several functions deep later, making it hard to reconcile
the stack and bp backtraces (as well as showing several internal backtrace
functions on the stack with bp based backtracing).

This patch moves the bp taking to the same place we take the stack pointer;
sadly this ripples through several layers of the back tracing stack,
but it's not all that bad in the end I hope.

Signed-off-by: Arjan van de Ven 
Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner

x86: add the capability to print fuzzy backtraces

2008-01-30T12:33:07+00:00

For enhancing the 32 bit EBP based backtracer, I need the capability
for the backtracer to tell it's customer that an entry is either
reliable or unreliable, and the backtrace printing code then needs to
print the unreliable ones slightly different.

This patch adds the basic capability, the next patch will add a user
of this capability.

Signed-off-by: Arjan van de Ven 
Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner

x86: nuke a ton of unused exports

2008-01-30T12:30:28+00:00

Signed-off-by: Thomas Gleixner 
Signed-off-by: Ingo Molnar

sched: latencytop support

2008-01-25T20:08:34+00:00

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

x86: constify stacktrace_ops

2007-10-17T18:16:11+00:00

.. as they're never written to.

[ tglx: arch/x86 adaptation ]

Signed-off-by: Jan Beulich 
Signed-off-by: Andi Kleen 
Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner