From: Samir Mulani <samir@linux.ibm.com>
To: ltp@lists.linux.it
Cc: Samir Mulani <samir@linux.ibm.com>
Subject: [LTP] [PATCH 0/2] cgroup: Add tests for cgroupv2 cpu.max.burst
Date: Mon, 28 Sep 2026 07:17:33 +0200 [thread overview]
Message-ID: <20260928051740.591819-1-samir@linux.ibm.com> (raw)
Hi all,
This patch series adds two new testcases to test the cgroupv2 cpu.max.burst
interface:
Patch 1 adds cpu_max_burst01 to test the basic functionality of cpu.max.burst.
It checks default values, read/write boundaries, stat accounting (nr_bursts
and burst_usec in cpu.stat), dynamic updates, and making sure the burst value
is preserved when quota is removed or period is changed.
Patch 2 adds cpu_max_burst_invalid01 to test invalid inputs to cpu.max.burst.
It checks that values like burst > quota, negative values, sum overflow,
garbage strings, and trailing characters are rejected with EINVAL and do
not change the saved burst value.
Both tests are written using the new LTP API and require CONFIG_CFS_BANDWIDTH=y
and the cgroupv2 cpu controller.
Thanks,
Samir Mulani
Samir Mulani (2):
cgroup: Add cgroup_burst01 test
cgroup: Add invalid burst test
runtest/controllers | 2 +
.../kernel/controllers/cgroup/.gitignore | 2 +
.../controllers/cgroup/cpu_max_burst01.c | 650 ++++++++++++++++++
.../cgroup/cpu_max_burst_invalid01.c | 417 +++++++++++
4 files changed, 1071 insertions(+)
create mode 100644 testcases/kernel/controllers/cgroup/cpu_max_burst01.c
create mode 100644 testcases/kernel/controllers/cgroup/cpu_max_burst_invalid01.c
--
2.53.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-09-28 5:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 5:17 Samir Mulani [this message]
2026-09-28 5:17 ` [LTP] [PATCH 1/2] cgroup: Add cgroup_burst01 test Samir Mulani
2026-09-29 7:14 ` [LTP] " linuxtestproject.agent
2026-09-28 5:17 ` [LTP] [PATCH 2/2] cgroup: Add invalid burst test Samir Mulani
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=20260928051740.591819-1-samir@linux.ibm.com \
--to=samir@linux.ibm.com \
--cc=ltp@lists.linux.it \
/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.