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>,
"Jonathan Corbet" <corbet@lwn.net>,
"Randy Dunlap" <rdunlap@infradead.org>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"Hui Peng" <benquike@gmail.com>,
"Guopeng Zhang" <guopeng.zhang@linux.dev>
Subject: Re: [PATCH-next v4 0/9] cgroup/cpuset: Fix various housekeeping check problems
Date: Mon, 19 Oct 2026 10:51:16 -1000 [thread overview]
Message-ID: <ataCxJxYwg_uhS-j@slm.duckdns.org> (raw)
In-Reply-To: <20261019181020.1069325-1-longman@redhat.com>
On Mon, Oct 19, 2026 at 02:10:11PM -0400, Waiman Long wrote:
> v4:
> - Adjust a number of patches to fix issues reported by Sashiko and
> Guopeng Zhang.
> - Add more test cases to test_cpuset_prs.sh to improve test coverage.
>
> v3:
> - https://lore.kernel.org/lkml/20261014140548.575122-1-longman@redhat.com
> - Further revise the code based on feedback from sashiko and
> reviewers.
> - Add a new fix patch which fixes a bug found during the testing process.
> - Add a patch to impose a new restriction that creating a child root
> partition under an isolated parent partition is not allowed.
>
> v2:
> - Update patches 2 and 3 to address bugs reported by sashiko.
> - Add a new test_cpuset_prs.sh patch to skip the test if some of the
> required CPUs are offline.
Can you ping me after -rc1 drops?
Thanks.
--
tejun
next prev parent reply other threads:[~2026-10-19 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 18:10 [PATCH-next v4 0/9] cgroup/cpuset: Fix various housekeeping check problems Waiman Long
2026-10-19 18:10 ` [PATCH-next v4 1/9] cgroup/cpuset: Fix a missing isolated_cpus update in update_cpumasks_hier() Waiman Long
2026-10-19 18:10 ` [PATCH-next v4 2/9] cgroup/cpuset: Consolidate isolated_cpus_can_update() into prstate_housekeeping_conflict() Waiman Long
2026-10-19 18:10 ` [PATCH-next v4 3/9] cgroup/cpuset: Consider all the exclusive CPUs when doing housekeeping check Waiman Long
2026-10-19 18:10 ` [PATCH-next v4 4/9] cgroup/cpuset: Do housekeeping check before converting invalid partition to valid Waiman Long
2026-10-19 18:10 ` [PATCH-next v4 5/9] cgroup/cpuset: Properly disabling partition when partition state switching fails Waiman Long
2026-10-19 18:10 ` [PATCH-next v4 6/9] cgroup/cpuset: Don't allow a child root partition under an isolated parent Waiman Long
2026-10-19 18:10 ` [PATCH-next v4 7/9] selftests/cgroup: Add tests for isolcpus housekeeping check Waiman Long
2026-10-19 18:10 ` [PATCH-next v4 8/9] selftests/cgroup: Add tests for nohz_full " Waiman Long
2026-10-19 18:10 ` [PATCH-next v4 9/9] selftests/cgroup: Skip test_cpuset_prs.sh test if some required CPUs are offline Waiman Long
2026-10-19 20:51 ` Tejun Heo [this message]
2026-10-19 20:57 ` [PATCH-next v4 0/9] cgroup/cpuset: Fix various housekeeping check problems Waiman Long
2026-10-19 23:16 ` Tejun Heo
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=ataCxJxYwg_uhS-j@slm.duckdns.org \
--to=tj@kernel.org \
--cc=benquike@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=guopeng.zhang@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=rdunlap@infradead.org \
--cc=ridong.chen@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox