From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: "Ridong Chen" <ridong.chen@linux.dev>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Shuah Khan" <shuah@kernel.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
"Guopeng Zhang" <guopeng.zhang@linux.dev>,
sashiko-bot@kernel.org
Subject: Re: [PATCH-next v3 00/11] cgroup/cpuset: Miscellaneous bug fixes & cleanup
Date: Mon, 26 Oct 2026 08:26:59 -1000 [thread overview]
Message-ID: <5e2e1243e837e2b73dcfe8217f521b0f@kernel.org> (raw)
In-Reply-To: <20261025214449.310715-1-longman@redhat.com>
> cgroup/cpuset: Find furthest isolated ancestor for invalidated
> isolated partition
> cgroup/cpuset: Properly compute effective xcpus in
> update_parent_effective_cpumask()
> cgroup/cpuset: Fix incorrect effective_cpus bug in
> update_cpumasks_hier()
> cgroup/cpuset: Minor fixes to prstate_housekeeping_conflict()
> selftests/cgroup: Check for a single range nohz_full CPUs before
> running test matrix
> cgroup/cpuset: Prevent recursive call of remote_cpus_update() via
> update_cpumasks_hier()
> cgroup/cpuset: Make sure compute_partition_effective_cpumask() is only
> called for valid partition
> cgroup/cpuset: Release invalid isolated CPUs in
> compute_partition_effective_cpumask()
> cgroup/cpuset: Release invalid isolated CPUs with a shrunk root
> partition parent
> cgroup/cpuset: Relocate compute_*effective_cpumask() and
> compute_effective_nodemask()
> cgroup/cpuset: Integrate compute_partition_effective_cpumask() into
> compute_effective_cpumask()
Applied 1-11 to cgroup/for-7.4-fixes (9 as v3.1) with the Fixes tag
dropped from 5 and the following tags added:
Reviewed-by: Guopeng Zhang <zhangguopeng@kylinos.cn> (1-4, 8, 9)
Tested-by: Guopeng Zhang <zhangguopeng@kylinos.cn> (2, 8, 9)
Acked-by: Guopeng Zhang <zhangguopeng@kylinos.cn> (7, 10, 11)
Thanks.
--
tejun
prev parent reply other threads:[~2026-10-26 18:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 21:44 [PATCH-next v3 00/11] cgroup/cpuset: Miscellaneous bug fixes & cleanup Waiman Long
2026-10-25 21:44 ` [PATCH-next v3 01/11] cgroup/cpuset: Find furthest isolated ancestor for invalidated isolated partition Waiman Long
2026-10-26 6:33 ` Guopeng Zhang
2026-10-25 21:44 ` [PATCH-next v3 02/11] cgroup/cpuset: Properly compute effective xcpus in update_parent_effective_cpumask() Waiman Long
2026-10-26 6:39 ` Guopeng Zhang
2026-10-25 21:44 ` [PATCH-next v3 03/11] cgroup/cpuset: Fix incorrect effective_cpus bug in update_cpumasks_hier() Waiman Long
2026-10-26 6:46 ` Guopeng Zhang
2026-10-25 21:44 ` [PATCH-next v3 04/11] cgroup/cpuset: Minor fixes to prstate_housekeeping_conflict() Waiman Long
2026-10-26 6:57 ` Guopeng Zhang
2026-10-25 21:44 ` [PATCH-next v3 05/11] selftests/cgroup: Check for a single range nohz_full CPUs before running test matrix Waiman Long
2026-10-25 21:44 ` [PATCH-next v3 06/11] cgroup/cpuset: Prevent recursive call of remote_cpus_update() via update_cpumasks_hier() Waiman Long
2026-10-25 21:44 ` [PATCH-next v3 07/11] cgroup/cpuset: Make sure compute_partition_effective_cpumask() is only called for valid partition Waiman Long
2026-10-26 7:14 ` Guopeng Zhang
2026-10-25 21:44 ` [PATCH-next v3 08/11] cgroup/cpuset: Release invalid isolated CPUs in compute_partition_effective_cpumask() Waiman Long
2026-10-26 8:49 ` Guopeng Zhang
2026-10-25 21:44 ` [PATCH-next v3 09/11] cgroup/cpuset: Release invalid isolated CPUs with a shrunk root partition parent Waiman Long
2026-10-25 23:53 ` [PATCH-next v3.1 " Waiman Long
2026-10-26 8:51 ` Guopeng Zhang
2026-10-25 23:56 ` [PATCH-next v3 " Waiman Long
2026-10-25 21:44 ` [PATCH-next v3 10/11] cgroup/cpuset: Relocate compute_*effective_cpumask() and compute_effective_nodemask() Waiman Long
2026-10-26 9:08 ` Guopeng Zhang
2026-10-25 21:44 ` [PATCH-next v3 11/11] cgroup/cpuset: Integrate compute_partition_effective_cpumask() into compute_effective_cpumask() Waiman Long
2026-10-26 9:44 ` Guopeng Zhang
2026-10-26 18:26 ` Tejun Heo [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=5e2e1243e837e2b73dcfe8217f521b0f@kernel.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=guopeng.zhang@linux.dev \
--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=sashiko-bot@kernel.org \
--cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.