From: Guopeng Zhang <guopeng.zhang@linux.dev>
To: Waiman Long <longman@redhat.com>,
cgroups@vger.kernel.org, ridong.chen@linux.dev
Cc: tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com,
shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Guopeng Zhang <zhangguopeng@kylinos.cn>
Subject: Re: [PATCH v3 1/7] cgroup/cpuset: Factor out child partition validation
Date: Mon, 7 Sep 2026 17:48:30 +0800 [thread overview]
Message-ID: <8c4ae94b-503f-4ef5-9e60-724378b5fd23@linux.dev> (raw)
In-Reply-To: <9ff85fed-190c-4a8d-8d47-2a37990c1cbb@redhat.com>
在 2026/9/4 03:11, Waiman Long 写道:
> On 9/2/26 6:26 AM, Guopeng Zhang wrote:
>> From: Guopeng Zhang <zhangguopeng@kylinos.cn>
>>
>> compute_partition_effective_cpumask() checks whether each valid child
>> partition remains covered by the parent exclusive CPU mask and whether it
>> would consume all remaining CPUs of a populated parent.
>>
>> Factor these two checks into child_partition_error() so the same rules can
>> be reused when evaluating a proposed parent configuration. This is a
>> preparatory refactoring with no intended functional change.
>>
>> Signed-off-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
>> ---
>> kernel/cgroup/cpuset.c | 38 +++++++++++++++++++++++++++++---------
>> 1 file changed, 29 insertions(+), 9 deletions(-)
>>
>> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
>> index 8f24171b6055..6994dc75d940 100644
>> --- a/kernel/cgroup/cpuset.c
>> +++ b/kernel/cgroup/cpuset.c
>> @@ -2085,6 +2085,26 @@ static int update_parent_effective_cpumask(struct cpuset *cs, int cmd,
>> return 0;
>> }
>> +/*
>> + * Return the error that will invalidate a child partition under a proposed
>> + * parent partition configuration.
>> + */
>> +static enum prs_errcode
>> +child_partition_error(struct cpuset *child,
>> + const struct cpumask *partition_cpus,
>> + const struct cpumask *remaining_cpus,
>> + bool parent_populated)
>> +{
>> + if (!cpumask_subset(child->effective_xcpus, partition_cpus))
>> + return PERR_INVCPUS;
>> +
>> + if (parent_populated &&
>> + cpumask_subset(remaining_cpus, child->effective_xcpus))
>> + return PERR_NOCPUS;
>> +
>> + return PERR_NONE;
>> +}
>> +
>> /**
>> * compute_partition_effective_cpumask - compute effective_cpus for partition
>> * @cs: partition root cpuset
>> @@ -2121,6 +2141,8 @@ static void compute_partition_effective_cpumask(struct cpuset *cs,
>> rcu_read_lock();
>> cpuset_for_each_child(child, css, cs) {
>> + enum prs_errcode child_err;
>> +
>> if (!is_partition_valid(child))
>> continue;
>> @@ -2129,15 +2151,13 @@ static void compute_partition_effective_cpumask(struct cpuset *cs,
>> * partition root.
>> */
>> WARN_ON_ONCE(is_remote_partition(child));
>> - WRITE_ONCE(child->prs_err, 0);
>> - if (!cpumask_subset(child->effective_xcpus,
>> - cs->effective_xcpus))
>
> Looking at the patch again, I now see that the current code is incorrect. It should be "if (!cpumask_subset(child->effective_xcpus, new_ecpus))" So you only need to pass the "parent_excpus" (for instance) to the new helper instead of passing two.
>
Longman, thanks for your review.
Yes, you are right that using `cs->effective_xcpus` here is incorrect.
In v1, I had a change for this issue, and based on your comment [1], I moved it to another fix. I also followed Ridong's suggestion to split the original 17-patch series into smaller series. I split it into three parts locally, and the current series is the second part, so this fix is not included here.
I plan to address this in the third series, together with the CPU ownership and isolation accounting issues following child partition invalidation.
In that series, the two masks have different meanings: the newly computed unfiltered exclusive mask, including offline CPUs, is used for the child containment check, while the active CPU mask remaining after child ownership is accounted for is used for the `PERR_NOCPUS` check. So I would prefer to keep the two-mask interface here and clarify their meanings with comments.
Does this approach make sense to you?
[1] https://lore.kernel.org/all/3bf50da2-f13a-4cef-bfb8-cd592f862164@redhat.com/
Thanks,
Guopeng
next prev parent reply other threads:[~2026-09-07 9:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 10:26 [PATCH v3 0/7] cgroup/cpuset: Fix partition type transitions Guopeng Zhang
2026-09-02 10:26 ` [PATCH v3 1/7] cgroup/cpuset: Factor out child partition validation Guopeng Zhang
2026-09-03 18:33 ` Waiman Long
2026-09-04 1:25 ` Ridong Chen
2026-09-04 1:55 ` Ridong Chen
2026-09-07 10:16 ` Guopeng Zhang
2026-09-08 1:27 ` Ridong Chen
2026-09-08 12:14 ` Guopeng Zhang
2026-09-04 1:57 ` Ridong Chen
2026-09-04 2:00 ` Ridong Chen
2026-09-07 9:49 ` Guopeng Zhang
2026-09-08 1:40 ` Ridong Chen
2026-09-08 12:25 ` Guopeng Zhang
2026-09-07 9:48 ` Guopeng Zhang
2026-09-03 19:11 ` Waiman Long
2026-09-07 9:48 ` Guopeng Zhang [this message]
2026-09-02 10:26 ` [PATCH v3 2/7] cgroup/cpuset: Account for child CPU ownership in partition changes Guopeng Zhang
2026-09-02 10:26 ` [PATCH v3 3/7] selftests/cgroup: Add tests for type-change isolation accounting Guopeng Zhang
2026-09-02 10:26 ` [PATCH v3 4/7] selftests/cgroup: Test child CPU ownership in partition changes Guopeng Zhang
2026-09-02 10:26 ` [PATCH v3 5/7] selftests/cgroup: Add tests for housekeeping CPU return to isolated parents Guopeng Zhang
2026-09-02 10:26 ` [PATCH v3 6/7] cgroup/cpuset: Release CPUs when type-change validation fails Guopeng Zhang
2026-09-02 10:26 ` [PATCH v3 7/7] selftests/cgroup: Add CPU release tests for type-change validation failures 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=8c4ae94b-503f-4ef5-9e60-724378b5fd23@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=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®