lkml.org 
[lkml]   [2009]   [Jun]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] tracing/fastboot: document the need of initcall_debug
    On Mon, Jun 29, 2009 at 11:14:22AM +0200, Ingo Molnar wrote:
    >
    > * Li Zefan <lizf@cn.fujitsu.com> wrote:
    >
    > > Ingo Molnar wrote:
    > > > * Li Zefan <lizf@cn.fujitsu.com> wrote:
    > > >
    > > >> To use boot tracer, one should pass initcall_debug as well as
    > > >> ftrace=initcall to the command line.
    > > >
    > > > I think both should be auto-enabled if BOOT_TRACER is enabled, for
    > > > ease of use - agreed?
    > >
    > > If both are auto-enabled, we'll always do boot tracing. But we
    > > want BOOT_TRACER to be enabled and only enable boot tracing when
    > > it's needed.
    > >
    > > But maybe we can make ftrace=initcall implies initcall_debug=1?
    >
    > That's reasonable indeed.
    >
    > Ingo

    Yeah.

    Although I wonder if this tracer is still useful.
    It was first written to debug fastboot, to get more
    than the initcall_debug output, ie: the scheduling
    events but now I guess the latter is not useful
    anymore. And using initcall_debug already does the
    job of printing the initcall events.

    What do you think?



    \
     
     \ /
      Last update: 2009-06-29 13:21    [W:0.020 / U:31.376 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site