linux-kernel - Re: [PATCH 06/18] sched: Generate trace points only if scheduler tracing is enabled

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:	Wed, 24 Mar 2010 01:31:08 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Jan Kara <jack@...e.cz>, LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 06/18] sched: Generate trace points only if scheduler
	tracing is enabled

On Tue, Mar 23, 2010 at 07:52:01PM -0400, Steven Rostedt wrote:
> On Tue, 2010-03-23 at 02:07 +0100, Frederic Weisbecker wrote:
> > On Tue, Mar 23, 2010 at 01:32:08AM +0100, Jan Kara wrote:
> > > CC: Ingo Molnar <mingo@...e.hu>
> > > CC: Peter Zijlstra <peterz@...radead.org>
> > > Signed-off-by: Jan Kara <jack@...e.cz>
> > > ---
> > 
> > 
> > Note this one is an exception.
> > Once tracing is enabled, we need the context switch
> > tracer anyway to keep track of the pid:cmdline mappings.
> > 
> > 
> 
> Yes, the scheduling tracepoints are needed by several tracers. This must
> be enabled by all.
> 
> But then again, I'm thinking it would be nicer to find a way to lower
> the impact than just turning them off.
> 
> Perhaps only allow the individual disabling if CONFIG_EMBEDDED is set.


Yeah agreed!

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