Messages in this thread | | | Date | Sat, 4 Oct 2008 21:05:05 +0200 | From | "Frédéric Weisbecker" <> | Subject | Re: [PATCH -tip] Tracing/fastboot: Only trace non-module initcalls |
| |
2008/10/3 Alan Jenkins <alan-jenkins@tuffmail.co.uk>: > If you want to disable non-module initcalls, then what do you have left > that you want to trace after "Freeing unused kernel memory"? > > On my desktop dmesg I can see that the initramfs is loaded and started > some time before the initcalls finish. The initramfs includes udev > which loads many modules; I see network, usb, sata being initialised > before the "Freeing unused kernel memory" message. Um... your changes > will _not_ stop the initcalls from these modules being shown. > > So I think your patch description is a bit inaccurate, and I don't > understand what you are trying to achieve.
Hmm I'm beginning to understand what you say. Actually I didn't think about initramfs that could launch modules initcalls early. It seems that modules initcalls are launched with the builtin initcalls when one use initramfs. Since I'm not using it, I see only the builtin initcalls before the message of memory freeing.
I missed that point. And actually I misunderstood the real problem. My issues with the graph happened because of a bug in the bootgraph.pl script. I have a patch ready that corrects it. I'm going to post it and explain the real problem.
Thanks Alan!
| |