From: tip-bot for Vincent Guittot <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, hpa@zytor.com, paulmck@linux.vnet.ibm.com,
hkallweit1@gmail.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, geert+renesas@glider.be,
vincent.guittot@linaro.org, peterz@infradead.org,
torvalds@linux-foundation.org
Subject: [tip:sched/urgent] sched/fair: Fix the update of blocked load when newly idle
Date: Thu, 3 May 2018 02:25:28 -0700 [thread overview]
Message-ID: <tip-457be908c83637ee10bda085a23dc05afa3b14a0@git.kernel.org> (raw)
In-Reply-To: <20180426103133.GA6953@linaro.org>
Commit-ID: 457be908c83637ee10bda085a23dc05afa3b14a0
Gitweb: https://git.kernel.org/tip/457be908c83637ee10bda085a23dc05afa3b14a0
Author: Vincent Guittot <vincent.guittot@linaro.org>
AuthorDate: Thu, 26 Apr 2018 12:19:32 +0200
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Thu, 3 May 2018 07:38:03 +0200
sched/fair: Fix the update of blocked load when newly idle
With commit:
31e77c93e432 ("sched/fair: Update blocked load when newly idle")
... we release the rq->lock when updating blocked load of idle CPUs.
This opens a time window during which another CPU can add a task to this
CPU's cfs_rq.
The check for newly added task of idle_balance() is not in the common path.
Move the out label to include this check.
Reported-by: Heiner Kallweit <hkallweit1@gmail.com>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Fixes: 31e77c93e432 ("sched/fair: Update blocked load when newly idle")
Link: http://lkml.kernel.org/r/20180426103133.GA6953@linaro.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/sched/fair.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 54dc31e7ab9b..e3002e5ada31 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -9847,6 +9847,7 @@ static int idle_balance(struct rq *this_rq, struct rq_flags *rf)
if (curr_cost > this_rq->max_idle_balance_cost)
this_rq->max_idle_balance_cost = curr_cost;
+out:
/*
* While browsing the domains, we released the rq lock, a task could
* have been enqueued in the meantime. Since we're not going idle,
@@ -9855,7 +9856,6 @@ static int idle_balance(struct rq *this_rq, struct rq_flags *rf)
if (this_rq->cfs.h_nr_running && !pulled_task)
pulled_task = 1;
-out:
/* Move the next balance forward */
if (time_after(this_rq->next_balance, next_balance))
this_rq->next_balance = next_balance;
next prev parent reply other threads:[~2018-05-03 9:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 9:18 Potential problem with 31e77c93e432dec7 ("sched/fair: Update blocked load when newly idle") Niklas Söderlund
2018-04-12 10:33 ` Vincent Guittot
2018-04-12 11:15 ` Niklas Söderlund
[not found] ` <20180412133031.GA551@linaro.org>
2018-04-12 19:43 ` Heiner Kallweit
2018-04-14 11:21 ` Vincent Guittot
2018-04-12 22:39 ` Niklas Söderlund
2018-04-14 11:24 ` Vincent Guittot
2018-04-20 16:00 ` Vincent Guittot
2018-04-20 16:30 ` Joel Fernandes
2018-04-22 22:18 ` Niklas Söderlund
2018-04-23 9:54 ` Vincent Guittot
[not found] ` <20180425225603.GA26177@bigcity.dyn.berto.se>
2018-04-26 10:31 ` Vincent Guittot
2018-04-26 11:48 ` Peter Zijlstra
2018-04-26 14:41 ` Niklas Söderlund
2018-04-26 15:27 ` Vincent Guittot
2018-04-26 15:38 ` Niklas Söderlund
2018-05-02 13:40 ` Geert Uytterhoeven
2018-05-03 9:25 ` tip-bot for Vincent Guittot [this message]
2018-04-13 20:38 ` Niklas Söderlund
2018-04-14 11:26 ` Vincent Guittot
2018-04-12 22:06 ` Niklas Söderlund
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=tip-457be908c83637ee10bda085a23dc05afa3b14a0@git.kernel.org \
--to=tipbot@zytor.com \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.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).