From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 00/12 -next] [for linux-next] ftrace: Recursion protection and speed up
Date: Wed, 23 Jan 2013 15:30:02 -0500 [thread overview]
Message-ID: <20130123203002.957226869@goodmis.org> (raw)
This change set replaces the function tracing recursion protection
with a context one, that keeps track of interrupts, NMIs, softirqs,
such that we do not need to disable interrupts and not miss any
events, as the old recursion protection had a race where interrupt
events could be dropped.
This also speeds up function tracing by 15% or more.
I'm posting these as a generic review of the changes I'll be pushing
into linux-next and will be pushing this for 3.9.
These patches have passed a series of tests I've run on few machines
with several different configs and such.
You can find the patches here. I'll add these to linux-next tomorrow.
-- Steve
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/core
Head SHA1: 0b07436d95b5404134da4d661fd183eac863513e
Steven Rostedt (12):
tracing: Remove trace.h header from trace_clock.c
tracing: Fix race with max_tr and changing tracers
tracing: Fix selftest function recursion accounting
ftrace: Fix global function tracers that are not recursion safe
ftrace: Fix function tracing recursion self test
ftrace: Optimize the function tracer list loop
ftrace: Add context level recursion bit checking
tracing: Make the trace recursion bits into enums
tracing: Avoid unnecessary multiple recursion checks
ftrace: Use only the preempt version of function tracing
ring-buffer: User context bit recursion checking
ring-buffer: Remove trace.h from ring_buffer.c
----
kernel/trace/ftrace.c | 82 ++++++++++++++++---------
kernel/trace/ring_buffer.c | 88 ++++++++++++++++++--------
kernel/trace/trace.c | 29 ++++++---
kernel/trace/trace.h | 133 ++++++++++++++++++++++++++++++++++++----
kernel/trace/trace_clock.c | 2 -
kernel/trace/trace_functions.c | 61 +++++-------------
kernel/trace/trace_selftest.c | 19 ++----
7 files changed, 275 insertions(+), 139 deletions(-)
next reply other threads:[~2013-01-23 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 20:30 Steven Rostedt [this message]
2013-01-23 20:30 ` [PATCH 01/12 -next] tracing: Remove trace.h header from trace_clock.c Steven Rostedt
2013-01-23 20:30 ` [PATCH 02/12 -next] tracing: Fix race with max_tr and changing tracers Steven Rostedt
2013-01-23 20:30 ` [PATCH 03/12 -next] tracing: Fix selftest function recursion accounting Steven Rostedt
2013-01-23 20:30 ` [PATCH 04/12 -next] ftrace: Fix global function tracers that are not recursion safe Steven Rostedt
2013-01-23 20:30 ` [PATCH 05/12 -next] ftrace: Fix function tracing recursion self test Steven Rostedt
2013-01-23 20:30 ` [PATCH 06/12 -next] ftrace: Optimize the function tracer list loop Steven Rostedt
2013-01-23 20:30 ` [PATCH 07/12 -next] ftrace: Add context level recursion bit checking Steven Rostedt
2013-01-23 20:30 ` [PATCH 08/12 -next] tracing: Make the trace recursion bits into enums Steven Rostedt
2013-01-23 20:30 ` [PATCH 09/12 -next] tracing: Avoid unnecessary multiple recursion checks Steven Rostedt
2013-01-23 20:30 ` [PATCH 10/12 -next] ftrace: Use only the preempt version of function tracing Steven Rostedt
2013-01-23 20:30 ` [PATCH 11/12 -next] ring-buffer: User context bit recursion checking Steven Rostedt
2013-01-23 20:30 ` [PATCH 12/12 -next] ring-buffer: Remove trace.h from ring_buffer.c 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=20130123203002.957226869@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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