Re: [PATCH v3] tracing: expose current->comm to [ku]probe events

2016-06-17 Thread Omar Sandoval
On Fri, Jun 17, 2016 at 12:19:27PM -0400, Steven Rostedt wrote: > On Thu, 9 Jun 2016 11:55:34 +0900 > Masami Hiramatsu wrote: > > > On Wed, 8 Jun 2016 18:38:02 -0700 > > Omar Sandoval wrote: > > > > > From: Omar Sandoval > > > > > > ftrace is very quick to give up on saving the task command

Re: [PATCH v3] tracing: expose current->comm to [ku]probe events

2016-06-17 Thread Steven Rostedt
On Thu, 9 Jun 2016 11:55:34 +0900 Masami Hiramatsu wrote: > On Wed, 8 Jun 2016 18:38:02 -0700 > Omar Sandoval wrote: > > > From: Omar Sandoval > > > > ftrace is very quick to give up on saving the task command line (see > > `trace_save_cmdline()`). The workaround for events which really care

Re: [PATCH v3] tracing: expose current->comm to [ku]probe events

2016-06-08 Thread Masami Hiramatsu
On Wed, 8 Jun 2016 18:38:02 -0700 Omar Sandoval wrote: > From: Omar Sandoval > > 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.

[PATCH v3] tracing: expose current->comm to [ku]probe events

2016-06-08 Thread Omar Sandoval
From: Omar Sandoval 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 straigh