| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <c62985530810031059v5ed44e04qebaf9453710e76c1@mail.gmail.com> Date: Fri, 3 Oct 2008 19:59:08 +0200 From: "Frédéric Weisbecker" <fweisbec@...il.com> To: "Alan Jenkins" <aj504@...dent.cs.york.ac.uk> Cc: "Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org, "Arjan van de Ven" <arjan@...radead.org> Subject: Re: [PATCH -tip] Tracing/fastboot: Only trace non-module initcalls 2008/10/3 Alan Jenkins <aj504@...dent.cs.york.ac.uk>: > 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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists