Prev: [PATCH 08/18] lockdep: Provide config option for enabling lock tracepoints
Next: shutdown bugs, since about 2.6.31 or so
From: Jan Kara on 22 Mar 2010 20:40

Hi,

currently, when one tracer is selected, most of tracepoints for other
tracers also gets pulled into the kernel. So for example it's not possible
to enable BLK_DEV_IO_TRACE without polluting slab allocation paths with
tracepoint checks (see changelog of patch 01). This patch set adds a
possibility for each set of trace points to be compile-enabled separately.
The first patch contains the necessary magic in linux/tracepoint.h. Other
patches just tell tracing framework about correspoding config options
and possibly introduce them if they did not exist before.
The patches in this patch set are actually completely independent so
they can be merged via respective subsystem trees. But changes are rather
tiny so I don't expect much conflicts...

Honza
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 08/18] lockdep: Provide config option for enabling lock tracepoints
Next: shutdown bugs, since about 2.6.31 or so