Steven Rostedt 5361499101 ftrace: add stack trace to function tracer
Impact: new feature to stack trace any function

Chris Mason asked about being able to pick and choose a function
and get a stack trace from it. This feature enables his request.

 # echo io_schedule > /debug/tracing/set_ftrace_filter
 # echo function > /debug/tracing/current_tracer
 # echo func_stack_trace > /debug/tracing/trace_options

Produces the following in /debug/tracing/trace:

       kjournald-702   [001]   135.673060: io_schedule <-sync_buffer
       kjournald-702   [002]   135.673671:
 <= sync_buffer
 <= __wait_on_bit
 <= out_of_line_wait_on_bit
 <= __wait_on_buffer
 <= sync_dirty_buffer
 <= journal_commit_transaction
 <= kjournald

Note, be careful about turning this on without filtering the functions.
You may find that you have a 10 second lag between typing and seeing
what you typed. This is why the stack trace for the function tracer
does not use the same stack_trace flag as the other tracers use.

Signed-off-by: Steven Rostedt <srostedt@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-01-16 12:15:32 +01:00
..
2009-01-09 03:39:43 -05:00
2009-01-08 08:31:10 -08:00
2008-10-16 11:21:30 -07:00
2008-09-14 16:25:35 +02:00
2008-07-28 14:37:38 +02:00
2009-01-06 15:59:27 -08:00
2008-12-10 08:01:54 -08:00
2008-08-13 12:55:10 +02:00
2008-10-20 15:43:10 +02:00
2009-01-08 08:31:02 -08:00
2009-01-08 08:31:12 -08:00
2008-09-02 19:21:40 -07:00
2009-01-05 13:09:49 +01:00
2009-01-06 11:07:15 +01:00
2008-11-05 10:30:14 +01:00
2009-01-07 16:10:54 +01:00
2008-11-19 18:49:57 -08:00
2008-12-31 15:11:46 +01:00
2008-10-16 11:21:47 -07:00
2008-10-16 11:21:31 -07:00