On 9/22/26 5:20 AM, Guopeng Zhang wrote:
> From: Guopeng Zhang <zhangguopeng@kylinos.cn>
>
> The cpuset interface documentation says cpuset.cpus.isolated is empty
> unless an isolated partition exists, omitting CPUs isolated at boot with
> isolcpus=domain. Its cpuset.cpus.effective description also assumes CPUs
> come from the immediate parent and are normally a subset of
> cpuset.cpus, which is not always true for valid non-root partition roots.
>
> Update both descriptions to match the existing behavior.
>
> Changes since v2:
> - Update the valid partition root example to show that an offline CPU
> can remain in cpuset.cpus.exclusive.effective while being excluded
> from cpuset.cpus.effective.
> - Add the Reviewed-by tag to patch 2.
> - Patch 1 is unchanged.
>
> Guopeng Zhang (2):
> docs: cgroup-v2: Describe boot-isolated CPUs in cpuset.cpus.isolated
> docs: cgroup-v2: Describe effective CPUs of partition roots
>
> Documentation/admin-guide/cgroup-v2.rst | 62 ++++++++++++++++++++-----
> 1 file changed, 51 insertions(+), 11 deletions(-)
For the patch series,
Reviewed-by: Waiman Long <longman@redhat.com>