mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: linux-kernel@vger.kernel.org, Wanpeng Li <wanpeng.li@hotmail.com>,
	Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: [PATCH] workqueue: fix rebind bound workers warning
Date: Mon, 9 May 2016 13:00:13 -0400	[thread overview]
Message-ID: <20160509170013.GI7110@mtj.duckdns.org> (raw)
In-Reply-To: <1462412491-11156-1-git-send-email-wanpeng.li@hotmail.com>

Hello,

On Thu, May 05, 2016 at 09:41:31AM +0800, Wanpeng Li wrote:
> The boot CPU handles housekeeping duty(unbound timers, workqueues, 
> timekeeping, ...) on behalf of full dynticks CPUs. It must remain 
> online when nohz full is enabled. There is a priority set to every
> notifier_blocks:
> 
> workqueue_cpu_up > tick_nohz_cpu_down > workqueue_cpu_down
> 
> So tick_nohz_cpu_down callback failed when down prepare cpu 0, and 
> notifier_blocks behind tick_nohz_cpu_down will not be called any 
> more, which leads to workers are actually not unbound. Then hotplug 
> state machine will fallback to undo and online cpu 0 again. Workers 
> will be rebound unconditionally even if they are not unbound and 
> trigger the warning in this progress.

I'm a bit confused.  Are you saying that the hotplug statemachine may
invoke CPU_DOWN_FAILED w/o preceding CPU_DOWN on the same callback?

Thanks.

-- 
tejun

  parent reply	other threads:[~2016-05-09 17:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05  1:41 Wanpeng Li
2016-05-09  7:28 ` Wanpeng Li
2016-05-09 17:00 ` Tejun Heo [this message]
2016-05-09 21:50   ` Wanpeng Li
2016-05-09 22:14     ` Wanpeng Li
2016-05-10 23:23     ` Wanpeng Li
2016-05-11  7:34       ` Thomas Gleixner
2016-05-11  8:05         ` Wanpeng Li
2016-05-11 10:03           ` Thomas Gleixner
2016-05-11 10:21             ` 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=20160509170013.GI7110@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=kernellwp@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®