From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-team@lge.com
Subject: Re: [PATCH 0/4] ftrace: Add 'function-fork' trace option (v1)
Date: Thu, 30 Mar 2017 18:28:29 -0400 [thread overview]
Message-ID: <20170330182829.266f6bf0@gandalf.local.home> (raw)
In-Reply-To: <20170331072550.22454e289ac28c562073dcb4@kernel.org>
On Fri, 31 Mar 2017 07:25:50 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> On Thu, 30 Mar 2017 09:49:29 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Thu, 30 Mar 2017 10:40:46 +0900
> > Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > > Hi Masami,
> > >
> > > On Thu, Mar 30, 2017 at 9:54 AM, Masami Hiramatsu <mhiramat@kernel.org> wrote:
> > > > On Wed, 29 Mar 2017 10:46:21 +0900
> > > > Namhyung Kim <namhyung@kernel.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.
> > > >
> > > > By the way, I thought that event-fork option also effected to
> > > > function tracer. Is there any reason we should separate those?
> > > > I mean, we can add "trace-fork" option instead of "function-fork"
> > > > for setting both pid filters at once.
> > > >
> > > > Thank you,
> > >
> > > I'm ok with combining two options.
> > >
> >
> > I prefer not. Mainly because they are two different mechanisms, and
> > only event-fork is available now.
>
> That sounds like implementation issue. From the viewpoint of users,
> they may want to use just one knob to filter both. And I didn't
> suggest replacing event-fork, but adding trace-fork for both, like a
> superset option.
Well, trace-cmd will just set both when one adds -c
I'd like to have two options for now. We can always add a superset
option for later.
-- Steve
>
> > trace-cmd will use ptrace if function
> > fork is needed. Having it separate will let trace-cmd know if it needs
> > to use ptrace or not for function forking.
>
> Yeah, that's a good workaround for older kernel.
prev parent reply other threads:[~2017-03-30 22:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 1:46 Namhyung Kim
2017-03-29 1:46 ` [PATCH 1/4] ftrace: Fix function pid filter on instances Namhyung Kim
2017-03-29 2:08 ` Steven Rostedt
2017-03-29 2:20 ` Namhyung Kim
2017-03-29 2:28 ` Steven Rostedt
2017-03-29 2:42 ` Namhyung Kim
2017-03-29 2:58 ` Steven Rostedt
2017-03-29 3:02 ` Namhyung Kim
2017-03-29 2:25 ` Namhyung Kim
2017-03-29 1:46 ` [PATCH 2/4] ftrace: Add 'function-fork' trace option Namhyung Kim
2017-03-29 2:18 ` Steven Rostedt
2017-03-29 2:21 ` Steven Rostedt
2017-03-29 1:46 ` [PATCH 3/4] selftests: ftrace: Add -l/--logdir option Namhyung Kim
2017-03-29 8:30 ` Masami Hiramatsu
2017-03-29 1:46 ` [PATCH 4/4] selftests: ftrace: Add a testcase for function PID filter Namhyung Kim
2017-03-29 1:51 ` [PATCH 0/4] ftrace: Add 'function-fork' trace option (v1) Steven Rostedt
2017-03-30 0:54 ` Masami Hiramatsu
2017-03-30 1:40 ` Namhyung Kim
2017-03-30 13:49 ` Steven Rostedt
2017-03-30 22:25 ` Masami Hiramatsu
2017-03-30 22:28 ` Steven Rostedt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170330182829.266f6bf0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®