[lkml]   [2010]   [Jul]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 1/6] vmscan: tracing: Roll up of patches currently in mmotm
    On Fri, Jul 30, 2010 at 04:04:42PM +0200, Frederic Weisbecker wrote:
    > On Fri, Jul 30, 2010 at 02:36:55PM +0100, Mel Gorman wrote:
    > > This is a roll-up of patches currently in mmotm related to stack reduction and
    > > tracing reclaim. It is based on 2.6.35-rc6 and included for the convenience
    > > of testing.
    > >
    > > No signed off required.
    > > ---
    > > .../trace/postprocess/ | 654 ++++++++++++++++++++
    > I have the feeling you've made an ad-hoc post processing script that seems
    > to rewrite all the format parsing, debugfs, stream handling, etc... we
    > have that in perf tools already.

    It's an hoc adaption of which was developed
    before the perf scripting report. It's a bit klunky.

    > May be you weren't aware of what we have in perf in terms of scripting support.

    I'm aware, I just haven't gotten around to adapting what the script does
    to the perf scripting support. The existance of the script I have means
    people can reproduce my results without having to wait for me to rewrite
    the post-processing scripts for perf.

    > First, launch perf list and spot the events you're interested in, let's
    > say you're interested in irqs:
    > $ perf list
    > [...]
    > irq:irq_handler_entry [Tracepoint event]
    > irq:irq_handler_exit [Tracepoint event]
    > irq:softirq_entry [Tracepoint event]
    > irq:softirq_exit [Tracepoint event]
    > [...]
    > Now do a trace record:
    > # perf record -e irq:irq_handler_entry -e irq:irq_handler_exit -e irq:softirq_entry -e irq:softirq_exit cmd
    > or more simple:
    > # perf record -e irq:* cmd
    > You can use -a instead of cmd for wide tracing.
    > Now generate a perf parsing script on top of these traces:
    > # perf trace -g perl
    > generated Perl script:
    > Fill up the trace handlers inside and just run it:
    > # perf trace -s
    > Once ready, you can place your script in the script directory.

    Ultimately, the post-processing scripts should be adapted to perf but it
    could be a while before I get around to it.

    Mel Gorman
    Part-time Phd Student Linux Technology Center
    University of Limerick IBM Dublin Software Lab

     \ /
      Last update: 2010-07-30 16:15    [W:0.030 / U:9.416 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site