lkml.org 
[lkml]   [2008]   [Jan]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Announce] Development release 0.1 of the LatencyTOP tool II
On Sat, Jan 19, 2008 at 06:33:30AM +0100, Andi Kleen wrote:
> > another thing that the current profiling can't do, is to show what the
> > system is doing
> > when it hits the latency.. so someone calling fsync() will show up in the
> > waiting for
> > IO function, but not that it was due to an fsync().
>
> Hmm so how about extending oprofile to always log the syscall number
> in the event logs (can be gotten from top of stack). I think given

Ok to handle exceptions like page faults this way you would need to save
the vector somewhere on entry, but that shouldn't be very costly
or difficult and could probably even be done unconditionally.

-Andi


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