linux-kernel - Re: [PATCH][RFC] tracing: Enable tracepoints via module parameters

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1299629657.20306.105.camel@gandalf.stny.rr.com>
Date:	Tue, 08 Mar 2011 19:14:17 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Yuanhan Liu <yuanhan.liu@...ux.intel.com>,
	chris <chris@...is-wilson.co.uk>
Subject: Re: [PATCH][RFC] tracing: Enable tracepoints via module parameters

On Tue, 2011-03-08 at 19:07 -0500, Mathieu Desnoyers wrote:

> So what you are saying here is that modifying /etc/modprobe.d/ is the actual
> interface you propose presenting to the end-users to control their tracepoints ?

If you want to have them enabled on boot, sure.

> Maybe I am missing something, but this interface seems to lack the layer of
> finish we might want to put into a user-visible API. I don't really see how
> distributions can hope to automate any of this for their end-user without making
> a mess of the /etc/modprobe.d/ they ship with.

What distros enable tracepoints by default?

If you want to enable a tracepoint on module load simply do:

 modprobe mymod trace_my_tracepoint=1

Otherwise modify your modprobe.d directory. This is the way users have
been doing module parameters for years.

That's pretty simple to me.

-- 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/