From: Guopeng Zhang <guopeng.zhang@linux.dev>
To: cgroups@vger.kernel.org, longman@redhat.com, ridong.chen@linux.dev
Cc: tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com,
shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Guopeng Zhang <zhangguopeng@kylinos.cn>
Subject: [PATCH v2 3/6] selftests/cgroup: Add tests for type changes with child-owned CPUs
Date: Fri, 28 Aug 2026 17:56:40 +0800 [thread overview]
Message-ID: <20260828095643.13395-4-guopeng.zhang@linux.dev> (raw)
In-Reply-To: <20260828095643.13395-1-guopeng.zhang@linux.dev>
From: Guopeng Zhang <zhangguopeng@kylinos.cn>
Create an isolated child that owns a boot-isolated CPU, then change its
parent type and CPU mask. Check that the child stays isolated and the
parent remains valid.
Cache the boot-isolated CPU data during setup so this test does not depend
on an earlier test calling get_boot_isolated_cpu(). Keep the per-test check
that the selected CPU is online.
Signed-off-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
---
.../selftests/cgroup/test_cpuset_prs.sh | 69 +++++++++++++++++--
1 file changed, 65 insertions(+), 4 deletions(-)
diff --git a/tools/testing/selftests/cgroup/test_cpuset_prs.sh b/tools/testing/selftests/cgroup/test_cpuset_prs.sh
index 9a1cce4807b4..ae27245e90bb 100755
--- a/tools/testing/selftests/cgroup/test_cpuset_prs.sh
+++ b/tools/testing/selftests/cgroup/test_cpuset_prs.sh
@@ -107,6 +107,17 @@ then
echo "Pre-isolated CPUs: $BOOT_ISOLCPUS"
fi
+# Cache the CPUs isolated from scheduler domains at boot.
+BOOT_ISOLATED_FILE=/sys/devices/system/cpu/isolated
+BOOT_CPUS=
+BOOT_CPU=
+if [[ -r $BOOT_ISOLATED_FILE ]]
+then
+ BOOT_CPUS=$(cat $BOOT_ISOLATED_FILE)
+ [[ -n "$BOOT_CPUS" ]] &&
+ BOOT_CPU=$(echo "$BOOT_CPUS" | sed -e 's/[,-].*//')
+fi
+
cleanup()
{
online_cpus
@@ -1158,25 +1169,22 @@ test_isolated()
}
#
-# Select an online CPU isolated from scheduler domains at boot.
+# Check that a boot-isolated CPU selected during initialization is online.
# $1: test name used in the skip message
#
get_boot_isolated_cpu()
{
TEST_NAME=$1
- BOOT_ISOLATED_FILE=/sys/devices/system/cpu/isolated
[[ -r $BOOT_ISOLATED_FILE ]] || {
echo "$TEST_NAME test SKIPPED: boot isolation state unavailable"
return 1
}
- BOOT_CPUS=$(cat $BOOT_ISOLATED_FILE)
[[ -n "$BOOT_CPUS" ]] || {
echo "$TEST_NAME test SKIPPED: no boot-isolated CPU"
return 1
}
- BOOT_CPU=$(echo "$BOOT_CPUS" | sed -e 's/[,-].*//')
CPU_ONLINE=/sys/devices/system/cpu/cpu${BOOT_CPU}/online
[[ ! -e $CPU_ONLINE || $(cat $CPU_ONLINE) -eq 1 ]] || {
echo "$TEST_NAME test SKIPPED: CPU $BOOT_CPU is offline"
@@ -1214,6 +1222,58 @@ test_boot_isolated()
echo "$TEST_NAME test PASSED."
}
+#
+# A parent's type and CPU-mask changes must check only CPUs owned directly by
+# the parent, not a boot-isolated CPU owned by a valid child partition.
+#
+test_child_owned_cpus()
+{
+ TEST_NAME="Child-owned CPU type change"
+ get_boot_isolated_cpu "$TEST_NAME" || return 0
+ echo "Running $TEST_NAME test ..."
+
+ cd $CGROUP2/test
+ echo member > cpuset.cpus.partition
+ echo +cpuset > cgroup.subtree_control
+ echo 2,$BOOT_CPU > cpuset.cpus
+ [[ $(cat cpuset.cpus.effective) = "2,$BOOT_CPU" ]] || {
+ echo "$TEST_NAME test SKIPPED: CPUs 2,$BOOT_CPU are unavailable"
+ echo "" > cpuset.cpus
+ cd $CGROUP2
+ return 0
+ }
+ test_partition isolated
+ mkdir A1
+ cd A1
+ echo $BOOT_CPU > cpuset.cpus
+ test_partition isolated
+ cd ..
+ test_effective_cpus 2
+ test_partition root
+ echo 2-3,$BOOT_CPU > cpuset.cpus
+ test_effective_cpus 2-3
+ [[ $(cat cpuset.cpus.partition) = root ]] || {
+ echo "Parent partition became invalid during CPU update"
+ exit 1
+ }
+ [[ $(cat A1/cpuset.cpus.partition) = isolated ]] || {
+ echo "Child partition changed during parent update"
+ exit 1
+ }
+ check_isolcpus "." || {
+ echo "Parent update corrupted child isolation"
+ exit 1
+ }
+ cd A1
+ test_partition member
+ cd ..
+ rmdir A1
+ test_partition member
+ echo "" > cpuset.cpus
+ cd $CGROUP2
+ echo "$TEST_NAME test PASSED."
+}
+
#
# Wait for inotify event for the given file and read it
# $1: cgroup file to wait for
@@ -1286,5 +1346,6 @@ run_state_test TEST_MATRIX
run_remote_state_test REMOTE_TEST_MATRIX
test_isolated
test_boot_isolated
+test_child_owned_cpus
test_inotify
echo "All tests PASSED."
--
2.43.0
next prev parent reply other threads:[~2026-08-28 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 9:56 [PATCH v2 0/6] cgroup/cpuset: Fix partition type transitions Guopeng Zhang
2026-08-28 9:56 ` [PATCH v2 1/6] cgroup/cpuset: Respect child CPU ownership in type changes Guopeng Zhang
2026-08-28 9:56 ` [PATCH v2 2/6] selftests/cgroup: Add tests for type-change isolation accounting Guopeng Zhang
2026-08-28 9:56 ` Guopeng Zhang [this message]
2026-08-28 9:56 ` [PATCH v2 4/6] selftests/cgroup: Add tests for housekeeping CPU return to isolated parents Guopeng Zhang
2026-08-28 9:56 ` [PATCH v2 5/6] cgroup/cpuset: Release CPUs when type-change validation fails Guopeng Zhang
2026-08-28 9:56 ` [PATCH v2 6/6] selftests/cgroup: Add CPU release tests for type-change validation failures Guopeng Zhang
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=20260828095643.13395-4-guopeng.zhang@linux.dev \
--to=guopeng.zhang@linux.dev \
--cc=cgroups@vger.kernel.org \
--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=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®