From: Waiman Long <longman@redhat.com>
To: "Ridong Chen" <ridong.chen@linux.dev>,
"Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Shuah Khan" <shuah@kernel.org>
Cc: Chen Ridong <chenridong@huawei.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, Sashiko <sashiko-bot@kernel.org>,
Guopeng Zhang <zhangguopeng@kylinos.cn>,
Ridong Chen <chenridong@xiaomi.com>
Subject: Re: [PATCH v2 4/4] cpuset: generalize the validate_partition() interface
Date: Fri, 6 Nov 2026 22:59:13 -0500 [thread overview]
Message-ID: <04c50e9b-954f-4869-a9bd-41b9341bdef8@redhat.com> (raw)
In-Reply-To: <20261106105538.2915492-5-ridong.chen@linux.dev>
On 11/6/26 5:55 AM, Ridong Chen wrote:
> From: Chen Ridong <chenridong@huawei.com>
>
> Refactor validate_partition() to take the parent partition, the new
> partition root state, the new effective exclusive CPUs and the CPUs to
> be deleted, instead of a trial cpuset. A NULL parent stands for a
> remote partition, whose CPUs come from top_cpuset. This makes the
> interface flexible enough to handle both local and remote partition
> validation.
>
> The housekeeping conflict check is folded into validate_partition(). It
> is skipped when the parent is not a valid partition root, as @cs can't
> be a valid local partition in that case.
>
> Use the new interface for local partition enablement in
> update_parent_effective_cpumask() and in partition_cpus_change(),
> replacing the open-coded checks there. The order of the checks is now
> the same for both paths: empty CPUs, housekeeping conflict, then no CPU
> left for tasks.
>
> Signed-off-by: Chen Ridong <chenridong@huawei.com>
> Signed-off-by: Ridong Chen <chenridong@xiaomi.com>
> ---
> kernel/cgroup/cpuset.c | 112 +++++++++++++++++++----------------------
> 1 file changed, 52 insertions(+), 60 deletions(-)
>
> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
> index a5ab9396eb61..1b0ac4e76ec7 100644
> --- a/kernel/cgroup/cpuset.c
> +++ b/kernel/cgroup/cpuset.c
> @@ -1434,6 +1434,41 @@ static bool prstate_housekeeping_conflict(int new_prs, int parent_prs,
> return res;
> }
>
> +/**
> + * validate_partition - Validate a cpuset partition configuration
> + * @cs: The cpuset to validate
> + * @parent: Parent partition of @cs, NULL for remote partition
> + * @new_prs: The proposed new partition root state
> + * @new_excpus: The new effective exclusive CPUs mask to validate
> + * @del: exclusive CPUs to be deleted from @cs, can be NULL
> + *
> + * The housekeeping check is skipped if @parent is not a valid partition
> + * root as @cs can't be a valid local partition in that case.
> + *
> + * Return: PRS error code (0 if valid, non-zero error code if invalid)
> + */
> +static enum prs_errcode validate_partition(struct cpuset *cs,
> + struct cpuset *parent, int new_prs,
> + struct cpumask *new_excpus, struct cpumask *del)
> +{
> + int parent_prs = parent ? parent->partition_root_state : PRS_ROOT;
> +
> + if (new_prs == PRS_MEMBER)
> + return PERR_NONE;
> +
> + if (cpumask_empty(new_excpus))
> + return PERR_INVCPUS;
> +
> + if ((parent_prs > 0) &&
> + prstate_housekeeping_conflict(new_prs, parent_prs, new_excpus, del))
> + return PERR_HKEEPING;
> +
> + if (tasks_nocpu_error(parent_cs(cs), cs, new_excpus))
> + return PERR_NOCPUS;
For remote partition, the parent should be top_cpuset. I think we should
set parent to top_cpuset if NULL and pass it directly to
tasks_nocpu_error().
Other than that, the rests look good to me.
Cheers,
Longman
> +
> + return PERR_NONE;
> +}
> +
> /*
> * cpuset_update_sd_hk_unlock - Rebuild sched domains, update HK & unlock
> *
> @@ -1954,18 +1989,10 @@ static int update_parent_effective_cpumask(struct cpuset *cs, int cmd,
> if ((cmd == partcmd_enable) || (cmd == partcmd_enablei)) {
> new_prs = (cmd == partcmd_enable) ? PRS_ROOT : PRS_ISOLATED;
>
> - /*
> - * Enabling partition root is not allowed if its
> - * effective_xcpus is empty.
> - */
> - if (cpumask_empty(tmp->delmask))
> - return PERR_INVCPUS;
> -
> - if (prstate_housekeeping_conflict(new_prs, parent_prs, tmp->delmask, NULL))
> - return PERR_HKEEPING;
> -
> - if (nocpu)
> - return PERR_NOCPUS;
> + part_error = validate_partition(cs, parent, new_prs,
> + tmp->delmask, NULL);
> + if (part_error)
> + return part_error;
>
> /*
> * This function will only be called when all the preliminary
> @@ -2444,32 +2471,6 @@ static int parse_cpuset_cpulist(const char *buf, struct cpumask *out_mask)
> return 0;
> }
>
> -/**
> - * validate_partition - Validate a cpuset partition configuration
> - * @cs: The cpuset to validate
> - * @trialcs: The trial cpuset containing proposed configuration changes
> - *
> - * If any validation check fails, the appropriate error code is set in the
> - * cpuset's prs_err field.
> - *
> - * Return: PRS error code (0 if valid, non-zero error code if invalid)
> - */
> -static enum prs_errcode validate_partition(struct cpuset *cs, struct cpuset *trialcs)
> -{
> - struct cpuset *parent = parent_cs(cs);
> -
> - if (cs_is_member(trialcs))
> - return PERR_NONE;
> -
> - if (cpumask_empty(trialcs->effective_xcpus))
> - return PERR_INVCPUS;
> -
> - if (tasks_nocpu_error(parent, cs, trialcs->effective_xcpus))
> - return PERR_NOCPUS;
> -
> - return PERR_NONE;
> -}
> -
> /**
> * partition_cpus_change - Handle partition state changes due to CPU mask updates
> * @cs: The target cpuset being modified
> @@ -2483,33 +2484,24 @@ static void partition_cpus_change(struct cpuset *cs, struct cpuset *trialcs,
> struct tmpmasks *tmp)
> {
> enum prs_errcode prs_err;
> - int parent_prs = is_remote_partition(cs)
> - ? PRS_ROOT : parent_cs(cs)->partition_root_state;
> + struct cpuset *parent = is_remote_partition(cs) ? NULL : parent_cs(cs);
>
> if (cs_is_member(cs))
> return;
>
> - prs_err = validate_partition(cs, trialcs);
> - if (!prs_err && (parent_prs > 0) &&
> - !cpumask_empty(trialcs->effective_xcpus)) {
> - int prs = cs->partition_root_state;
> -
> - /*
> - * Check for housekeeping conflict by passing the whole
> - * effective_xcpus as well as those CPUs that are to be
> - * removed from cs as delmask.
> - */
> - if (prs > 0)
> - cpumask_andnot(tmp->delmask, cs->effective_xcpus,
> - trialcs->effective_xcpus);
> - else
> - cpumask_clear(tmp->delmask);
> -
> - if (prstate_housekeeping_conflict(prs, parent_prs,
> - trialcs->effective_xcpus, tmp->delmask))
> - prs_err = PERR_HKEEPING;
> - }
> + /*
> + * Check for housekeeping conflict by passing the whole
> + * effective_xcpus as well as those CPUs that are to be
> + * removed from cs as delmask.
> + */
> + if (is_partition_valid(cs))
> + cpumask_andnot(tmp->delmask, cs->effective_xcpus,
> + trialcs->effective_xcpus);
> + else
> + cpumask_clear(tmp->delmask);
>
> + prs_err = validate_partition(cs, parent, trialcs->partition_root_state,
> + trialcs->effective_xcpus, tmp->delmask);
> if (prs_err) {
> WRITE_ONCE(cs->prs_err, prs_err);
> trialcs->prs_err = prs_err;
prev parent reply other threads:[~2026-11-07 3:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 10:55 [PATCH v2 0/4] cpuset: preparatory fixes and cleanups for partition rework Ridong Chen
2026-11-06 10:55 ` [PATCH v2 1/4] cgroup/cpuset: Reset partition data when an invalid partition stays invalid Ridong Chen
2026-11-06 19:10 ` Waiman Long
2026-11-06 10:55 ` [PATCH v2 2/4] cpuset: add early empty cpumask check in partition_xcpus_add/del Ridong Chen
2026-11-07 2:21 ` Waiman Long
2026-11-06 10:55 ` [PATCH v2 3/4] cpuset: settle isolation state when CPUs are given back to parent Ridong Chen
2026-11-07 2:28 ` Waiman Long
2026-11-06 10:55 ` [PATCH v2 4/4] cpuset: generalize the validate_partition() interface Ridong Chen
2026-11-07 3:59 ` Waiman Long [this message]
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=04c50e9b-954f-4869-a9bd-41b9341bdef8@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=chenridong@xiaomi.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=ridong.chen@linux.dev \
--cc=sashiko-bot@kernel.org \
--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®