Re: [PATCH -tip] Fastboot: fix initcalls disposition in bootgraph.pl

Frédéric Weisbecker wrote:
> 2008/10/6 Ingo Molnar <mingo <at> elte.hu>:
>> * Frédéric Weisbecker <fweisbec <at> gmail.com> wrote:
>>
>>> 2008/10/5 Ingo Molnar <mingo <at> elte.hu>:
>>>> Frédéric, is the revert still needed, or is latest tip/master OK ?
>>> Yes it should be reverted. Tracing is still stopped at the end of
>>> kernel_init().
>> lost track - exactly which commit ID should be reverted?
>>
>>        Ingo
>>
> 
> Hmm actually, the "stop_boot_trace" feature may be needed in  the
> future. If I trace the shed events too,
> I should be able to limit the tracing to avoid too much entries. I
> will see later.
> Perhaps just a patch to remove the trace stopping after builtin initcalls.
> I will submit it soon.
> 
> Sorry, just forget this revert request.
> 
> Thanks.
> 

From: Frederic Weisbecker <fweisbec <at> gmail.com>
Subject: [PATCH -tip] Tracing/fastboot: Revert the stopping of the boot tracer

Since the patch that stopped the tracing after builtin-initcalls wasn't
a real solution of a bootgraph.pl's bug, we may continue to trace boot
after builtin initcalls. But we want to keep the stop_boot_trace function
for further uses.

Signed-off-by: Frederic Weisbecker <fweisbec <at> gmail.com>
---
diff --git a/init/main.c b/init/main.c
index 6371981..f039e7a 100644
--- a/init/main.c
+++ b/init/main.c
@@ -975,7 +975,6 @@ static int __init kernel_init(void * unused)
 	 * we're essentially up and running. Get rid of the
 	 * initmem segments and start the user-mode stuff..
 	 */
-	stop_boot_trace();
 	init_post();
 	return 0;
 }