diff options
author | 2014-07-15 11:05:12 -0400 | |
---|---|---|
committer | 2014-07-15 11:10:25 -0400 | |
commit | 5f8bf2d263a20b986225ae1ed7d6759dc4b93af9 (patch) | |
tree | d5ece8db33d03be215cf845155751b3f2fc0c155 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | tracing: Add ftrace_trace_stack into __trace_puts/__trace_bputs (diff) | |
download | linux-dev-5f8bf2d263a20b986225ae1ed7d6759dc4b93af9.tar.xz linux-dev-5f8bf2d263a20b986225ae1ed7d6759dc4b93af9.zip |
tracing: Fix graph tracer with stack tracer on other archs
Running my ftrace tests on PowerPC, it failed the test that checks
if function_graph tracer is affected by the stack tracer. It was.
Looking into this, I found that the update_function_graph_func()
must be called even if the trampoline function is not changed.
This is because archs like PowerPC do not support ftrace_ops being
passed by assembly and instead uses a helper function (what the
trampoline function points to). Since this function is not changed
even when multiple ftrace_ops are added to the code, the test that
falls out before calling update_function_graph_func() will miss that
the update must still be done.
Call update_function_graph_function() for all calls to
update_ftrace_function()
Cc: stable@vger.kernel.org # 3.3+
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions