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>
Subject: [PATCH 0/8] [GIT PULL][2.6.40] ftrace: cleanups
Date: Sat, 30 Apr 2011 11:30:40 -0400 [thread overview]
Message-ID: <20110430153040.354378898@goodmis.org> (raw)
Ingo,
I'm still working on the accounting of ftrace function tracer to be able
to have multiple users that do not conflict with each other in selecting
functions to trace. It's going well and is almost done.
But in doing this, there were several cleanups that had to be made first.
This patch series contains those cleanups and I've already run my tests
on them and wanted to get them out now, instead of sending them with
the major changes. This will let reviews focus on the major changes
and not have to worry about these cleanups. Reviewers can examine these
cleanups now if they want.
One nice thing about this patch set is the stats:
141 insertions(+), 214 deletions(-)
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 (8):
ftrace: Make FTRACE_WARN_ON() work in if condition
ftrace: Remove unnecessary disabling of irqs
ftrace: Remove failures file
ftrace: Remove FTRACE_FL_FAILED flag
ftrace: Remove FTRACE_FL_CONVERTED flag
ftrace: Move record update for normal and modules into a separate function
ftrace: Consolidate updating of ftrace_trace_function
ftrace: Consolidate the function match routines for normal and mods
----
include/linux/ftrace.h | 8 +-
kernel/trace/ftrace.c | 347 +++++++++++++++++++-----------------------------
2 files changed, 141 insertions(+), 214 deletions(-)
next reply other threads:[~2011-04-30 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 15:30 Steven Rostedt [this message]
2011-04-30 15:30 ` [PATCH 1/8] ftrace: Make FTRACE_WARN_ON() work in if condition Steven Rostedt
2011-04-30 15:30 ` [PATCH 2/8] ftrace: Remove unnecessary disabling of irqs Steven Rostedt
2011-04-30 15:30 ` [PATCH 3/8] ftrace: Remove failures file Steven Rostedt
2011-04-30 15:30 ` [PATCH 4/8] ftrace: Remove FTRACE_FL_FAILED flag Steven Rostedt
2011-04-30 15:30 ` [PATCH 5/8] ftrace: Remove FTRACE_FL_CONVERTED flag Steven Rostedt
2011-04-30 15:30 ` [PATCH 6/8] ftrace: Move record update for normal and modules into a separate function Steven Rostedt
2011-04-30 15:30 ` [PATCH 7/8] ftrace: Consolidate updating of ftrace_trace_function Steven Rostedt
2011-04-30 15:30 ` [PATCH 8/8] ftrace: Consolidate the function match routines for normal and mods Steven Rostedt
2011-05-01 17:36 ` [PATCH 0/8] [GIT PULL][2.6.40] ftrace: cleanups Ingo Molnar
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=20110430153040.354378898@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.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
all inboxes | Powered by JetHome®