From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161271AbcFQLxF (ORCPT ); Fri, 17 Jun 2016 07:53:05 -0400 Received: from www.linutronix.de ([62.245.132.108]:50256 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161210AbcFQLwy (ORCPT ); Fri, 17 Jun 2016 07:52:54 -0400 Date: Fri, 17 Jun 2016 13:50:50 +0200 (CEST) From: Thomas Gleixner To: Zhaoyang Huang cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, mingo@redhat.com, peterz@infradead.org, =?GB2312?Q?Zhaoyang_Huang_=28=BB=C6=B3=AF=D1=F4=29?= Subject: Re: [RESEND PATCH v2 2/2] power/idle: enhance the precision of sleep_length In-Reply-To: Message-ID: References: <1466154816-17900-1-git-send-email-zhaoyang.huang@spreadtrum.com> <1466154816-17900-2-git-send-email-zhaoyang.huang@spreadtrum.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 17 Jun 2016, Zhaoyang Huang wrote: > On 17 June 2016 at 17:27, Thomas Gleixner wrote: > > On Fri, 17 Jun 2016, Zhaoyang Huang wrote: > >> There should be a gap between tick_nohz_idle_enter and > >> tick_nohz_get_sleep_length when idle, which will cause the > >> sleep_length is not very precised. Change it in this patch. > > > > What kind of imprecision are we talking about? Seconds, nanoseconds or > > lightyears? > > > > Your changelog lacks any form of useful information. > > > sorry for the confusion. The imprecision can be caused by, for > example, the callback function registered for CPU_PM_ENTER, which may > consume a period of time within the 'idle' time. Besides, I also > wonder why not calc the 'sleep_length' in the > tick_nohz_get_sleep_length? This value is calculated at very > beginning of the idle in current approach. You still are not explaining the amount of imprecision. What are you talking about and is it really relevant in any way or are you just trying to solve an acedemic issue? Thanks, tglx