Tom Zanussi 5f77a88b3f tracing/infrastructure: separate event tracer from event support
Add a new config option, CONFIG_EVENT_TRACING that gets selected
when CONFIG_TRACING is selected and adds everything needed by the stuff
in trace_export - basically all the event tracing support needed by e.g.
bprint, minus the actual events, which are only included if
CONFIG_EVENT_TRACER is selected.

So CONFIG_EVENT_TRACER can be used to turn on or off the generated events
(what I think of as the 'event tracer'), while CONFIG_EVENT_TRACING turns
on or off the base event tracing support used by both the event tracer and
the other things such as bprint that can't be configured out.

Signed-off-by: Tom Zanussi <tzanussi@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: fweisbec@gmail.com
LKML-Reference: <1239178441.10295.34.camel@tropicana>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-04-14 00:00:55 +02:00
..
2008-02-06 10:41:00 -08:00
2008-05-01 08:03:58 -07:00
2005-04-16 15:20:36 -07:00
2009-04-02 19:04:51 -07:00
2005-04-16 15:20:36 -07:00
2008-08-12 16:07:31 -07:00
2008-05-02 16:18:19 -07:00
2005-09-08 14:57:25 -07:00
2007-05-11 08:29:34 -07:00
2009-01-15 16:39:40 -08:00
2009-03-26 18:14:21 +01:00
2008-09-05 14:39:38 -07:00
2005-04-16 15:20:36 -07:00
2005-04-16 15:20:36 -07:00