[lkml]   [2010]   [Nov]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [ANNOUNCE] New utility: 'trace'
    On Tue, Nov 16, 2010 at 08:47:40PM -0500, Steven Rostedt wrote:
    > Note, I just posted an RFC stable event patch set. I would like any tool
    > that does general analysis, to use stable events and not random raw
    > events created by the perspective maintainers.
    > The tool could tap into the raw events, but I don't like the "trace
    > check" I think anything that the trace needs should be guaranteed there
    > (with the stable tracepoints).
    > The tracepoints used for general analysis should be stable, anything
    > else is just shear bonus.

    Which is fine with me, so long as it is accepted that the 'trace' tool
    is not targetted at kernel developers (who would probably like to use
    a combination of stable and unstable tracepoints).

    Do we all agree on what the intended target audience is for this
    'trace' tool?

    My one concern of having a tool that doesn't support the unstable
    tracepoints is that if the kernel developers aren't using it for their
    day-to-day use, it won't get attention/love, and it risks the fate of
    'systemtap' --- ignored by kernel developers and treated as if it
    doesn't exist.

    Maybe the answer is there's a #ifdef, and there's one version of the
    tool that is intended for use by kernel developers, and one which is
    restricted to the stable interface that we give to the hoi polloi?

    - Ted

     \ /
      Last update: 2010-11-17 04:19    [W:0.020 / U:11.248 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site