Re: perf report for .ko files

[Mike Galbraith]

On Fri, 2010-01-29 at 17:15 -0200, Arnaldo Carvalho de Melo wrote:

> I actually never tried doing annotation with a module, will try.

Seems it went south again in both .git and .tip.  32 works.

ed52ce2e3c33dc7626a40fa2da766d1a6460e543 is the first bad commit                             
commit ed52ce2e3c33dc7626a40fa2da766d1a6460e543                                              
Author: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>                                           
Date:   Mon Oct 19 17:17:57 2009 -0200                                                       

    perf tools: Add ->unmap_ip operation to struct map
                                                      
    We need this because we get section relative addresses when
    reading the symtabs, but when a tool like 'perf annotate' needs
    to match these address to what 'objdump -dS' produces we need
    the address + section back again.

    So in annotate now we look at the 'struct hist_entry' instances
    (that weren't really being used) so that we iterate only over
    the symbols that had some hit and get the map where that
    particular hit happened so that we can get the right address to
    match with annotate.

    Verified that at least:

     perf annotate mmap_read_counter # Uses the ~/bin/perf binary
     perf annotate --vmlinux /home/acme/git/build/perf/vmlinux intel_pmu_enable_all

    on a 'perf record perf top' session seems to work.

    Signed-off-by: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
    Cc: Frederic Weisbecker <fweisbec@xxxxxxxxx>
    Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
    Cc: Paul Mackerras <paulus@xxxxxxxxx>
    Cc: Mike Galbraith <efault@xxxxxx>
    LKML-Reference: <1255979877-12533-1-git-send-email-acme@xxxxxxxxxx>
    Signed-off-by: Ingo Molnar <mingo@xxxxxxx>


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/