Thomas Gleixner fa84e9eecf init: Move sched_clock_init after late_time_init ... 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> LKML-Reference: <new-submission> Cc: linux-arch@vger.kernel.org		2009-08-27 16:38:18 +02:00
..
calibrate.c
do_mounts_initrd.c
do_mounts_md.c
do_mounts_rd.c
do_mounts.c
do_mounts.h
initramfs.c
Kconfig	perf_counter: Set the CONFIG_PERF_COUNTERS default to y if CONFIG_PROFILING=y	2009-08-04 18:19:30 +02:00
main.c	init: Move sched_clock_init after late_time_init	2009-08-27 16:38:18 +02:00
Makefile
noinitramfs.c
version.c