linux-kernel - Re: [PATCH 2/4] tracing: introduce trace_set_clr_module

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 09 Nov 2010 13:31:27 +0000
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Yuanhan Liu <yuanhan.liu@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, rostedt@...dmis.org,
	fweisbec@...il.com, mingo@...hat.com
Subject: Re: [PATCH 2/4] tracing: introduce trace_set_clr_module_event

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.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
--
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/