From mboxrd@z Thu Jan  1 00:00:00 1970
From: peterz@infradead.org (Peter Zijlstra)
Date: Wed, 10 Dec 2008 20:28:38 +0100
Subject: [ltt-dev] [patch] add tracepoints to trace activate/deactivate
 task
In-Reply-To: <20081210175245.GA13055@Krystal>
References: <20081208194948.GC27166@redhat.com>
	<1228766050.6939.7.camel@twins> <20081208223840.GA30314@redhat.com>
	<1228776169.12729.2.camel@twins> <20081209210048.GA4440@redhat.com>
	<20081209221012.GA4673@Krystal> <1228892902.6978.23.camel@twins>
	<20081210122712.GC28524@Krystal> <1228914941.12143.12.camel@twins>
	<20081210171423.GA3137@redhat.com>  <20081210175245.GA13055@Krystal>
Message-ID: <1228937318.12143.24.camel@twins>

On Wed, 2008-12-10 at 12:52 -0500, Mathieu Desnoyers wrote:

> > I understand and appreciate what you guys are saying about do not
> > instrument the code too generally, but IMHO activate/deactivate are core
> > scheduler primitives, which are difficult to piece together otherwise.

That's simply not true - its mostly a scheduler implementation detail.

Re-read my previous email.