From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752773AbeCOSTG (ORCPT ); Thu, 15 Mar 2018 14:19:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:59100 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752238AbeCOSTE (ORCPT ); Thu, 15 Mar 2018 14:19:04 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3072B20779 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: Thu, 15 Mar 2018 19:19:00 +0100 From: Frederic Weisbecker To: "Rafael J. Wysocki" Cc: Peter Zijlstra , Linux PM , Frederic Weisbecker , Thomas Gleixner , Paul McKenney , Thomas Ilsche , Doug Smythies , Rik van Riel , Aubrey Li , Mike Galbraith , LKML Subject: Re: [RFT][PATCH v4 3/7] sched: idle: Do not stop the tick before cpuidle_idle_call() Message-ID: <20180315181858.GA14983@lerouge> References: <2352117.3UUoYAu18A@aspire.rjw.lan> <3550231.xNMJN5JcLx@aspire.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3550231.xNMJN5JcLx@aspire.rjw.lan> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 12, 2018 at 10:53:25AM +0100, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Make cpuidle_idle_call() decide whether or not to stop the tick. > > First, the cpuidle_enter_s2idle() path deals with the tick (and with > the entire timekeeping for that matter) by itself and it doesn't need > the tick to be stopped beforehand. Not sure you meant timekeeping either :) > if (idle_should_enter_s2idle() || dev->use_deepest_state) { > if (idle_should_enter_s2idle()) { > + rcu_idle_enter(); > + > entered_state = cpuidle_enter_s2idle(drv, dev); > if (entered_state > 0) { > local_irq_enable(); > goto exit_idle; > } > + > + rcu_idle_exit(); > } I'm not sure how the tick is stopped on suspend to idle. Perhaps through hrtimer (tick_cancel_sched_timer()) or clockevents code. But we may have a similar problem than with idle_poll() called right after call_cpuidle(). Ie: we arrive in cpuidle_enter_s2idle() with a tick that should be reprogrammed while it is not. No idea if that can hurt somehow. I guess it depends what happens to the tick on s2idle, I'm not clear with that.