From: Chen Ridong <chenridong@huaweicloud.com>
To: Waiman Long <llong@redhat.com>,
tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
lujialin4@huawei.com
Subject: Re: [PATCH -next 6/6] cpuset: remove v1-specific code from generate_sched_domains
Date: Thu, 18 Dec 2025 11:32:31 +0800 [thread overview]
Message-ID: <73f40887-658c-4302-a16b-890ce4f6ccce@huaweicloud.com> (raw)
In-Reply-To: <5a4927e2-ff7f-4f81-b8e3-183f3acb84f4@redhat.com>
On 2025/12/18 11:14, Waiman Long wrote:
> On 12/17/25 8:39 PM, Chen Ridong wrote:
>>
>> On 2025/12/18 3:05, Waiman Long wrote:
>>> On 12/17/25 3:49 AM, Chen Ridong wrote:
>>>> From: Chen Ridong <chenridong@huawei.com>
>>>>
>>>> Following the introduction of cpuset1_generate_sched_domains() for v1
>>>> in the previous patch, v1-specific logic can now be removed from the
>>>> generic generate_sched_domains(). This patch cleans up the v1-only
>>>> code and ensures uf_node is only visible when CONFIG_CPUSETS_V1=y.
>>>>
>>>> Signed-off-by: Chen Ridong <chenridong@huawei.com>
>>>> ---
>>>> kernel/cgroup/cpuset-internal.h | 10 +--
>>>> kernel/cgroup/cpuset-v1.c | 2 +-
>>>> kernel/cgroup/cpuset.c | 144 +++++---------------------------
>>>> 3 files changed, 27 insertions(+), 129 deletions(-)
>>>>
>>>> diff --git a/kernel/cgroup/cpuset-internal.h b/kernel/cgroup/cpuset-internal.h
>>>> index bd767f8cb0ed..ef7b7c5afd4c 100644
>>>> --- a/kernel/cgroup/cpuset-internal.h
>>>> +++ b/kernel/cgroup/cpuset-internal.h
>>>> @@ -175,14 +175,14 @@ struct cpuset {
>>>> /* Handle for cpuset.cpus.partition */
>>>> struct cgroup_file partition_file;
>>>> - /* Used to merge intersecting subsets for generate_sched_domains */
>>>> - struct uf_node node;
>>>> -
>>>> #ifdef CONFIG_CPUSETS_V1
>>>> struct fmeter fmeter; /* memory_pressure filter */
>>>> /* for custom sched domain */
>>>> int relax_domain_level;
>>>> +
>>>> + /* Used to merge intersecting subsets for generate_sched_domains */
>>>> + struct uf_node node;
>>>> #endif
>>>> };
>>>> @@ -315,8 +315,6 @@ void cpuset1_hotplug_update_tasks(struct cpuset *cs,
>>>> int cpuset1_validate_change(struct cpuset *cur, struct cpuset *trial);
>>>> void cpuset1_init(struct cpuset *cs);
>>>> void cpuset1_online_css(struct cgroup_subsys_state *css);
>>>> -void update_domain_attr_tree(struct sched_domain_attr *dattr,
>>>> - struct cpuset *root_cs);
>>>> int cpuset1_generate_sched_domains(cpumask_var_t **domains,
>>>> struct sched_domain_attr **attributes);
>>>> @@ -331,8 +329,6 @@ static inline int cpuset1_validate_change(struct cpuset *cur,
>>>> struct cpuset *trial) { return 0; }
>>>> static inline void cpuset1_init(struct cpuset *cs) {}
>>>> static inline void cpuset1_online_css(struct cgroup_subsys_state *css) {}
>>>> -static inline void update_domain_attr_tree(struct sched_domain_attr *dattr,
>>>> - struct cpuset *root_cs) {}
>>>> static inline int cpuset1_generate_sched_domains(cpumask_var_t **domains,
>>>> struct sched_domain_attr **attributes) { return 0; };
>>>> diff --git a/kernel/cgroup/cpuset-v1.c b/kernel/cgroup/cpuset-v1.c
>>>> index 5c0bded46a7c..0226350e704f 100644
>>>> --- a/kernel/cgroup/cpuset-v1.c
>>>> +++ b/kernel/cgroup/cpuset-v1.c
>>>> @@ -560,7 +560,7 @@ update_domain_attr(struct sched_domain_attr *dattr, struct cpuset *c)
>>>> dattr->relax_domain_level = c->relax_domain_level;
>>>> }
>>>> -void update_domain_attr_tree(struct sched_domain_attr *dattr,
>>>> +static void update_domain_attr_tree(struct sched_domain_attr *dattr,
>>>> struct cpuset *root_cs)
>>>> {
>>>> struct cpuset *cp;
>>>> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
>>>> index 6bb0b201c34b..3e3468d928f3 100644
>>>> --- a/kernel/cgroup/cpuset.c
>>>> +++ b/kernel/cgroup/cpuset.c
>>>> @@ -789,18 +789,13 @@ static int generate_sched_domains(cpumask_var_t **domains,
>>>> {
>>>> struct cpuset *cp; /* top-down scan of cpusets */
>>>> struct cpuset **csa; /* array of all cpuset ptrs */
>>>> - int csn; /* how many cpuset ptrs in csa so far */
>>>> int i, j; /* indices for partition finding loops */
>>>> cpumask_var_t *doms; /* resulting partition; i.e. sched domains */
>>>> struct sched_domain_attr *dattr; /* attributes for custom domains */
>>>> int ndoms = 0; /* number of sched domains in result */
>>>> - int nslot; /* next empty doms[] struct cpumask slot */
>>>> struct cgroup_subsys_state *pos_css;
>>>> - bool root_load_balance = is_sched_load_balance(&top_cpuset);
>>>> - bool cgrpv2 = cpuset_v2();
>>>> - int nslot_update;
>>>> - if (!cgrpv2)
>>>> + if (!cpuset_v2())
>>>> return cpuset1_generate_sched_domains(domains, attributes);
>>>> doms = NULL;
>>>> @@ -808,70 +803,25 @@ static int generate_sched_domains(cpumask_var_t **domains,
>>>> csa = NULL;
>>>> /* Special case for the 99% of systems with one, full, sched domain */
>>>> - if (root_load_balance && cpumask_empty(subpartitions_cpus)) {
>>>> -single_root_domain:
>>>> + if (cpumask_empty(subpartitions_cpus)) {
>>>> ndoms = 1;
>>>> - doms = alloc_sched_domains(ndoms);
>>>> - if (!doms)
>>>> - goto done;
>>>> -
>>>> - dattr = kmalloc(sizeof(struct sched_domain_attr), GFP_KERNEL);
>>>> - if (dattr) {
>>>> - *dattr = SD_ATTR_INIT;
>>>> - update_domain_attr_tree(dattr, &top_cpuset);
>>>> - }
>>>> - cpumask_and(doms[0], top_cpuset.effective_cpus,
>>>> - housekeeping_cpumask(HK_TYPE_DOMAIN));
>>>> -
>>>> - goto done;
>>>> + goto generate_doms;
>>> That is not correct. The code under the generate_doms label will need to access csa[0] which is not
>>> allocated yet and may cause panic. You either need to keep the current code or move it after the csa
>>> allocation and assign top_cpuset to csa[0].
>>>
>> Thank you, Longman.
>>
>> Sorry, I should note that I made a small change. I added a !csa check: if csa is not allocated, then
>> ndoms should equal 1, and we only need the top_cpuset (no csa is indeed required). I think it's
>> cleaner to avoid allocating csa when there's no valid partition.
>>
>> ```
>> + for (i = 0; i < ndoms; i++) {
>> + /*
>> + * The top cpuset may contain some boot time isolated
>> + * CPUs that need to be excluded from the sched domain.
>> + */
>> + if (!csa || csa[i] == &top_cpuset)
>> + cpumask_and(doms[i], top_cpuset.effective_cpus,
>> + housekeeping_cpumask(HK_TYPE_DOMAIN));
>> + else
>> + cpumask_copy(doms[i], csa[i]->effective_cpus);
>> + if (dattr)
>> + dattr[i] = SD_ATTR_INIT;
>> }
>> ```
>>
>> Tested with single‑domain generation — no panic or warning observed.
>
> Yes, !csa check here should be good enough to handle the NULL csa case here. Maybe adding a comment
> in the goto line saying that !csa will be correctly handled.
>
Good idea, will add.
--
Best regards,
Ridong
next prev parent reply other threads:[~2025-12-18 3:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 8:49 [PATCH -next 0/6] cpuset: further separate v1 and v2 implementations Chen Ridong
2025-12-17 8:49 ` [PATCH -next 1/6] cpuset: add assert_cpuset_lock_held helper Chen Ridong
2025-12-17 17:02 ` Waiman Long
2025-12-18 0:37 ` Chen Ridong
2025-12-17 8:49 ` [PATCH -next 2/6] cpuset: add cpuset1_online_css helper for v1-specific operations Chen Ridong
2025-12-17 8:49 ` [PATCH -next 3/6] cpuset: add cpuset1_init helper for v1 initialization Chen Ridong
2025-12-17 8:49 ` [PATCH -next 4/6] cpuset: move update_domain_attr_tree to cpuset_v1.c Chen Ridong
2025-12-17 17:09 ` Waiman Long
2025-12-18 0:44 ` Chen Ridong
2025-12-18 3:06 ` Waiman Long
2025-12-17 8:49 ` [PATCH -next 5/6] cpuset: separate generate_sched_domains for v1 and v2 Chen Ridong
2025-12-17 17:48 ` Waiman Long
2025-12-18 1:28 ` Chen Ridong
2025-12-18 3:09 ` Waiman Long
2025-12-18 3:31 ` Chen Ridong
2025-12-17 8:49 ` [PATCH -next 6/6] cpuset: remove v1-specific code from generate_sched_domains Chen Ridong
2025-12-17 19:05 ` Waiman Long
2025-12-18 1:39 ` Chen Ridong
2025-12-18 3:14 ` Waiman Long
2025-12-18 3:32 ` Chen Ridong [this message]
2025-12-18 3:56 ` Chen Ridong
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=73f40887-658c-4302-a16b-890ce4f6ccce@huaweicloud.com \
--to=chenridong@huaweicloud.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llong@redhat.com \
--cc=lujialin4@huawei.com \
--cc=mkoutny@suse.com \
--cc=tj@kernel.org \
/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