From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>
Cc: lizefan.x@bytedance.com, hannes@cmpxchg.org,
cgroups@vger.kernel.org, peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 0/4] cgroup: Introduce cpu controller test suite
Date: Fri, 22 Apr 2022 08:40:46 -1000 [thread overview]
Message-ID: <YmL2rt7A6qfiv1X4@slm.duckdns.org> (raw)
In-Reply-To: <20220422173349.3394844-1-void@manifault.com>
On Fri, Apr 22, 2022 at 10:33:47AM -0700, David Vernet wrote:
> This patchset introduces a new test_cpu.c test suite as part of
> tools/testing/selftests/cgroup. test_cpu.c will contain testcases that
> validate the cgroup v2 cpu controller.
>
> This patchset only contains testcases that validate cpu.stat and
> cpu.weight, but I'm expecting to send further patchsets after this that
> also include testcases that validate other knobs such as cpu.max.
>
> Note that checkpatch complains about a missing MAINTAINERS file entry for
> [PATCH 1/4], but Roman Gushchin added that entry in a separate patchset:
> https://lore.kernel.org/all/20220415000133.3955987-4-roman.gushchin@linux.dev/.
Applied to cgroup/for-5.19.
Thanks.
--
tejun
next prev parent reply other threads:[~2022-04-22 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 17:33 [PATCH 0/4] cgroup: Introduce cpu controller test suite David Vernet
2022-04-22 17:33 ` [PATCH v2 1/4] cgroup: Add new test_cpu.c test suite in cgroup selftests David Vernet
2022-04-22 17:33 ` [PATCH v2 2/4] cgroup: Add test_cpucg_stats() testcase to cgroup cpu selftests David Vernet
2022-04-22 17:33 ` [PATCH v2 3/4] cgroup: Add test_cpucg_weight_overprovisioned() testcase David Vernet
2024-04-29 6:29 ` Pengfei Xu
2022-04-22 17:33 ` [PATCH v2 4/4] cgroup: Add test_cpucg_weight_underprovisioned() testcase David Vernet
2022-04-22 17:48 ` [PATCH 0/4] cgroup: Introduce cpu controller test suite Tejun Heo
2022-04-22 17:50 ` Peter Zijlstra
2022-04-22 18:40 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-19 21:32 David Vernet
2022-04-21 22:21 ` Tejun Heo
2022-04-22 12:32 ` David Vernet
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=YmL2rt7A6qfiv1X4@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=void@manifault.com \
/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