From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: [for-next][PATCH 00/18] ftrace/rcu: Handle unsafe RCU functions and ftrace callbacks
Date: Wed, 04 Sep 2013 10:35:52 -0400 [thread overview]
Message-ID: <20130904143552.456506259@goodmis.org> (raw)
This is the latest patches to be queued for 3.12.
A little late, but as Dave Jones has been stumbling over this for a
while, I thought it would be good to get it in now. It's not that
complex to resolve any issues that may pop up.
I'll keep it in linux-next for a while to make sure it really is clean.
Note, the checker will stumble over a few functions in irq and scheduler
code if enabled. This is because those patches have not received Acks
from Thomas Gleixner and Peter Zijlstra. When I get those acks, I'll
add the changes to silent those too.
Thanks to Paul McKenney for reviewing the patches.
Enjoy,
-- Steve
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 7fb3a66134ed5a40448131cf4195823d22f70aa3
Alexander Z Lam (1)
tracing: Make tracing_cpumask available for all instances
Steven Rostedt (Red Hat) (17)
ftrace: Fix a slight race in modifying what function callback gets traced
ftrace/rcu: Do not trace debug_lockdep_rcu_enabled()
ftrace: Add hash list to save RCU unsafe functions
ftrace: Do not set ftrace records for unsafe RCU when not allowed
ftrace: Set ftrace internal function tracing RCU safe
ftrace: Add test for ops against unsafe RCU functions in callback
ftrace: Do not display non safe RCU functions in available_filter_functions
ftrace: Add rcu_unsafe_filter_functions file
ftrace: Add selftest to check if RCU unsafe functions are filtered properly
ftrace: Create a RCU unsafe checker
ftrace: Add infrastructure to stop RCU unsafe checker from checking
ftrace: Disable RCU unsafe checker when function graph is enabled
ftrace: Disable the RCU unsafe checker when irqsoff is enabled
ftrace/lockdep: Have the RCU lockdep splat show what function triggered
ftrace/rcu: Mark functions that are RCU unsafe
ftrace/cpuidle/x86: Mark functions that are RCU unsafe
ftrace: Print a message when the rcu checker is disabled
----
b/arch/x86/kernel/process.c | 2
b/drivers/cpuidle/cpuidle.c | 2
b/include/asm-generic/vmlinux.lds.h | 10 +
b/include/linux/ftrace.h | 38 +++++
b/kernel/cpu/idle.c | 2
b/kernel/lockdep.c | 2
b/kernel/rcupdate.c | 2
b/kernel/rcutiny.c | 1
b/kernel/rcutree.c | 7 +
b/kernel/trace/Kconfig | 22 +++
b/kernel/trace/ftrace.c | 17 ++
b/kernel/trace/trace.c | 37 ++---
b/kernel/trace/trace.h | 1
b/kernel/trace/trace_functions.c | 48 ++++++-
b/kernel/trace/trace_irqsoff.c | 16 ++
b/kernel/trace/trace_selftest.c | 94 +++++++++++++
b/kernel/trace/trace_selftest_dynamic.c | 7 +
include/linux/ftrace.h | 8 +
kernel/trace/ftrace.c | 218 +++++++++++++++++++++++++++++---
kernel/trace/trace.h | 17 ++
kernel/trace/trace_functions.c | 40 +++++
21 files changed, 551 insertions(+), 40 deletions(-)
next reply other threads:[~2013-09-04 14:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 14:35 Steven Rostedt [this message]
2013-09-04 14:35 ` [for-next][PATCH 01/18] tracing: Make tracing_cpumask available for all instances Steven Rostedt
2013-09-04 14:35 ` [for-next][PATCH 02/18] ftrace: Fix a slight race in modifying what function callback gets traced Steven Rostedt
2013-09-04 14:35 ` [for-next][PATCH 03/18] ftrace/rcu: Do not trace debug_lockdep_rcu_enabled() Steven Rostedt
2013-09-04 14:35 ` [for-next][PATCH 04/18] ftrace: Add hash list to save RCU unsafe functions Steven Rostedt
2013-09-04 14:35 ` [for-next][PATCH 05/18] ftrace: Do not set ftrace records for unsafe RCU when not allowed Steven Rostedt
2013-09-04 14:35 ` [for-next][PATCH 06/18] ftrace: Set ftrace internal function tracing RCU safe Steven Rostedt
2013-09-04 14:35 ` [for-next][PATCH 07/18] ftrace: Add test for ops against unsafe RCU functions in callback Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 08/18] ftrace: Do not display non safe RCU functions in available_filter_functions Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 09/18] ftrace: Add rcu_unsafe_filter_functions file Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 10/18] ftrace: Add selftest to check if RCU unsafe functions are filtered properly Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 11/18] ftrace: Create a RCU unsafe checker Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 12/18] ftrace: Add infrastructure to stop RCU unsafe checker from checking Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 13/18] ftrace: Disable RCU unsafe checker when function graph is enabled Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 14/18] ftrace: Disable the RCU unsafe checker when irqsoff " Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 15/18] ftrace/lockdep: Have the RCU lockdep splat show what function triggered Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 16/18] ftrace/rcu: Mark functions that are RCU unsafe Steven Rostedt
2013-09-04 16:43 ` Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 17/18] ftrace/cpuidle/x86: " Steven Rostedt
2013-09-04 14:36 ` [for-next][PATCH 18/18] ftrace: Print a message when the rcu checker is disabled Steven Rostedt
2013-09-04 18:27 ` [for-next][PATCH 00/18] ftrace/rcu: Handle unsafe RCU functions and ftrace callbacks 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=20130904143552.456506259@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 \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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