| 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
| ||
|
Message-ID: <1289226184.12418.4.camel@gandalf.stny.rr.com> Date: Mon, 08 Nov 2010 09:23:04 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: Christoph Hellwig <hch@...radead.org> Cc: Chris Wilson <chris@...is-wilson.co.uk>, Yuanhan Liu <yuanhan.liu@...ux.intel.com>, linux-kernel@...r.kernel.org, Frederic Weisbecker <fweisbec@...il.com>, Ingo Molnar <mingo@...hat.com> Subject: Re: [PATCH] Tracing: do export trace_set_clr_event On Mon, 2010-11-08 at 09:14 -0500, Christoph Hellwig wrote: > On Mon, Nov 08, 2010 at 09:02:14AM -0500, Steven Rostedt wrote: > > I like the trace=on parameter much better. If that is set we could > > enable the tracepoints of that module at load time. I really do not want > > to export the function that was proposed in that patch. > > Yes. Adding generic support in the module loader to turn on tracepoint > seems like the much better long term strategy. Even better if it allows > turning on individual points instead of all or nothing. I was thinking the same. How about this: trace=1 - all tracepoints in the module is enabled trace=0 - same as leaving it off trace=name - a specific tracepoint is enabled, using the simple globs that set_event allows. trace=name1,name2,name3 - for more than one tracepoint. -- 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