[PATCH-next 0/3] Skip boot CPU or don't allow it from being used in isolcpus and isolated partitions

From: Waiman Long

Date: Fri Nov 20 2026 - 22:14:18 EST


It is reported that having CPU 0 being domain isolated can cause
problems in the some kernel subystems which don't take into account
that the boot CPU (CPU 0) may not be a HK_TYPE_DOMAIN housekeeping CPU.
As a result, it makes sense to just disallow CPU 0 from being used
in the isolcpus=domain boot parameter as well as in cpuset isolated
partitions instead of trying to fix the problems when they show up.

The first patch fixes the inconsistency problems between
tick_nohz_full_mask and HK_TYPE_KERNEL_NOISE cpumask.

The second patch removes the boot CPU from the isolcpus=domain parameter
if set.

The third patch disallows isolated partitions from being created if CPU 0
is specified in its effective exclusive cpumask.

Waiman Long (3):
tick/sched: Make tick_nohz_full_mask and HK_TYPE_KERNEL_NOISE cpumask
consistent
sched/isolation: Forbid the boot CPU from being isolated
cgroup/cpuset: Disallow CPU 0 from being used in isolated partition

Documentation/admin-guide/cgroup-v2.rst | 1 +
.../admin-guide/kernel-parameters.txt | 7 +--
include/linux/sched/isolation.h | 2 +
kernel/cgroup/cpuset-internal.h | 1 +
kernel/cgroup/cpuset.c | 6 +++
kernel/sched/isolation.c | 31 ++++++++++---
kernel/time/tick-sched.c | 8 +++-
.../selftests/cgroup/test_cpuset_prs.sh | 43 ++++++++++++-------
8 files changed, 74 insertions(+), 25 deletions(-)

--
2.56.1