[lkml]   [2008]   [Dec]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [ltt-dev] trace a futex
    * Peter Zijlstra ( wrote:
    > FWIW, the ftrace infrastructure has on many an occasion (even before it
    > was called ftrace and specific to -rt) helped in debugging and fixing
    > futex races.

    Hrm, I'm not sure futex races is the key aspect of interest here.
    Knowing which amount of pthread mutex lock calls ends up calling the
    scheduler looks a bit more like the topic brought by this particular
    use-case. Therefore, correlating the information from the nptl with the
    kernel information would be useful.

    Is lockdep called when a futex is taken ? Should we add instrumentation
    (tracepoints) to futex.c ? If yes, was there specific instrumentation
    you used with ftrace that should be added ?


    Mathieu Desnoyers
    OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68

     \ /
      Last update: 2008-12-05 13:37    [W:0.019 / U:35.552 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site