Prev: how to debug a kernel that does not power off?
Next: [patch 0/2] x86,pat: Reduce contention on the memtype_lock -V4
From: Steven Rostedt on 23 Mar 2010 20:00
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(a)elte.hu>
> > CC: Peter Zijlstra <peterz(a)infradead.org>
> > Signed-off-by: Jan Kara <jack(a)suse.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.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: how to debug a kernel that does not power off?
Next: [patch 0/2] x86,pat: Reduce contention on the memtype_lock -V4