From: Waiman Long <llong@redhat.com>
To: Chen Ridong <chenridong@huaweicloud.com>,
tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
lujialin4@huawei.com, chenridong@huawei.com
Subject: Re: [PATCH -next RFC -v2 07/11] cpuset: refactor out validate_partition
Date: Mon, 15 Sep 2025 14:53:45 -0400 [thread overview]
Message-ID: <90fb9914-3c6f-4d2a-8512-cebcaa5ddbb6@redhat.com> (raw)
In-Reply-To: <20250909033233.2731579-8-chenridong@huaweicloud.com>
On 9/8/25 11:32 PM, Chen Ridong wrote:
> From: Chen Ridong <chenridong@huawei.com>
>
> Refactor the validate_partition function to handle cpuset partition
> validation when modifying cpuset.cpus. This refactoring also makes the
> function reusable for handling cpuset.cpus.exclusive updates in subsequent
> patches.
>
> Signed-off-by: Chen Ridong <chenridong@huawei.com>
> ---
> kernel/cgroup/cpuset.c | 48 +++++++++++++++++++++++++++++++-----------
> 1 file changed, 36 insertions(+), 12 deletions(-)
>
> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
> index 389dfd5be6c8..770b33e30576 100644
> --- a/kernel/cgroup/cpuset.c
> +++ b/kernel/cgroup/cpuset.c
> @@ -2386,6 +2386,37 @@ 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 (prstate_housekeeping_conflict(trialcs->partition_root_state,
> + trialcs->effective_xcpus))
> + return PERR_HKEEPING;
> +
> + if (tasks_nocpu_error(parent, cs, trialcs->effective_xcpus))
> + return PERR_NOCPUS;
> +
> + return PERR_NONE;
> +}
> +
> +
> /**
> * update_cpumask - update the cpus_allowed mask of a cpuset and all tasks in it
> * @cs: the cpuset to consider
> @@ -2401,6 +2432,7 @@ static int update_cpumask(struct cpuset *cs, struct cpuset *trialcs,
> bool invalidate = false;
> bool force = false;
> int old_prs = cs->partition_root_state;
> + enum prs_errcode prs_err;
>
> retval = parse_cpuset_cpulist(buf, trialcs->cpus_allowed);
> if (retval < 0)
> @@ -2415,18 +2447,10 @@ static int update_cpumask(struct cpuset *cs, struct cpuset *trialcs,
>
> compute_trialcs_excpus(trialcs, cs);
>
> - if (old_prs) {
> - if (is_partition_valid(cs) &&
> - cpumask_empty(trialcs->effective_xcpus)) {
> - invalidate = true;
> - cs->prs_err = PERR_INVCPUS;
> - } else if (prstate_housekeeping_conflict(old_prs, trialcs->effective_xcpus)) {
> - invalidate = true;
> - cs->prs_err = PERR_HKEEPING;
> - } else if (tasks_nocpu_error(parent, cs, trialcs->effective_xcpus)) {
> - invalidate = true;
> - cs->prs_err = PERR_NOCPUS;
> - }
> + prs_err = validate_partition(cs, trialcs);
> + if (prs_err) {
> + invalidate = true;
> + cs->prs_err = prs_err;
> }
>
> /*
Reviewed-by: Waiman Long <longman@redhat.com>
next prev parent reply other threads:[~2025-09-15 18:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 3:32 [PATCH -next RFC -v2 00/11] Refactor cpus mask setting Chen Ridong
2025-09-09 3:32 ` [PATCH -next RFC -v2 01/11] cpuset: move the root cpuset write check earlier Chen Ridong
2025-09-15 18:43 ` Waiman Long
2025-09-09 3:32 ` [PATCH -next RFC -v2 02/11] cpuset: remove unused assignment to trialcs->partition_root_state Chen Ridong
2025-09-15 18:44 ` Waiman Long
2025-09-09 3:32 ` [PATCH -next RFC -v2 03/11] cpuset: change return type of is_partition_[in]valid to bool Chen Ridong
2025-09-15 18:44 ` Waiman Long
2025-09-09 3:32 ` [PATCH -next RFC -v2 04/11] cpuset: Refactor exclusive CPU mask computation logic Chen Ridong
2025-09-15 18:47 ` Waiman Long
2025-09-09 3:32 ` [PATCH -next RFC -v2 05/11] cpuset: refactor CPU mask buffer parsing logic Chen Ridong
2025-09-15 18:49 ` Waiman Long
2025-09-09 3:32 ` [PATCH -next RFC -v2 06/11] cpuset: introduce cpus_excl_conflict and mems_excl_conflict helpers Chen Ridong
2025-09-15 18:42 ` Waiman Long
2025-09-16 7:59 ` Chen Ridong
2025-09-09 3:32 ` [PATCH -next RFC -v2 07/11] cpuset: refactor out validate_partition Chen Ridong
2025-09-15 18:53 ` Waiman Long [this message]
2025-09-09 3:32 ` [PATCH -next RFC -v2 08/11] cpuset: refactor cpus_allowed_validate_change Chen Ridong
2025-09-15 19:05 ` Waiman Long
2025-09-09 3:32 ` [PATCH -next RFC -v2 09/11] cpuset: refactor partition_cpus_change Chen Ridong
2025-09-15 19:34 ` Waiman Long
2025-09-16 8:01 ` Chen Ridong
2025-09-09 3:32 ` [PATCH -next RFC -v2 10/11] cpuset: use parse_cpulist for setting cpus.exclusive Chen Ridong
2025-09-15 19:39 ` Waiman Long
2025-09-09 3:32 ` [PATCH -next RFC -v2 11/11] cpuset: use partition_cpus_change for setting exclusive cpus Chen Ridong
2025-09-15 20:05 ` Waiman Long
2025-09-16 8:02 ` Chen Ridong
2025-09-15 11:18 ` [PATCH -next RFC -v2 00/11] Refactor cpus mask setting 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=90fb9914-3c6f-4d2a-8512-cebcaa5ddbb6@redhat.com \
--to=llong@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=chenridong@huaweicloud.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--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