summaryrefslogtreecommitdiffstats
path: root/include/linux/ftrace.h
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2019-04-21 19:40:44 -0400
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2019-04-21 19:46:56 -0400
commit52fde6e70cccc2fcf3f39fed0d0392960e2c2b03 (patch)
treef4018df08575ea04b9a2aa917e1518655745a35e /include/linux/ftrace.h
parent2fa717a0337e7acafda9283c938b635191b8036b (diff)
downloadtalos-op-linux-52fde6e70cccc2fcf3f39fed0d0392960e2c2b03.tar.gz
talos-op-linux-52fde6e70cccc2fcf3f39fed0d0392960e2c2b03.zip
function_graph: Have selftest also emulate tr->reset() as it did with tr->init()
The function_graph boot up self test emulates the tr->init() function in order to add a wrapper around the function graph tracer entry code to test for lock ups and such. But it does not emulate the tr->reset(), and just calls the function_graph tracer tr->reset() function which will use its own fgraph_ops to unregister function tracing with. As the fgraph_ops is becoming more meaningful with the register_ftrace_graph() and unregister_ftrace_graph() functions, the two need to be the same. The emulated tr->init() uses its own fgraph_ops descriptor, which means the unregister_ftrace_graph() must use the same ftrace_ops, which the selftest currently does not do. By emulating the tr->reset() as the selftest does with the tr->init() it will be able to pass the same fgraph_ops descriptor to the unregister_ftrace_graph() as it did with the register_ftrace_graph(). Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'include/linux/ftrace.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud