From: Peter Zijlstra <peterz@infradead.org> To: mingo@kernel.org, tglx@linutronix.de Cc: linux-kernel@vger.kernel.org, jiangshanlai@gmail.com, valentin.schneider@arm.com, cai@redhat.com, vincent.donnefort@arm.com, decui@microsoft.com, paulmck@kernel.org, vincent.guittot@linaro.org, rostedt@goodmis.org, tj@kernel.org, peterz@infradead.org Subject: [PATCH 0/4] sched: Fix hot-unplug regressions Date: Tue, 12 Jan 2021 15:43:44 +0100 [thread overview] Message-ID: <20210112144344.850850975@infradead.org> (raw) Hi, These 4 patches are the simplest means (barring a revert) of fixing the CPU hot-unplug problems introduced by commit: 1cf12e08bc4d ("sched/hotplug: Consolidate task migration on CPU unplug") Testing here, any by Paul, indicate they survive a pounding. They restore the previous behaviour of forced affinity breaking for the class of kernel threads that happen to have single CPU affinity, but are not strictly a per-cpu kthread.
next reply other threads:[~2021-01-12 14:52 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-12 14:43 Peter Zijlstra [this message] 2021-01-12 14:43 ` [PATCH 2/4] kthread: Extract KTHREAD_IS_PER_CPU Peter Zijlstra 2021-01-12 14:43 ` [PATCH 3/4] workqueue: Tag bound workers with KTHREAD_IS_PER_CPU Peter Zijlstra 2021-01-12 16:36 ` Lai Jiangshan 2021-01-13 11:43 ` Peter Zijlstra 2021-01-12 17:57 ` Valentin Schneider 2021-01-13 13:28 ` Lai Jiangshan 2021-01-13 14:16 ` Valentin Schneider 2021-01-13 17:52 ` Paul E. McKenney 2021-01-13 18:43 ` Valentin Schneider 2021-01-13 18:59 ` Paul E. McKenney 2021-01-14 13:12 ` Peter Zijlstra 2021-01-14 13:21 ` Valentin Schneider 2021-01-14 15:34 ` Peter Zijlstra 2021-01-16 6:27 ` Lai Jiangshan 2021-01-16 12:45 ` Peter Zijlstra 2021-01-16 14:45 ` Lai Jiangshan 2021-01-16 15:16 ` Peter Zijlstra 2021-01-16 16:14 ` Lai Jiangshan 2021-01-16 18:46 ` Peter Zijlstra 2021-01-17 9:54 ` Peter Zijlstra 2021-01-16 15:13 ` Peter Zijlstra 2021-01-12 14:43 ` [PATCH 4/4] sched: Fix CPU hotplug / tighten is_per_cpu_kthread() Peter Zijlstra
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=20210112144344.850850975@infradead.org \ --to=peterz@infradead.org \ --cc=cai@redhat.com \ --cc=decui@microsoft.com \ --cc=jiangshanlai@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=paulmck@kernel.org \ --cc=rostedt@goodmis.org \ --cc=tglx@linutronix.de \ --cc=tj@kernel.org \ --cc=valentin.schneider@arm.com \ --cc=vincent.donnefort@arm.com \ --cc=vincent.guittot@linaro.org \ --subject='Re: [PATCH 0/4] sched: Fix hot-unplug regressions' \ /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
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).