Re: [PATCH 2/2] ftrace: add stack trace to function tracer

[Steven Rostedt]

On Thu, 15 Jan 2009, Steven Rostedt wrote:
> 
> 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, the above is from two different CPUS. This is because I did not want 
to messy up the current function trace with more branches. I took the easy 
way out. I simply registered another tracer to the function tracer to dump 
out the trace.

I have an idea how to fix it. I'll work on a solution now.

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/