On Sat, Jan 19, 2008 at 06:33:30AM +0100, Andi Kleen wrote:
quoted text
> > 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
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/