From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: [PATCH 00/13] [GIT PULL] ftrace: Allow function tracer to be used by multiple clients
Date: Wed, 18 May 2011 22:11:51 -0400 [thread overview]
Message-ID: <20110519021151.600991800@goodmis.org> (raw)
Ingo,
Please pull the latest tip/perf/core tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/perf/core
Steven Rostedt (13):
ftrace: Replace FTRACE_FL_NOTRACE flag with a hash of ignored functions
ftrace: Use hash instead for FTRACE_FL_FILTER
ftrace: Create a global_ops to hold the filter and notrace hashes
ftrace: Separate hash allocation and assignment
ftrace: Use counters to enable functions to trace
ftrace: Add enabled_functions file
ftrace: Add ops parameter to ftrace_startup/shutdown functions
ftrace: Have global_ops store the functions that are to be traced
ftrace: Free hash with call_rcu_sched()
ftrace: Implement separate user function filtering
ftrace: Allow dynamically allocated function tracers
ftrace: Modify ftrace_set_filter/notrace to take ops
ftrace: Add self-tests for multiple function trace users
----
include/linux/ftrace.h | 33 +-
include/linux/kernel.h | 1 +
kernel/extable.c | 8 +
kernel/trace/ftrace.c | 992 ++++++++++++++++++++++++++++-----
kernel/trace/trace.h | 2 +
kernel/trace/trace_functions.c | 2 +
kernel/trace/trace_irqsoff.c | 1 +
kernel/trace/trace_sched_wakeup.c | 1 +
kernel/trace/trace_selftest.c | 214 +++++++-
kernel/trace/trace_selftest_dynamic.c | 6 +
kernel/trace/trace_stack.c | 1 +
11 files changed, 1116 insertions(+), 145 deletions(-)
next reply other threads:[~2011-05-19 2:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 2:11 Steven Rostedt [this message]
2011-05-19 2:11 ` [PATCH 01/13] ftrace: Replace FTRACE_FL_NOTRACE flag with a hash of ignored Steven Rostedt
2011-05-19 2:11 ` [PATCH 02/13] ftrace: Use hash instead for FTRACE_FL_FILTER Steven Rostedt
2011-05-19 2:11 ` [PATCH 03/13] ftrace: Create a global_ops to hold the filter and notrace hashes Steven Rostedt
2011-05-19 2:11 ` [PATCH 04/13] ftrace: Separate hash allocation and assignment Steven Rostedt
2011-05-19 2:11 ` [PATCH 05/13] ftrace: Use counters to enable functions to trace Steven Rostedt
2011-05-19 2:11 ` [PATCH 06/13] ftrace: Add enabled_functions file Steven Rostedt
2011-05-19 2:11 ` [PATCH 07/13] ftrace: Add ops parameter to ftrace_startup/shutdown functions Steven Rostedt
2011-05-19 2:11 ` [PATCH 08/13] ftrace: Have global_ops store the functions that are to be traced Steven Rostedt
2011-05-19 2:12 ` [PATCH 09/13] ftrace: Free hash with call_rcu_sched() Steven Rostedt
2011-05-19 2:12 ` [PATCH 10/13] ftrace: Implement separate user function filtering Steven Rostedt
2011-05-19 2:12 ` [PATCH 11/13] ftrace: Allow dynamically allocated function tracers Steven Rostedt
2011-05-19 2:12 ` [PATCH 12/13] ftrace: Modify ftrace_set_filter/notrace to take ops Steven Rostedt
2011-05-19 2:12 ` [PATCH 13/13] ftrace: Add self-tests for multiple function trace users 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=20110519021151.600991800@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome