Received: by 10.213.65.68 with SMTP id h4csp210881imn; Fri, 6 Apr 2018 19:44:58 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/rTLEPN/qcEUqtdLRyeOj/A7QUuHsr79VkbvJEi6OFPQz2wZeZLvQIOA/3KMKOwER52NUk X-Received: by 10.99.181.13 with SMTP id y13mr18999712pge.279.1523069098663; Fri, 06 Apr 2018 19:44:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523069098; cv=none; d=google.com; s=arc-20160816; b=BGCS81AhdpcQptGz8fSVI8rTifiJbbj0c4dJGXzqs+0xynRR4vBLQGHW9s1WsGUBTs cALcDv6wdI/a2uDP+guPWhdbyjyhDX6CNlo02KC2rOH7Wr8ah9Z14s8i0QRqqEinCKvd Pz+0nLNN3ePiF+EOfl1tF2K2qF8DWex4jSZDHNa5rrwJKZxjPNe2mTPxwjK5ISJHSQRN ZmBxIzH2R13nfcH26cRMuodGe5DakEQXQ98YecSqOGkRV1xHZ7VPPR/x3BtpfmvmJrr7 A0ngdw64Q0+JwMFdQC2SEw3Bi/nJIrvGLilqRsW51Hhc3nQKrNhFTYv/ipl0degN3pcr IeUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dmarc-filter:arc-authentication-results; bh=pu8R1NLCGXregkExUEk7RhV06lDgVNcyuzysJBAqU6s=; b=s5pkKnQruhCP2d+ND17Xc1Ck002aktvbuEYcx95+akEIUcNArbZXDxtKpLi1Z0gGUJ HGPo2usLsYB4hqGLogntegE6Eg15M+c1I2KNLnt1y2X+hbxesCMbmIv4Osre5T7aAFTA 1PomcDI0jfBg0s81uxEZHZB2WGl1ZvLxdiHKnRvpwIOB1P7vYfNor15H0ZH4tyHxs2Sm yslUliUb+KJR7HsB0mLZehu0sH1mCeIvMqbTHf5N+anK8KYeinNLvqZZRUfWaRF2cYWb Ns8EWTxUKajpCXDbflifXG2yYMjbzzKTY4uCt46sg0aX80Qs+qsTVpD+vxynrbZ+s3nb NOCA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n86si9005165pfa.381.2018.04.06.19.44.21; Fri, 06 Apr 2018 19:44:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751807AbeDGCgc (ORCPT + 99 others); Fri, 6 Apr 2018 22:36:32 -0400 Received: from mail.kernel.org ([198.145.29.99]:53042 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751425AbeDGCga (ORCPT ); Fri, 6 Apr 2018 22:36:30 -0400 Received: from localhost (LFbn-NCY-1-193-82.w83-194.abo.wanadoo.fr [83.194.41.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 0E18E20652; Sat, 7 Apr 2018 02:36:28 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0E18E20652 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=frederic@kernel.org Date: Sat, 7 Apr 2018 04:36:25 +0200 From: Frederic Weisbecker To: "Rafael J. Wysocki" Cc: Linux PM , Peter Zijlstra , Frederic Weisbecker , Thomas Gleixner , Paul McKenney , Thomas Ilsche , Doug Smythies , Rik van Riel , Aubrey Li , Mike Galbraith , LKML , Len Brown Subject: Re: [PATCH v9 06/10] time: tick-sched: Split tick_nohz_stop_sched_tick() Message-ID: <20180407023623.GA16600@lerouge> References: <1736751.LdhZHb50jq@aspire.rjw.lan> <4511679.r9V9QramI4@aspire.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4511679.r9V9QramI4@aspire.rjw.lan> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 04, 2018 at 10:41:13AM +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > In order to address the issue with short idle duration predictions > by the idle governor after the scheduler tick has been stopped, split > tick_nohz_stop_sched_tick() into two separate routines, one computing > the time to the next timer event and the other simply stopping the > tick when the time to the next timer event is known. > > Prepare these two routines to be called separately, as one of them > will be called by the idle governor in the cpuidle_select() code > path after subsequent changes. > > Update the former callers of tick_nohz_stop_sched_tick() to use > the new routines, tick_nohz_next_event() and tick_nohz_stop_tick(), > instead of it and move the updates of the sleep_length field in > struct tick_sched into __tick_nohz_idle_stop_tick() as it doesn't > need to be updated anywhere else. > > There should be no intentional visible changes in functionality > resulting from this change. > > Signed-off-by: Rafael J. Wysocki Reviewed-by: Frederic Weisbecker Thanks! And sorry for the slow reviews, the changes are sensitive and I want to make sure we are not breaking some subtlety.