From: Guopeng Zhang <guopeng.zhang@linux.dev>
To: Waiman Long <longman@redhat.com>, Tejun Heo <tj@kernel.org>
Cc: "Ridong Chen" <ridong.chen@linux.dev>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Shuah Khan" <shuah@kernel.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Guopeng Zhang" <guopeng.zhang@linux.dev>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
"Guopeng Zhang" <zhangguopeng@kylinos.cn>
Subject: [PATCH v3 0/3] cgroup/cpuset: Keep the top scheduling domain populated
Date: Tue, 10 Nov 2026 13:03:21 +0800 [thread overview]
Message-ID: <20261110050324.173461-1-guopeng.zhang@linux.dev> (raw)
From: Guopeng Zhang <zhangguopeng@kylinos.cn>
Boot-isolated CPUs stay in top_cpuset.effective_cpus, but are excluded
from its scheduling domain. Allocating all boot domain housekeeping CPUs
to partitions can therefore leave the top scheduling domain empty even
though effective_cpus is nonempty, leading to warnings and an OOPS in
build_perf_domains(). CPU hotplug can reach the same state.
The patches are ordered as follows:
1. Check local and remote partition creation and CPU mask updates.
2. Allow top-level partition CPU replacements that return CPUs to the
parent in the same update.
3. Handle CPU hotplug and preserve partitions that cannot return an
active boot domain housekeeping CPU.
Changes since v2:
Keep patch 1's kernel changes unchanged. Update its selftests following
Longman's and Sashiko's comments and cover recovery with a single
top-level HK CPU. Add patch 2 to fix the CPU replacement rejection
reported by Sashiko, with its own regression test. Update the hotplug
fix, now patch 3, to avoid invalidating unrelated partitions, including
partitions whose boot housekeeping CPUs are all offline. Drop v2's
isolated CPU cleanup patch in favor of Ridong's fix:
https://lore.kernel.org/all/20261107120100.3587595-4-ridong.chen@linux.dev/
v2: https://lore.kernel.org/all/20261105130344.664336-1-guopeng.zhang@linux.dev/
Changes since v1:
Rework the fix following Ridong's suggestion and add test cases.
Add patch 2 for CPU hotplug and patch 3 for isolated CPU cleanup
when the parent partition becomes invalid.
v1: https://lore.kernel.org/all/20261104071600.474587-1-guopeng.zhang@linux.dev/
Guopeng Zhang (3):
cgroup/cpuset: Reject updates that empty the top sched domain
cgroup/cpuset: Allow top-level partition CPU replacement
cgroup/cpuset: Keep the top sched domain non-empty on CPU hotplug
kernel/cgroup/cpuset.c | 75 +++++++++++++++++--
.../selftests/cgroup/test_cpuset_prs.sh | 68 +++++++++++++++++
2 files changed, 137 insertions(+), 6 deletions(-)
--
2.43.0
next reply other threads:[~2026-11-10 5:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 5:03 Guopeng Zhang [this message]
2026-11-10 5:03 ` [PATCH v3 1/3] cgroup/cpuset: Reject updates that empty the top sched domain Guopeng Zhang
2026-11-10 5:03 ` [PATCH v3 2/3] cgroup/cpuset: Allow top-level partition CPU replacement Guopeng Zhang
2026-11-10 5:03 ` [PATCH v3 3/3] cgroup/cpuset: Keep the top sched domain non-empty on CPU hotplug Guopeng Zhang
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=20261110050324.173461-1-guopeng.zhang@linux.dev \
--to=guopeng.zhang@linux.dev \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mkoutny@suse.com \
--cc=ridong.chen@linux.dev \
--cc=shuah@kernel.org \
--cc=tj@kernel.org \
--cc=zhangguopeng@kylinos.cn \
/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®