android_kernel_xiaomi_sm8350/init
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 fs: fix do_mount_root() false positive kmemcheck warning 2009-06-15 15:49:42 +02:00
do_mounts.h
initramfs.c initramfs: clean up messages related to initramfs unpacking 2009-05-06 16:36:10 -07:00
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