From: Odin Ugedal <odin@uged.al>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Sachin Sant <sachinp@linux.vnet.ibm.com>,
Odin Ugedal <odin@uged.al>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [powerpc][next-20210621] WARNING at kernel/sched/fair.c:3277 during boot
Date: Wed, 23 Jun 2021 14:18:16 +0200 [thread overview]
Message-ID: <CAFpoUr01xb9ZJF9mb2nmZDpUHXFH3VSbY3AU8-1owV-_7wVTPg@mail.gmail.com> (raw)
In-Reply-To: <20210623120835.GB29143@vingu-book>
Hi,
Wouldn't the attached diff below also help when load is removed,
Vincent? Isn't there a theoretical chance that x_sum ends up at zero
while x_load ends up as a positive value (without this patch)? Can
post as a separate patch if it works for Sachin.
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index bfaa6e1f6067..def48bc2e90b 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -3688,15 +3688,15 @@ update_cfs_rq_load_avg(u64 now, struct cfs_rq *cfs_rq)
r = removed_load;
sub_positive(&sa->load_avg, r);
- sub_positive(&sa->load_sum, r * divider);
+ sa->load_sum = sa->load_avg * divider;
r = removed_util;
sub_positive(&sa->util_avg, r);
- sub_positive(&sa->util_sum, r * divider);
+ sa->util_sum = sa->util_avg * divider;
r = removed_runnable;
sub_positive(&sa->runnable_avg, r);
- sub_positive(&sa->runnable_sum, r * divider);
+ sa->runnable_sum = sa->runnable_avg * divider;
/*
* removed_runnable is the unweighted version of
removed_load so we
next prev parent reply other threads:[~2021-06-23 12:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 7:39 [powerpc][next-20210621] WARNING at kernel/sched/fair.c:3277 during boot Sachin Sant
2021-06-22 7:49 ` Vincent Guittot
2021-06-22 14:31 ` Vincent Guittot
2021-06-22 15:59 ` Sachin Sant
2021-06-23 7:19 ` Vincent Guittot
2021-06-23 7:58 ` Sachin Sant
2021-06-23 10:22 ` Sachin Sant
2021-06-23 12:08 ` Vincent Guittot
2021-06-23 12:18 ` Odin Ugedal [this message]
2021-06-23 12:22 ` Vincent Guittot
2021-06-23 12:37 ` Odin Ugedal
2021-06-23 13:55 ` Vincent Guittot
2021-06-23 15:13 ` Odin Ugedal
2021-06-23 15:25 ` Vincent Guittot
2021-06-23 16:45 ` Sachin Sant
2021-06-23 16:55 ` Vincent Guittot
2021-06-23 17:27 ` Vincent Guittot
2021-06-23 17:37 ` Odin Ugedal
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=CAFpoUr01xb9ZJF9mb2nmZDpUHXFH3VSbY3AU8-1owV-_7wVTPg@mail.gmail.com \
--to=odin@uged.al \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.vnet.ibm.com \
--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).