diff options
author | Omar Sandoval <osandov@fb.com> | 2016-06-09 03:38:02 +0200 |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2016-06-20 15:54:19 +0200 |
commit | 35abb67de744b5dbaec54381f2f9e0246089331d (patch) | |
tree | be334f88bb9cdf78b7f2fd33529469ac352c179e /drivers/of | |
parent | ftrace: Have set_ftrace_pid use the bitmap like events do (diff) | |
download | linux-35abb67de744b5dbaec54381f2f9e0246089331d.tar.xz linux-35abb67de744b5dbaec54381f2f9e0246089331d.zip |
tracing: expose current->comm to [ku]probe events
ftrace is very quick to give up on saving the task command line (see
`trace_save_cmdline()`). The workaround for events which really care
about the command line is to explicitly assign it as part of the entry.
However, this doesn't work for kprobe events, as there's no
straightforward way to get access to current->comm. Add a kprobe/uprobe
event variable $comm which provides exactly that.
Link: http://lkml.kernel.org/r/f59b472033b943a370f5f48d0af37698f409108f.1465435894.git.osandov@fb.com
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'drivers/of')
0 files changed, 0 insertions, 0 deletions