lkml.org 
[lkml]   [2010]   [May]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] tracing: Add task activate/deactivate tracepoints
From
Date
On Mon, 2010-05-31 at 10:00 +0200, Ingo Molnar wrote:
> >
> > NAK, aside from a few corner cases wakeup and sleep are the important
> > points.
> >
> > The activate and deactivate functions are implementation details.
>
> Frederic, can you show us a concrete example of where we dont know what is
> going on due to inadequate instrumentation? Can we fix that be extending the
> existing tracepoints?

Right, so a few of those corner cases I mentioned above are things like
re-nice, PI-boosts etc.. Those use deactivate, modify task-state,
activate cycles. so if you want to see those, we can add an explicit
tracepoint for those actions.

An explicit nice/PI-boost tracepoint is much clearer than trying to
figure out wth the deactivate/activate cycle was for.


\
 
 \ /
  Last update: 2010-05-31 10:15    [W:0.080 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site