From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Sargun Dhillon <sargun@sargun.me>,
Xie XiuQi <xiexiuqi@huawei.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
xiezhipeng1@huawei.com, huawei.libin@huawei.com,
linux-kernel <linux-kernel@vger.kernel.org>,
Dmitry Adamushko <dmitry.adamushko@gmail.com>,
Rik van Riel <riel@surriel.com>
Subject: Re: [PATCH] sched: fix infinity loop in update_blocked_averages
Date: Thu, 27 Dec 2018 18:02:43 -0800 [thread overview]
Message-ID: <20181228020243.GH2509588@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20181228015352.GG2509588@devbig004.ftw2.facebook.com>
On Thu, Dec 27, 2018 at 05:53:52PM -0800, Tejun Heo wrote:
> Vincent knows that part way better than me but I think the safest way
> would be doing the optimization removal iff tmp_alone_branch is
> already pointing to leaf_cfs_rq_list. IIUC, it's pointing to
> something else only while a branch is being built and deferring
> optimization removal by an avg update cycle isn't gonna make any
> difference anyway.
So, something like the following. Xie, can you see whether the
following patch resolves the problem?
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index d1907506318a..88b9118b5191 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -7698,7 +7698,8 @@ static void update_blocked_averages(int cpu)
* There can be a lot of idle CPU cgroups. Don't let fully
* decayed cfs_rqs linger on the list.
*/
- if (cfs_rq_is_decayed(cfs_rq))
+ if (cfs_rq_is_decayed(cfs_rq) &&
+ rq->tmp_alone_branch == &rq->leaf_cfs_rq_list)
list_del_leaf_cfs_rq(cfs_rq);
/* Don't need periodic decay once load/util_avg are null */
next prev parent reply other threads:[~2018-12-28 2:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 3:04 [PATCH] sched: fix infinity loop in update_blocked_averages Xie XiuQi
2018-12-27 9:21 ` Vincent Guittot
2018-12-27 10:21 ` Vincent Guittot
2018-12-27 10:23 ` Vincent Guittot
2018-12-27 16:39 ` Sargun Dhillon
2018-12-27 17:01 ` Vincent Guittot
2018-12-27 18:15 ` Linus Torvalds
2018-12-27 21:08 ` Sargun Dhillon
2018-12-27 21:46 ` Linus Torvalds
2018-12-28 1:15 ` Tejun Heo
2018-12-28 1:36 ` Linus Torvalds
2018-12-28 1:53 ` Tejun Heo
2018-12-28 2:02 ` Tejun Heo [this message]
2018-12-28 2:30 ` Xie XiuQi
2018-12-28 5:38 ` Sargun Dhillon
2018-12-28 9:30 ` Vincent Guittot
2018-12-28 14:26 ` Sargun Dhillon
2018-12-28 16:54 ` Tejun Heo
2018-12-28 17:25 ` Vincent Guittot
2018-12-28 17:46 ` Tejun Heo
2018-12-28 18:04 ` Vincent Guittot
2018-12-28 10:25 ` Xiezhipeng (EulerOS)
2018-12-30 12:04 ` Ingo Molnar
2018-12-30 12:31 ` [PATCH] sched: Fix infinite loop in update_blocked_averages() by reverting a9e7f6544b9c Ingo Molnar
2018-12-30 12:36 ` [PATCH] sched: fix infinity loop in update_blocked_averages Vincent Guittot
2018-12-30 12:54 ` Ingo Molnar
2018-12-30 13:00 ` [tip:sched/urgent] sched/fair: Fix infinite loop in update_blocked_averages() by reverting a9e7f6544b9c tip-bot for Linus Torvalds
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=20181228020243.GH2509588@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=dmitry.adamushko@gmail.com \
--cc=huawei.libin@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=sargun@sargun.me \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--cc=xiexiuqi@huawei.com \
--cc=xiezhipeng1@huawei.com \
/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