[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170328215129.71b55ffc@grimm.local.home>
Date: Tue, 28 Mar 2017 21:51:29 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, kernel-team@....com
Subject: Re: [PATCH 0/4] ftrace: Add 'function-fork' trace option (v1)
On Wed, 29 Mar 2017 10:46:21 +0900
Namhyung Kim <namhyung@...nel.org> wrote:
> Hello,
>
> This patchset add 'function-fork' option to function tracer which
> makes pid filter to be inherited like 'event-fork' does. During the
> test, I found a bug of pid filter on an instance directory. The patch
> 1 fixes it and maybe it should go to the stable tree.
>
> The function-fork option is disabled by default as event-fork does,
> but we might consider changing the default since it seems to be more
> natural from an user's perspective IMHO.
>
> The code is also available at 'ftrace/function-fork-v1' branch on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
>
Thanks for the reminder. I actually have this functionality working,
and just forgot to push it :-/ I've had it done months ago too.
I'll take a look at what you did and compare it to my changes. Now I
need to find which branch I left it in (I have 446 git branches in my
repo!)
-- Steve
Powered by blists - more mailing lists