Re: [PATCH] ftrace: Documentation
- From: "Abhishek Sagar" <sagar.abhishek@xxxxxxxxx>
- Date: Sat, 12 Jul 2008 18:19:03 +0530
On Thu, Jul 10, 2008 at 10:16 PM, Steven Rostedt <rostedt@xxxxxxxxxxx> 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?
--
Regards,
Abhishek
--
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/
- Follow-Ups:
- Re: [PATCH] ftrace: Documentation
- From: Steven Rostedt
- Re: [PATCH] ftrace: Documentation
- References:
- [PATCH] ftrace: Documentation
- From: Steven Rostedt
- [PATCH] ftrace: Documentation
- Prev by Date: [patch 0/4] firewire: keeping accesses to fw_transaction in check
- Next by Date: [patch 1/4] firewire: fix race of bus reset with request transmission
- Previous by thread: Re: [PATCH] ftrace: Documentation
- Next by thread: Re: [PATCH] ftrace: Documentation
- Index(es):
Relevant Pages
|
