lkml.org 
[lkml]   [2008]   [Dec]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 0/3] tracing/function-graph-tracer: signal interrupt triggering on output
    2008/12/10 Steven Rostedt <rostedt@goodmis.org>:
    >
    > On Tue, 9 Dec 2008, Frederic Weisbecker wrote:
    >
    >> This patchset adds all the features to draw hardirq triggering on output
    >> for the function graph tracer.
    >> An example is given on the third patch.
    >>
    >> Just one question, on recordmcount.pl:
    >>
    >> my %text_sections = (
    >> ".text" => 1,
    >> ".sched.text" => 1,
    >> ".spinlock.text" => 1,
    >>
    >> The .sched.text section is included inside .text, it's a subsection, I'm not sure
    >> it's necessary to add it in text_sections. In doubt I added the new .irqentry.text
    >>
    >
    > Matters what objdump -dr shows.
    >
    > $ objdump -dr kernel/sched.o | grep 'Disassembly'
    > Disassembly of section .text:
    > Disassembly of section .cpuinit.text:
    > Disassembly of section .init.text:
    > Disassembly of section .sched.text:
    >
    > Yep, .sched.text is needed. It is not about what gets linked by the
    > linker. It is about what objdump shows, which is what recordmcount.pl uses
    > to determine whether or not to record the mcount callers in that section.


    Ok. I looked at a disassembly objdump on vmlinux to find those
    subsections and didn't find it.
    But I didn't see that recordmcount did its work on each build folder,
    I guess that these sections are
    visible on the objects found in the subdirectories....

    Thanks.


    \
     
     \ /
      Last update: 2008-12-10 09:49    [W:0.024 / U:0.040 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site