From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Ingo Molnar <mingo@kernel.org>, Leo Yan <leo.yan@linaro.org>
Subject: [PATCH] sched: idle: Avoid retaining the tick when it has been stopped
Date: Thu, 09 Aug 2018 19:08:34 +0200 [thread overview]
Message-ID: <2161372.IsD4PDzmmY@aspire.rjw.lan> (raw)
From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
If the tick has been stopped already, but the governor has not asked to
stop it (which it can do sometimes), the idle loop should invoke
tick_nohz_idle_stop_tick(), to let tick_nohz_stop_tick() take care
of this case properly.
Fixes: 554c8aa8ecad (sched: idle: Select idle state before stopping the tick)
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
kernel/sched/idle.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-pm/kernel/sched/idle.c
===================================================================
--- linux-pm.orig/kernel/sched/idle.c
+++ linux-pm/kernel/sched/idle.c
@@ -190,7 +190,7 @@ static void cpuidle_idle_call(void)
*/
next_state = cpuidle_select(drv, dev, &stop_tick);
- if (stop_tick)
+ if (stop_tick || tick_nohz_tick_stopped())
tick_nohz_idle_stop_tick();
else
tick_nohz_idle_retain_tick();
next reply other threads:[~2018-08-09 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 17:08 Rafael J. Wysocki [this message]
2018-08-10 6:19 ` [PATCH] sched: idle: Avoid retaining the tick when it has been stopped leo.yan
2018-08-10 7:15 ` Rafael J. Wysocki
2018-08-16 13:27 ` Frederic Weisbecker
2018-08-17 9:32 ` Rafael J. Wysocki
2018-08-17 10:05 ` Rafael J. Wysocki
2018-08-17 14:12 ` Frederic Weisbecker
2018-08-18 21:57 ` Rafael J. Wysocki
2018-08-19 0:36 ` leo.yan
2018-08-19 7:57 ` Rafael J. Wysocki
2018-08-20 9:14 ` Peter Zijlstra
2018-08-20 14:42 ` Frederic Weisbecker
2018-08-20 21:21 ` Rafael J. Wysocki
2018-08-21 23:21 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2161372.IsD4PDzmmY@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=frederic@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).