[lkml]   [2006]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108

    Alan Cox wrote:
    > b has been done, its called kprobes. We just need better tools for the
    > dynamic probes.

    As long as there needs to be the updating of an outside piece of something
    then "b" hasn't been done. Especially with regards to what this means
    to figuring out which of kernel or instrumentation-script is broken when
    you get bug reports on lkml.

    > and you can maintain "Karim's probe list" which is the dynamic probe set
    > which matches your old static probes, only of course its now much more
    > flexible.

    Sorry, the issue isn't about my probe list. The issue is that there
    needs to be a way of pointing important events without having to
    modify things at 3 or 4 different places. The only way this can be
    done is if it's in the tree -- regardless of the mechanism. This
    isn't about static tracers vs. dynamic tracers, it's about statically
    marking code. What goes underneath is secondary. And if the static
    markup -- with even the SystemTap people are interested in -- is
    but a hook for further selecting the appropriate instrumentation
    mechanism, then that's fine too.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-09-15 17:17    [W:0.021 / U:18.752 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site