From: Peter Zijlstra Date: Thu, 19 Aug 2010 11:31:43 +0000 (+0200) Subject: sched: Fix rq->clock synchronization when migrating tasks X-Git-Tag: firefly_0821_release~10186^2~953 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=6c55d19c1d235c267b151d1d6e55a9d6fd5b5161;p=firefly-linux-kernel-4.4.55.git sched: Fix rq->clock synchronization when migrating tasks commit 861d034ee814917a83bd5de4b26e3b8336ddeeb8 upstream sched_fork() -- we do task placement in ->task_fork_fair() ensure we update_rq_clock() so we work with current time. We leave the vruntime in relative state, so the time delay until wake_up_new_task() doesn't matter. wake_up_new_task() -- Since task_fork_fair() left p->vruntime in relative state we can safely migrate, the activate_task() on the remote rq will call update_rq_clock() and causes the clock to be synced (enough). Tested-by: Jack Daniel Tested-by: Philby John Signed-off-by: Peter Zijlstra LKML-Reference: <1281002322.1923.1708.camel@laptop> Signed-off-by: Ingo Molnar Signed-off-by: Mike Galbraith Signed-off-by: Greg Kroah-Hartman --- diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c index ee89be8571b1..be3450816f9e 100644 --- a/kernel/sched_fair.c +++ b/kernel/sched_fair.c @@ -1963,6 +1963,8 @@ static void task_fork_fair(struct task_struct *p) spin_lock_irqsave(&rq->lock, flags); + update_rq_clock(rq); + if (unlikely(task_cpu(p) != this_cpu)) __set_task_cpu(p, this_cpu);