* [RFC patch 31/32] init: Move sched_clock_init after late_time_init
[not found] <20090821205008.518392436@linutronix.de>
@ 2009-08-21 21:32 ` Thomas Gleixner
0 siblings, 0 replies; only message in thread
From: Thomas Gleixner @ 2009-08-21 21:32 UTC (permalink / raw)
To: LKML
Cc: x86 team, Andrew Morton, Peter Zijlstra, Arjan van de Veen,
Avi Kivity, Jeremy Fitzhardinge, Rusty Russell, Alok N Kataria,
Pan Jacob jun, linux-arch
[-- Attachment #1: init-move-sched-clock-init-after-late-time-init.patch --]
[-- Type: text/plain, Size: 1264 bytes --]
Some architectures initialize clocks and timers in late_time_init and
x86 wants to do the same to avoid FIXMAP hackery for calibrating the
TSC. That would result in undefined sched_clock readout and wreckaged
printk timestamps again. We probably have those already on archs which
do all their time/clock setup in late_time_init.
There is no harm to move that after late_time_init except that a few
more boot timestamps are stale. The scheduler is not active at that
point so no real wreckage is expected.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-arch@vger.kernel.org
---
init/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/init/main.c
===================================================================
--- linux-2.6.orig/init/main.c
+++ linux-2.6/init/main.c
@@ -631,7 +631,6 @@ asmlinkage void __init start_kernel(void
softirq_init();
timekeeping_init();
time_init();
- sched_clock_init();
profile_init();
if (!irqs_disabled())
printk(KERN_CRIT "start_kernel(): bug: interrupts were "
@@ -682,6 +681,7 @@ asmlinkage void __init start_kernel(void
numa_policy_init();
if (late_time_init)
late_time_init();
+ sched_clock_init();
calibrate_delay();
pidmap_init();
anon_vma_init();
^ permalink raw reply [flat|nested] only message in thread