From: Frederic Weisbecker <fweisbec@gmail.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Wanpeng Li <wanpeng.li@hotmail.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@arm.com>, Luca Abeni <luca.abeni@unitn.it>
Subject: Re: [PATCH] sched: fix the intention to re-evalute tick dependency for offline cpu
Date: Wed, 10 Aug 2016 14:43:09 +0200 [thread overview]
Message-ID: <20160810124308.GA19757@lerouge> (raw)
In-Reply-To: <1470304280-3917-1-git-send-email-wanpeng.li@hotmail.com>
On Thu, Aug 04, 2016 at 05:51:20PM +0800, Wanpeng Li wrote:
> From: Wanpeng Li <wanpeng.li@hotmail.com>
>
> The dl task will be replenished after dl task timer fire and start a new
> period. It will be enqueued and to re-evaluate its dependency on the tick
> in order to restart it. However, if cpu is hot-unplug, irq_work_queue will
> splash since the target cpu is offline.
>
> As a result:
>
> WARNING: CPU: 2 PID: 0 at kernel/irq_work.c:69 irq_work_queue_on+0xad/0xe0
> Call Trace:
> dump_stack+0x99/0xd0
> __warn+0xd1/0xf0
> warn_slowpath_null+0x1d/0x20
> irq_work_queue_on+0xad/0xe0
> tick_nohz_full_kick_cpu+0x44/0x50
> tick_nohz_dep_set_cpu+0x74/0xb0
> enqueue_task_dl+0x226/0x480
> activate_task+0x5c/0xa0
> dl_task_timer+0x19b/0x2c0
> ? push_dl_task.part.31+0x190/0x190
>
> This can be triggered by hot-unplug the full dynticks cpu which dl task
> is running on.
>
> Actually we don't need to restart the tick since the target cpu is offline
> and nothing need scheduler tick. This patch fix it by not intend to re-evaluate
> tick dependency if the cpu is offline.
>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Juri Lelli <juri.lelli@arm.com>
> Cc: Luca Abeni <luca.abeni@unitn.it>
> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com>
> ---
> kernel/sched/core.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 7f2cae4..43b494f 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -628,6 +628,9 @@ bool sched_can_stop_tick(struct rq *rq)
> {
> int fifo_nr_running;
>
> + if (unlikely(!rq->online))
> + return true;
> +
I see, the CPU is offline but the tasks haven't been migrated yet.
That said it seems that rollback is still possible at this stage.
Somehow we may need to deal with it.
Thanks.
> /* Deadline tasks, even if single, need the tick */
> if (rq->dl.dl_nr_running)
> return false;
> --
> 1.9.1
>
next prev parent reply other threads:[~2016-08-10 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 9:51 [PATCH] sched: fix the intention to re-evalute tick dependency for offline cpu Wanpeng Li
2016-08-05 5:36 ` Wanpeng Li
2016-08-10 12:43 ` Frederic Weisbecker [this message]
2016-08-10 13:23 ` Wanpeng Li
2016-08-10 18:53 ` Frederic Weisbecker
2016-08-11 1:36 ` Wanpeng Li
2016-08-11 14:45 ` Peter Zijlstra
2016-08-11 14:57 ` Frederic Weisbecker
2016-08-11 15:14 ` Juri Lelli
2016-08-11 22:35 ` Wanpeng Li
2016-08-26 9:27 ` Wanpeng Li
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=20160810124308.GA19757@lerouge \
--to=fweisbec@gmail.com \
--cc=juri.lelli@arm.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=wanpeng.li@hotmail.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