Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760023Ab3DINL6 (ORCPT ); Tue, 9 Apr 2013 09:11:58 -0400 Received: from mail-bk0-f42.google.com ([209.85.214.42]:44042 "EHLO mail-bk0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759009Ab3DINL5 (ORCPT ); Tue, 9 Apr 2013 09:11:57 -0400 MIME-Version: 1.0 In-Reply-To: <1365498784.2609.165.camel@laptop> References: <1365266760-24725-1-git-send-email-fweisbec@gmail.com> <1365266760-24725-2-git-send-email-fweisbec@gmail.com> <1365498784.2609.165.camel@laptop> Date: Tue, 9 Apr 2013 15:11:56 +0200 Message-ID: Subject: Re: [PATCH 1/7] sched: Update rq clock on nohz CPU before migrating tasks From: Frederic Weisbecker To: Peter Zijlstra Cc: Ingo Molnar , LKML , Alessio Igor Bogani , Andrew Morton , Chris Metcalf , Christoph Lameter , Geoff Levand , Gilad Ben Yossef , Hakan Akkan , Li Zhong , Namhyung Kim , "Paul E. McKenney" , Paul Gortmaker , Steven Rostedt , Thomas Gleixner , Paul Turner , Mike Galbraith Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 928 Lines: 22 2013/4/9 Peter Zijlstra : > On Sat, 2013-04-06 at 18:45 +0200, Frederic Weisbecker wrote: >> Because the sched_class::put_prev_task() callback of rt and fair >> classes are referring to the rq clock to update their runtime >> statistics. A CPU running in tickless mode may carry a stale value. >> We need to update it there. > > I'm failing to see how tickless makes a difference here.. we should > never rely on a ->clock set at the last tick, that's wrong. Ah I made that big mis-assumption then ;) > > So either explain which/how clock update gets lost by tickless or make > it unconditional. So most of those fixup need to be made unconditional I think. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/