lkml.org 
[lkml]   [2009]   [Feb]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] new irq tracer


    On Wed, 25 Feb 2009, Mathieu Desnoyers wrote:
    > > > The main thing I dislike about only tracing action->handler() calls is
    > > > that you are not tracing an IRQ per se, but rather the invocation of a
    > > > given handler within the interrupt. For instance, it would be difficult
    > > > to calculate the maximum interrupt latency for a given interrupt line,
    > > > because you don't have the "real" irq entry/exit events, just the
    > > > individual handler() calls.
    > >
    > > Then use the function_graph tracer.
    > >
    >
    > Sadly, the function tracer cannot be enabled on production systems.
    > Therefore it's not a usable solution in the context where I need this.

    And why not? It has zero overhead when disabled.

    -- Steve


    \
     
     \ /
      Last update: 2009-02-25 23:25    [W:0.019 / U:94.744 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site