[<prev] [next>] [day] [month] [year] [list]
Message-ID: <48EA02A1.9030800@gmail.com>
Date: Mon, 06 Oct 2008 14:20:49 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Ingo Molnar <mingo@...e.hu>
CC: linux-kernel@...r.kernel.org,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH -tip] Fastboot: fix initcalls disposition in bootgraph.pl
Frédéric Weisbecker wrote:
> 2008/10/6 Ingo Molnar <mingo@...e.hu>:
>> * Frédéric Weisbecker <fweisbec@...il.com> wrote:
>>
>>> 2008/10/5 Ingo Molnar <mingo@...e.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@...il.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@...il.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;
}
--
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