docs: cgroup-v2: Describe boot-isolated CPUs in cpuset.cpus.isolated

cpuset.cpus.isolated is documented as empty when no isolated partition
exists. This is not true when CPUs are isolated at boot with
isolcpus=domain. cpuset_init() adds those CPUs to the isolated mask,
and isolcpus=<cpu-list> uses domain isolation by default. They remain
listed after a partition using them is released.

Document the boot-isolated CPUs as well.

Suggested-by: Ridong Chen <ridong.chen@linux.dev>
Reviewed-by: Ridong Chen <ridong.chen@linux.dev>
Signed-off-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
Reviewed-by: Waiman Long <longman@redhat.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
This commit is contained in:
Guopeng Zhang 2026-09-22 17:20:33 +08:00 committed by Tejun Heo
parent 024e82e1d3
commit 7abedcd2ab

View File

@ -2657,8 +2657,9 @@ Cpuset Interface Files
A read-only and root cgroup only multiple values file.
This file shows the set of all isolated CPUs used in existing
isolated partitions. It will be empty if no isolated partition
is created.
isolated partitions or isolated at boot time via the "domain"
flag of "isolcpus". The latter remain listed even after any
partition using them is released.
cpuset.cpus.partition
A read-write single value file which exists on non-root