Messages in this thread |  | | | Date | Sun, 5 Apr 2009 16:47:05 +0200 | | From | Ingo Molnar <> | | Subject | Re: [PATCH 0/4] [GIT PULL] for tip/tracing/filters |
| |
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Sat, 4 Apr 2009, Tom Zanussi wrote: > > On Fri, 2009-04-03 at 10:36 -0400, Steven Rostedt wrote: > > > > I'm guessing the problem is that CONFIG_EVENT_TRACER wasn't selected but > > should have been, because those tracers all now export events > > (trace_event_types.h, included by trace_export.c). I'm not sure this is > > the right way to do it, but the patch below selects EVENT_TRACER if > > TRACING is selected (a couple of the exported events belong to bprint > > and print, which don't have a config option other than TRACING, so it > > seems to belong there). > > > > Signed-off-by: Tom Zanussi <tzanussi@gmail.com> > > > > --- > > kernel/trace/Kconfig | 3 ++- > > 1 files changed, 2 insertions(+), 1 deletions(-) > > > > diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig > > index 8a41360..a061746 100644 > > --- a/kernel/trace/Kconfig > > +++ b/kernel/trace/Kconfig > > @@ -56,6 +56,7 @@ config TRACING > > select TRACEPOINTS > > select NOP_TRACER > > select BINARY_PRINTF > > + select EVENT_TRACER > > Yeah, we can do this.
Yeah - it has become more of a core facility thing, not a separate plugin.
That's the long-term healthy life-cycle for certain tracing functionality anyway: if it becomes so useful that all tracers want to make use of it, it becomes part of the standard infrastructure.
Ingo
|  |