aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorMasami Hiramatsu <[email protected]>2020-04-25 14:49:17 +0900
committerSteven Rostedt (VMware) <[email protected]>2020-05-06 09:04:11 -0400
commitda0f1f4167e3af69e1d8b32d6d65195ddd2bfb64 (patch)
tree3f3004ade391b9d890c55ab35942a949eb5471ed /tools/perf/scripts/python/export-to-sqlite.py
parentdcbd21c9fca5e954fd4e3d91884907eb6d47187e (diff)
tracing/boottime: Fix kprobe event API usage
Fix boottime kprobe events to use API correctly for multiple events. For example, when we set a multiprobe kprobe events in bootconfig like below, ftrace.event.kprobes.myevent { probes = "vfs_read $arg1 $arg2", "vfs_write $arg1 $arg2" } This cause an error; trace_boot: Failed to add probe: p:kprobes/myevent (null) vfs_read $arg1 $arg2 vfs_write $arg1 $arg2 This shows the 1st argument becomes NULL and multiprobes are merged to 1 probe. Link: http://lkml.kernel.org/r/158779375766.6082.201939936008972838.stgit@devnote2 Cc: Ingo Molnar <[email protected]> Cc: [email protected] Fixes: 29a154810546 ("tracing: Change trace_boot to use kprobe_event interface") Reviewed-by: Tom Zanussi <[email protected]> Signed-off-by: Masami Hiramatsu <[email protected]> Signed-off-by: Steven Rostedt (VMware) <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions