lkml.org 
[lkml]   [2008]   [Jan]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 19/20 -v5] Trace irq disabled critical timings
From
Date

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.



\
 
 \ /
  Last update: 2008-01-23 19:13    [W:0.090 / U:0.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site