From: "Michal Koutný" <mkoutny@suse.com>
To: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-kselftest@vger.kernel.org
Cc: Waiman Long <longman@redhat.com>,
Zefan Li <lizefan.x@bytedance.com>, Tejun Heo <tj@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Shuah Khan <shuah@kernel.org>
Subject: [PATCH 0/3] cpuset: Allow setscheduler regardless of manipulated task
Date: Thu, 29 Jun 2023 11:11:43 +0200 [thread overview]
Message-ID: <20230629091146.28801-1-mkoutny@suse.com> (raw)
Changes in v1:
- added selftests
- comments rewording
RFC in https://lore.kernel.org/r/20220623124944.2753-1-mkoutny@suse.com
Michal Koutný (3):
cpuset: Allow setscheduler regardless of manipulated task
selftests: cgroup: Minor code reorganizations
selftests: cgroup: Add cpuset migrations testcase
MAINTAINERS | 2 +
kernel/cgroup/cpuset.c | 7 +
tools/testing/selftests/cgroup/.gitignore | 1 +
tools/testing/selftests/cgroup/Makefile | 2 +
tools/testing/selftests/cgroup/cgroup_util.c | 2 +
tools/testing/selftests/cgroup/cgroup_util.h | 2 +
tools/testing/selftests/cgroup/test_core.c | 2 +-
tools/testing/selftests/cgroup/test_cpuset.c | 272 ++++++++++++++++++
.../selftests/cgroup/test_cpuset_prs.sh | 2 +-
9 files changed, 290 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/cgroup/test_cpuset.c
base-commit: 6995e2de6891c724bfeb2db33d7b87775f913ad1
--
2.41.0
next reply other threads:[~2023-06-29 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 9:11 Michal Koutný [this message]
2023-06-29 9:11 ` [PATCH 1/3] cpuset: Allow setscheduler regardless of manipulated task Michal Koutný
2023-06-29 12:11 ` Waiman Long
2023-06-29 12:26 ` Michal Koutný
2023-06-29 13:25 ` Waiman Long
2023-06-30 18:42 ` Michal Koutný
2023-06-29 9:11 ` [PATCH 2/3] selftests: cgroup: Minor code reorganizations Michal Koutný
2023-06-29 9:11 ` [PATCH 3/3] selftests: cgroup: Add cpuset migrations testcase Michal Koutný
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=20230629091146.28801-1-mkoutny@suse.com \
--to=mkoutny@suse.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=shuah@kernel.org \
--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