From 6370716bc33928f91d75ecb5173986c79dedb111 Mon Sep 17 00:00:00 2001 From: Steve Muckle Date: Thu, 13 Nov 2014 18:06:59 -0800 Subject: sched: do not set window until sched_clock is fully initialized The system initially uses a jiffy-based sched clock. When the platform registers a new timer for sched_clock, sched_clock can jump backwards. Once sched_clock_postinit() runs it should be safe to rely on it. Also sched_clock_cpu() relies on completion of sched_clock_init() and until that happens sched_clock_cpu() returns zero. This is used in the irq accounting path which window-based stats relies upon. So do not set window_start until sched_clock_cpu() is working. Change-Id: Ided349de8f8554f80a027ace0f63ea52b1c38c68 Signed-off-by: Steve Muckle --- include/linux/sched.h | 1 + 1 file changed, 1 insertion(+) (limited to 'include/linux') diff --git a/include/linux/sched.h b/include/linux/sched.h index fd4d79416cdc..5398a8aea026 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -2381,6 +2381,7 @@ extern u64 sched_clock_cpu(int cpu); extern void sched_clock_init(void); +extern int sched_clock_initialized(void); #ifndef CONFIG_HAVE_UNSTABLE_SCHED_CLOCK static inline void sched_clock_tick(void) -- cgit v1.2.3