Re: [PATCH -tip] Tracing/fastboot: Only trace non-module initcalls

[Frédéric Weisbecker]

2008/10/3 Alan Jenkins <aj504@xxxxxxxxxxxxxxxxxxxxx>:
> Sorry to butt in.  I think tracing module initcalls was a deliberate addition by Arjan (a06e1c2b448b317bc141934879cbbbed8319b4d4).
>
> Maybe you use an initrd and that affects the trace?  It would be nice to see the "before" svg as well as the "after", to explain the change.
>
> Thanks
> Alan


Hi Alan,

The script bootgraph.pl in -tip stops the analyzing when it sees
"Freeing unused kernel memory". That's
exactly when the built-in initcalls are finished.
And as a result, the graph produced with dmesg always finishes at this point.

If you try to generate a graph whithout this limitation, you will not
be able to see something interesting because
the script will not find a lot of initcalls with a long enough time
proportion against the total boot time.
Perhaps it can be improved in that way but unfortunately I don't know
any word in Perl....
--
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/