Paul,
As we talked about earlier, I set up a branch based off of v3.11-rc2 which
the first patch has my tracing patch I need for other updates, and
the other three are RCU specific patches that you should take.
You can either just pull this branch from my tree, or you can pull
just the first patch (to keep the same SHA1) and apply the other three
patches any way you want.
I tested all these patches through my standard tests, but I did not run
the RCU ones through any specific RCU tests (like rcutorture). They
shouldn't affect the process of RCU in anyway and only should touch
the way trace points export their strings. You may want to run them through
other tests just to make sure there isn't some strange side effect I
caused. :-)
-- Steve
Please pull the latest ftrace/rcu tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
ftrace/rcu
Head SHA1: b7c2caaa81e8ce2643db611a661d1ef7f9fe6db8
SHA1 of first patch: 102c9323c35a83789ad5ebd3c45fa8fb389add88
Steven Rostedt (Red Hat) (4):
tracing: Add __tracepoint_string() to export string pointers
rcu: Add const annotation to char * for RCU tracepoints and functions
rcu: Simplify RCU_STATE_INITIALIZER() macro
rcu: Have the RCU tracepoints use the tracepoint_string infrastructure
----
include/asm-generic/vmlinux.lds.h | 7 ++-
include/linux/ftrace_event.h | 34 ++++++++++++
include/linux/rcupdate.h | 4 +-
include/trace/events/rcu.h | 82 ++++++++++++++---------------
kernel/rcu.h | 2 +-
kernel/rcupdate.c | 2 +-
kernel/rcutiny.c | 2 +-
kernel/rcutiny_plugin.h | 2 +-
kernel/rcutorture.c | 8 +--
kernel/rcutree.c | 105 +++++++++++++++++++++----------------
kernel/rcutree.h | 2 +-
kernel/rcutree_plugin.h | 42 +++++++--------
kernel/trace/trace.h | 3 ++
kernel/trace/trace_printk.c | 19 +++++++
14 files changed, 195 insertions(+), 119 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
