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>,
containers@lists.osdl.org,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
"Serge E. Hallyn" <serue@us.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: [PATCH 0/5] ftrace: rebase patches on top of tip/master + some extras
Date: Wed, 26 Nov 2008 00:16:22 -0500 [thread overview]
Message-ID: <20081126051622.134970943@goodmis.org> (raw)
Ingo,
Here's my patches rebased against latest tip/master. I also
added a couple of goodies at the end to enhance the function-graph
tracer.
The first patch is a repost of the set_ftrace_pid, so I am Cc'ing
the container guys so they can abuse me some more ;-)
The following patches are in:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
branch: tip/devel
Steven Rostedt (5):
ftrace: add function tracing to single thread
ftrace: use code patching for ftrace graph tracer
ftrace: let function tracing and function return run together
ftrace: add thread comm to function graph tracer
ftrace: add cpu annotation for function graph tracer
----
Documentation/ftrace.txt | 79 ++++++++++
arch/x86/kernel/entry_32.S | 5 +
arch/x86/kernel/ftrace.c | 48 ++++++-
include/linux/ftrace.h | 5 +
kernel/trace/ftrace.c | 264 +++++++++++++++++++++++++--------
kernel/trace/trace.c | 2 +-
kernel/trace/trace.h | 1 +
kernel/trace/trace_functions_graph.c | 51 +++++--
8 files changed, 373 insertions(+), 82 deletions(-)
--
next reply other threads:[~2008-11-26 5:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 5:16 Steven Rostedt [this message]
2008-11-26 5:16 ` [PATCH 1/5] ftrace: add function tracing to single thread Steven Rostedt
2008-11-26 5:29 ` Andrew Morton
2008-11-26 16:43 ` Steven Rostedt
2008-11-26 6:42 ` Eric W. Biederman
2008-11-26 6:54 ` Ingo Molnar
2008-11-26 16:55 ` Steven Rostedt
2008-11-26 16:54 ` Steven Rostedt
2008-11-26 5:16 ` [PATCH 2/5] ftrace: use code patching for ftrace graph tracer Steven Rostedt
[not found] ` <20081126051709.774546196-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org>
2008-11-26 5:35 ` Andrew Morton
2008-11-26 5:35 ` Andrew Morton
2008-11-26 6:52 ` Harvey Harrison
2008-11-26 8:04 ` Andrew Morton
2008-11-26 8:04 ` Andrew Morton
2008-11-26 8:27 ` Harvey Harrison
2008-11-26 8:35 ` Andrew Morton
[not found] ` <20081126003553.12d38150.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-11-26 8:44 ` Harvey Harrison
2008-11-26 8:44 ` Harvey Harrison
2008-11-26 9:05 ` Andrew Morton
2008-11-26 9:05 ` Andrew Morton
2008-11-26 9:22 ` Harvey Harrison
2008-11-26 16:46 ` Steven Rostedt
2008-11-26 18:02 ` Andrew Morton
2008-11-26 18:06 ` Harvey Harrison
2008-11-26 5:16 ` [PATCH 3/5] ftrace: let function tracing and function return run together Steven Rostedt
2008-11-26 5:16 ` [PATCH 4/5] ftrace: add thread comm to function graph tracer Steven Rostedt
2008-11-26 5:37 ` Andrew Morton
2008-11-26 16:48 ` Steven Rostedt
2008-11-26 18:04 ` Andrew Morton
2008-11-26 5:16 ` [PATCH 5/5] ftrace: add cpu annotation for " Steven Rostedt
2008-11-26 5:39 ` Andrew Morton
2008-11-26 5:47 ` Ingo Molnar
2008-11-26 5:55 ` Andrew Morton
2008-11-26 16:49 ` 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=20081126051622.134970943@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=serue@us.ibm.com \
--cc=sukadev@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.