Omar Sandoval 35abb67de7 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>		2016-06-20 09:54:19 -04:00
..
postprocess
coresight.txt	coresight: stm: adding driver for CoreSight STM component	2016-05-03 14:59:30 -07:00
events-kmem.txt
events-msr.txt
events-nmi.txt
events-power.txt
events.txt	tracing: Add support for named hist triggers	2016-04-19 18:56:01 -04:00
ftrace-design.txt
ftrace.txt	This includes two new updates for the ftrace infrastructure.	2016-05-18 18:55:19 -07:00
function-graph-fold.vim
intel_th.txt
kprobetrace.txt	tracing: expose current->comm to [ku]probe events	2016-06-20 09:54:19 -04:00
mmiotrace.txt
ring-buffer-design.txt
stm.txt
tracepoint-analysis.txt
tracepoints.txt
uprobetracer.txt	tracing: expose current->comm to [ku]probe events	2016-06-20 09:54:19 -04:00