Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936652Ab3DJK3x (ORCPT ); Wed, 10 Apr 2013 06:29:53 -0400 Received: from mail-ea0-f181.google.com ([209.85.215.181]:54679 "EHLO mail-ea0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753975Ab3DJK3w (ORCPT ); Wed, 10 Apr 2013 06:29:52 -0400 Date: Wed, 10 Apr 2013 12:29:48 +0200 From: Ingo Molnar To: Peter Zijlstra Cc: Frederic Weisbecker , 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 Subject: Re: [RFC GIT PULL] nohz: Full dynticks rq clock handling Message-ID: <20130410102948.GB28505@gmail.com> References: <1365266760-24725-1-git-send-email-fweisbec@gmail.com> <1365589603.30071.37.camel@laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1365589603.30071.37.camel@laptop> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 799 Lines: 23 * Peter Zijlstra wrote: > Another thing I just noticed; our update_curr() assumes its called at least once > every 4 odd seconds (2^32 ns like). > > update_curr() is 'required' for things like task runtime stats and everything > that hangs off of that like cputimers etc. > > Now I'm not entirely sure how the nr_running==1 nohz case deals with this, but I > can imagine it might take a while. In this case we might need to 'fix' > update_curr() to not asume the time delta fits in 32 bits. Good point ... Thanks, Ingo -- 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/