[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160419223010.3c46e254@grimm.local.home>
Date: Tue, 19 Apr 2016 22:30:10 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Daniel Bristot de Oliveira <bristot@...hat.com>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Jiri Olsa <jolsa@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
linux-trace-users@...r.kernel.org
Subject: Re: [RFC][PATCH 0/4] tracing: Add event-fork to trace tasks
children
On Tue, 19 Apr 2016 23:05:28 -0300
Daniel Bristot de Oliveira <bristot@...hat.com> wrote:
> On 04/19/2016 11:34 AM, Steven Rostedt wrote:
> > This code adds the event-fork option that, when set, will have tasks
> > with their PIDs in set_event_pid add their children PIDs when they
> > fork. It will also remove their PID from the file on exit.
>
> That is a nice feature! I tested it and it works. But, look this...
>
> Set the event-fork, the current shell pid, and enable the trace:
>
> [root@f23 tracing]# echo event-fork > trace_options
> [root@f23 tracing]# echo $$ > set_ftrace_pid
event-fork does not affect function tracing. I'm currently working on
patches to create a function-fork option for 4.8.
-- Steve
Powered by blists - more mailing lists