[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1289310971.12418.89.camel@gandalf.stny.rr.com>
Date: Tue, 09 Nov 2010 08:56:11 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Chris Wilson <chris@...is-wilson.co.uk>
Cc: Yuanhan Liu <yuanhan.liu@...ux.intel.com>,
linux-kernel@...r.kernel.org, fweisbec@...il.com, mingo@...hat.com
Subject: Re: [PATCH 2/4] tracing: introduce trace_set_clr_module_event
On Tue, 2010-11-09 at 13:31 +0000, Chris Wilson wrote:
> On Tue, 9 Nov 2010 21:20:59 +0800, Yuanhan Liu <yuanhan.liu@...ux.intel.com> wrote:
> > On Tue, Nov 09, 2010 at 11:27:18AM +0000, Chris Wilson wrote:
> > > I've not looked closely at this yet, but it seems like we should be able
> > > to hook into a trace_module_notify
> >
> > But there should be someplace to enable these events, right? And how do
> > you tell trace_module_notify to just enable one or several specific
> > event?
>
> Yes, I was thinking of extending the module loader to permit core to
> hook into parse_args() and so the trace= facility could work with any
> module without exporting any new functions.
Exactly, if you want, I probably could whip up a patch.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists