From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
linux-trace-users@vger.kernel.org
Subject: [RFC][PATCH 0/4] tracing: Add event-fork to trace tasks children
Date: Tue, 19 Apr 2016 10:34:21 -0400 [thread overview]
Message-ID: <20160419143421.829909157@goodmis.org> (raw)
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.
Thanks to HPA for suggesting the bitmask over the more complex special
"hash" algorithm I originally had. It simplified the code and makes
it more robust.
Steven Rostedt (3):
tracing: Rename check_ignore_pid() to ignore_this_task()
tracing: Use pid bitmap instead of a pid array for set_event_pid
tracing: Add infrastructure to allow set_event_pid to follow children
Steven Rostedt (Red Hat) (1):
tracing: Update the documentation to describe "event-fork" option
----
Documentation/trace/ftrace.txt | 34 +++--
kernel/trace/trace.c | 3 +
kernel/trace/trace.h | 7 +-
kernel/trace/trace_events.c | 297 +++++++++++++++++++++++------------------
4 files changed, 201 insertions(+), 140 deletions(-)
next reply other threads:[~2016-04-19 14:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 14:34 Steven Rostedt [this message]
2016-04-19 14:34 ` [RFC][PATCH 1/4] tracing: Rename check_ignore_pid() to ignore_this_task() Steven Rostedt
2016-04-19 14:34 ` [RFC][PATCH 2/4] tracing: Use pid bitmap instead of a pid array for set_event_pid Steven Rostedt
2016-04-19 16:55 ` Mathieu Desnoyers
2016-04-19 17:19 ` Steven Rostedt
2016-04-19 18:57 ` H. Peter Anvin
2016-04-19 19:41 ` Steven Rostedt
2016-04-19 20:17 ` Mathieu Desnoyers
2016-04-19 20:50 ` Steven Rostedt
2016-04-19 21:22 ` Mathieu Desnoyers
2016-04-19 22:49 ` Steven Rostedt
2016-04-19 22:59 ` Mathieu Desnoyers
2016-04-19 23:06 ` Steven Rostedt
2016-04-22 2:45 ` Namhyung Kim
2016-04-22 15:30 ` Steven Rostedt
2016-04-19 14:34 ` [RFC][PATCH 3/4] tracing: Add infrastructure to allow set_event_pid to follow children Steven Rostedt
2016-04-19 16:55 ` Mathieu Desnoyers
2016-04-19 17:13 ` Steven Rostedt
2016-04-19 20:30 ` Mathieu Desnoyers
2016-04-19 14:34 ` [RFC][PATCH 4/4] tracing: Update the documentation to describe "event-fork" option Steven Rostedt
2016-04-20 2:05 ` [RFC][PATCH 0/4] tracing: Add event-fork to trace tasks children Daniel Bristot de Oliveira
2016-04-20 2:30 ` Steven Rostedt
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=20160419143421.829909157@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
/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