[GIT PULL] tracing: Various cleanups for 2.6.32, v2

From: Frederic Weisbecker
Date: Thu Aug 06 2009 - 02:27:51 EST


Ingo,

This new shot fixes the build errors you've reported after testing
the first version.
The fact is that the trace_function() helper is not only used by the
function tracer but also by various other tracing callsites.

Instead of keeping it in the function tracer file and paint it
with messy #ifdefs, I think it's better to keep it in the generic
trace.c because it's actually a general helper for various tracers.

I've then zapped the trace_function() moving in the third patch but kept
one of its side effects necessary for the function graph tracer helpers
moving: the ftrace_cpu_disabled var globalizing.

This series also gained a new patch that shuts down a warning in
trace_events.c

Thanks,
Frederic.



The following changes since commit 1f9963cbb0280e0cd554161e00f1a0eeddbf1ae1:
Li Zefan (1):
tracing/filters: improve subsystem filter

are available in the git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git tracing/core

Frederic Weisbecker (6):
tracing/function-graph-tracer: Drop the useless nmi protection
tracing/core: Turn ftrace_cpu_disabled into a global var
tracing/core: Make the stack entry helpers global
tracing: Move sched event insertion helpers in the sched switch tracer file
tracing/function-graph-tracer: Move graph event insertion helpers in the graph tracer file
tracing/events: Only define remove_subsystem_dir() if CONFIG_MODULES

Lai Jiangshan (1):
tracing: Simplify print_graph_cpu()

arch/x86/kernel/ftrace.c | 4 -
kernel/trace/trace.c | 192 ++--------------------------------
kernel/trace/trace.h | 30 +++++-
kernel/trace/trace_events.c | 52 +++++-----
kernel/trace/trace_functions_graph.c | 152 ++++++++++++++++++++++-----
kernel/trace/trace_sched_switch.c | 57 ++++++++++
kernel/trace/trace_selftest.c | 1 +
7 files changed, 243 insertions(+), 245 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/