Re: [PATCH 19/20 -v5] Trace irq disabled critical timings

[Peter Zijlstra]

On Wed, 2008-01-23 at 12:27 -0500, Frank Ch. Eigler wrote:
> Hi -
> 
> On Wed, Jan 23, 2008 at 12:11:07PM -0500, Steven Rostedt wrote:
> > This patch adds latency tracing for critical timings
> > (how long interrupts are disabled for).
> > [...]
> 
> Is there an opportunity here to share effort with latencytop, and
> ideally to use markers as much as possible for these event hooks?

I'm still thinking latencytop should only record stack traces and do the
rest in user-space. 

Also, the things the latency tracer and latecytop measure are quite
different. the latency tracer measures how long a non-schedulable
section is, latencytop measures how a task was scheduled away.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/