summaryrefslogtreecommitdiff
path: root/kernel/trace/trace_events.c
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2017-04-18 21:50:39 +0300
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2017-04-21 05:06:46 +0300
commit7b60f3d8761561d95d7e962522d6338143fc2329 (patch)
treec129464e646cabd898b8c2ddde08f52f1afd6053 /kernel/trace/trace_events.c
parentb5f081b563a6cdcb85a543df8c851951a8978275 (diff)
downloadlinux-7b60f3d8761561d95d7e962522d6338143fc2329.tar.xz
ftrace: Dynamically create the probe ftrace_ops for the trace_array
In order to eventually have each trace_array instance have its own unique set of function probes (triggers), the trace array needs to hold the ops and the filters for the probes. This is the first step to accomplish this. Instead of having the private data of the probe ops point to the trace_array, create a separate list that the trace_array holds. There's only one private_data for a probe, we need one per trace_array. The probe ftrace_ops will be dynamically created for each instance, instead of being static. Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace_events.c')
-rw-r--r--kernel/trace/trace_events.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
index 713bec614312..48c7f70cbac7 100644
--- a/kernel/trace/trace_events.c
+++ b/kernel/trace/trace_events.c
@@ -2653,7 +2653,7 @@ event_enable_func(struct trace_array *tr, struct ftrace_hash *hash,
ops = param ? &event_disable_count_probe_ops : &event_disable_probe_ops;
if (glob[0] == '!') {
- ret = unregister_ftrace_function_probe_func(glob+1, ops);
+ ret = unregister_ftrace_function_probe_func(glob+1, tr, ops);
goto out;
}