diff options
author | Lai Jiangshan <laijs@cn.fujitsu.com> | 2010-01-13 19:38:30 +0800 |
---|---|---|
committer | Frederic Weisbecker <fweisbec@gmail.com> | 2010-01-29 01:05:12 +0100 |
commit | ea2c68a08fedb5053ba312d661e47df9f4d72411 (patch) | |
tree | 76e5e61b8377aac6283670481171bf899905052b /firmware | |
parent | 24a53652e361321b09df5040711e69387344ce09 (diff) | |
download | talos-op-linux-ea2c68a08fedb5053ba312d661e47df9f4d72411.tar.gz talos-op-linux-ea2c68a08fedb5053ba312d661e47df9f4d72411.zip |
tracing: Simplify test for function_graph tracing start point
In the function graph tracer, a calling function is to be traced
only when it is enabled through the set_graph_function file,
or when it is nested in an enabled function.
Current code uses TSK_TRACE_FL_GRAPH to test whether it is nested
or not. Looking at the code, we can get this:
(trace->depth > 0) <==> (TSK_TRACE_FL_GRAPH is set)
trace->depth is more explicit to tell that it is nested.
So we use trace->depth directly and simplify the code.
No functionality is changed.
TSK_TRACE_FL_GRAPH is not removed yet, it is left for future usage.
Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>
LKML-Reference: <4B4DB0B6.7040607@cn.fujitsu.com>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions