Messages in this thread | | | Date | Tue, 15 Jul 2008 10:39:13 -0400 (EDT) | From | Steven Rostedt <> | Subject | Re: [PATCH] ftrace: Documentation |
| |
On Sat, 12 Jul 2008, Abhishek Sagar wrote:
> > On Thu, Jul 10, 2008 at 10:16 PM, Steven Rostedt <rostedt@goodmis.org> wrote: > > > > This is the long awaited ftrace.txt. It explains in quite detail how to > > use ftrace and the various tracers. > > This is quite good. Thanks! > > > +Output format: > > +-------------- > > + > > +Here's an example of the output format of the file "trace" > > + > > + -------- > > +# tracer: ftrace > > +# > > +# TASK-PID CPU# TIMESTAMP FUNCTION > > +# | | | | | > > + bash-4251 [01] 10152.583854: path_put <-path_walk > > + bash-4251 [01] 10152.583855: dput <-path_put > > + bash-4251 [01] 10152.583855: _atomic_dec_and_lock <-dput > > + -------- > > A small caveat here...the function names may be substituted with a > "[unkown/kretprobe'd]" under special circumstances > (http://lkml.org/lkml/2008/5/27/275). May be that should be mentioned > here?
Hmm, I thinking that this might be too much information for this document. If you can think of a good way to expline this without "overloading" the reader, then please, let me know.
Thanks,
-- Steve
| |