From: Vincent Guittot <vincent.guittot@linaro.org>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Heiner Kallweit" <hkallweit1@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: Potential problem with 31e77c93e432dec7 ("sched/fair: Update blocked load when newly idle")
Date: Thu, 26 Apr 2018 12:31:33 +0200 [thread overview]
Message-ID: <20180426103133.GA6953@linaro.org> (raw)
In-Reply-To: <20180425225603.GA26177@bigcity.dyn.berto.se>
Hi Niklas,
Le Thursday 26 Apr 2018 à 00:56:03 (+0200), Niklas Söderlund a écrit :
> Hi Vincent,
>
> Here are the result, sorry for the delay.
>
> On 2018-04-23 11:54:20 +0200, Vincent Guittot wrote:
>
> [snip]
>
> >
> > Thanks for the report. Can you re run with the following trace-cmd sequence ? My previous sequence disables ftrace events
> >
> > trace-cmd reset > /dev/null
> > trace-cmd start -b 40000 -p function -l dump_backtrace:traceoff -e sched -e cpu_idle -e cpu_frequency -e timer -e ipi -e irq -e printk
> > trace-cmd start -b 40000 -p function -l dump_backtrace -e sched -e cpu_idle -e cpu_frequency -e timer -e ipi -e irq -e printk
> >
> > I have updated the patch and added traces to check that scheduler returns from idle_balance function and doesn't stay stuck
>
> Once more I applied the change bellow on-top of c18bb396d3d261eb ("Merge
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net").
>
> This time the result of 'trace-cmd report' is so large I do not include
> it here, but I attach the trace.dat file. Not sure why but the timing of
> sending the NMI to the backtrace print is different (but content the
> same AFIK) so in the odd change it can help figure this out:
>
Thanks for the trace, I have been able to catch a problem with it.
Could you test the patch below to confirm that the problem is solved ?
The patch apply on-top of
c18bb396d3d261eb ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net")
From: Vincent Guittot <vincent.guittot@linaro.org>
Date: Thu, 26 Apr 2018 12:19:32 +0200
Subject: [PATCH] sched/fair: fix the update of blocked load when newly idle
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
With commit 31e77c93e432 ("sched/fair: Update blocked load when newly idle"),
we release the rq->lock when updating blocked load of idle CPUs. This open
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.
Fixes: 31e77c93e432 ("sched/fair: Update blocked load when newly idle")
Reported-by: Heiner Kallweit <hkallweit1@gmail.com>
Reported-by: Niklas Söderlund <niklas.soderlund@ragnatech.se>
Signed-off-by: Vincent Guittot <vincent.guittot@linaro.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 0951d1c..15a9f5e 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;
--
2.7.4
[snip]
next prev parent reply other threads:[~2018-04-26 10:31 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 [this message]
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:sched/urgent] sched/fair: Fix the update of blocked load when newly idle tip-bot for Vincent Guittot
2018-04-13 20:38 ` Potential problem with 31e77c93e432dec7 ("sched/fair: Update blocked load when newly idle") 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=20180426103133.GA6953@linaro.org \
--to=vincent.guittot@linaro.org \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=paulmck@linux.vnet.ibm.com \
--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).