Messages in this thread | | | Subject | Re: [PATCH 19/20 -v5] Trace irq disabled critical timings | From | Peter Zijlstra <> | Date | Wed, 23 Jan 2008 18:58:23 +0100 |
| |
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.
| |