On Tue, May 06, 2014 at 02:50:57PM -0500, miny...@acm.org wrote:
> From: Corey Minyard <cminy...@mvista.com>
> 
> If the sched_clock time starts at a large value, the kernel will spin
> in sched_avg_update for a long time while rq->age_stamp catches up
> with rq->clock.
> 
> The comment in kernel/sched/clock.c says that there is no strict promise
> that it starts at zero.  So initialize rq->age_stamp when a cpu starts up
> to avoid this.
> 
> I was seeing long delays on a simulator that didn't start the clock at
> zero.  This might also be an issue on reboots on processors that don't
> re-initialize the timer to zero on reset, and when using kexec.
> 
> Signed-off-by: Corey Minyard <cminy...@mvista.com>

This patch made my cris-defconfig build fail.

Attachment: pgpH9sT0R_Hfz.pgp
Description: PGP signature

Reply via email to