Re: [PATCH] tracing: expose current->comm to kprobe events

2016-06-03 Thread Omar Sandoval
On Fri, Jun 03, 2016 at 05:59:43PM +0900, Masami Hiramatsu wrote: > On Fri, 3 Jun 2016 00:40:02 +0900 > Namhyung Kim wrote: > > > Hello, > > > > On Wed, Jun 1, 2016 at 3:17 PM, Omar Sandoval wrote: > > > From: Omar Sandoval > > > > > > ftrace is very quick to give up on saving the task command

Re: [PATCH] tracing: expose current->comm to kprobe events

2016-06-03 Thread Masami Hiramatsu
On Fri, 3 Jun 2016 00:40:02 +0900 Namhyung Kim wrote: > Hello, > > On Wed, Jun 1, 2016 at 3:17 PM, 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] tracing: expose current->comm to kprobe events

2016-06-02 Thread Omar Sandoval
Hi, On Fri, Jun 03, 2016 at 12:40:02AM +0900, Namhyung Kim wrote: > Hello, > > On Wed, Jun 1, 2016 at 3:17 PM, 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 r

Re: [PATCH] tracing: expose current->comm to kprobe events

2016-06-02 Thread Namhyung Kim
Hello, On Wed, Jun 1, 2016 at 3:17 PM, 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 ent

[PATCH] tracing: expose current->comm to kprobe events

2016-05-31 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