From: Steven Rostedt <rostedt@goodmis.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-team@lge.com
Subject: Re: [PATCH 0/4] ftrace: Add 'function-fork' trace option (v2)
Date: Tue, 18 Apr 2017 21:25:53 -0400 [thread overview]
Message-ID: <20170418212553.1033d730@grimm.local.home> (raw)
In-Reply-To: <CAM9d7cg5HGQXxhH+o1uNq=xUg445Ui3AD8x3c4tLFXddxCoBLA@mail.gmail.com>
On Wed, 19 Apr 2017 09:27:28 +0900
Namhyung Kim <namhyung@kernel.org> wrote:
> Hi Steve,
>
> Sorry for little late,
>
> On Tue, Apr 18, 2017 at 4:18 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Mon, 17 Apr 2017 11:44:26 +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.
> >
> > Hmm, are the other patches dependent on it?
>
> Nop, but there will be a small clash on trace.h for the declaration.
Yep, I push up a merge with mainline with my linux-next branch to cover
the conflicts. I'll let Linus know about it too when I do my pull
request in the merge window.
>
> >
> > I think I may just push it separately to Linus now, but the other
> > patches will be on my devel branch which will not be abased off of this
> > fix. Will that break too much? I just cherry-picked a patch from my
> > urgent branch as it required to be on my devel branch and go to Linus.
>
> I don't think it breaks much.
Except that your test triggers the bug it uncovered ;-)
-- Steve
>
> >
> > Hmm, I may be able to make a separate branch with this. I have to see
> > how much it conflicts with my current development.
prev parent reply other threads:[~2017-04-19 1:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 2:44 [PATCH 0/4] ftrace: Add 'function-fork' trace option (v2) Namhyung Kim
2017-04-17 2:44 ` [PATCH 1/4] ftrace: Fix function pid filter on instances Namhyung Kim
2017-04-17 11:52 ` Masami Hiramatsu
2017-04-17 13:00 ` Namhyung Kim
2017-04-17 2:44 ` [PATCH 2/4] ftrace: Add 'function-fork' trace option Namhyung Kim
2017-04-17 2:44 ` [PATCH 3/4] selftests: ftrace: Add -l/--logdir option Namhyung Kim
2017-04-17 2:44 ` [PATCH 4/4] selftests: ftrace: Add a testcase for function PID filter Namhyung Kim
2017-04-17 19:18 ` [PATCH 0/4] ftrace: Add 'function-fork' trace option (v2) Steven Rostedt
2017-04-19 0:27 ` Namhyung Kim
2017-04-19 1:25 ` 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=20170418212553.1033d730@grimm.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;
as well as URLs for NNTP newsgroup(s).