All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samir Mulani <samir@linux.ibm.com>
To: ltp@lists.linux.it
Cc: Samir Mulani <samir@linux.ibm.com>
Subject: [LTP] [PATCH v1 0/4] sched/psi: Add tests for PSI interface
Date: Sat, 24 Oct 2026 04:30:40 +0200	[thread overview]
Message-ID: <20261024023044.80055-1-samir@linux.ibm.com> (raw)

This patch series adds four new test cases for the Linux kernel's
Pressure Stall Information (PSI) interface (/proc/pressure/{cpu,memory,io}).

Currently, LTP lacks dedicated test coverage for PSI functionality, trigger
parsing rules, and stall accounting. These tests ensure kernel compliance
and validate PSI behavior.

Test series breakdown:
  1. psi_invalid_trigger01 (1/4):
     Tests trigger input validation in /proc/pressure/memory. Checks that
     invalid trigger strings return EINVAL and valid boundary values succeed.

  2. psi_multiple_trigger01 (2/4):
     Tests that only one trigger is allowed per open file description,
     and second triggers on the same or dup()'d file descriptor fail with EBUSY.

  3. psi_proc_format01 (3/4):
     Validates the file format of /proc/pressure/{cpu,memory,io}, ensuring
     percentages are between 0 and 100, totals never decrease, and CPU full
     stall reports 0.00.

  4. psi_accounting01 (4/4):
     Validates real stall accounting within isolated cgroups (cgroup v2)
     for CPU contention, memory throttling via memory.high, and O_DIRECT
     synchronous block I/O stalls.

Samir Mulani (4):
  sched/psi: Add psi_invalid_trigger01 test
  sched/psi: Add psi_multiple_trigger01 test
  sched/psi: Add psi_proc_format01 test
  sched/psi: Add psi_accounting01 test

 runtest/sched                                 |   5 +
 testcases/kernel/sched/psi/.gitignore         |   4 +
 testcases/kernel/sched/psi/Makefile           |   7 +
 testcases/kernel/sched/psi/psi_accounting01.c | 356 ++++++++++++++++++
 .../kernel/sched/psi/psi_invalid_trigger01.c  | 135 +++++++
 .../kernel/sched/psi/psi_multiple_trigger01.c | 172 +++++++++
 .../kernel/sched/psi/psi_proc_format01.c      | 191 ++++++++++
 7 files changed, 870 insertions(+)
 create mode 100644 testcases/kernel/sched/psi/.gitignore
 create mode 100644 testcases/kernel/sched/psi/Makefile
 create mode 100644 testcases/kernel/sched/psi/psi_accounting01.c
 create mode 100644 testcases/kernel/sched/psi/psi_invalid_trigger01.c
 create mode 100644 testcases/kernel/sched/psi/psi_multiple_trigger01.c
 create mode 100644 testcases/kernel/sched/psi/psi_proc_format01.c

-- 
2.53.0


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2026-10-23 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24  2:30 Samir Mulani [this message]
2026-10-24  2:30 ` [LTP] [PATCH v1 1/4] sched/psi: Add psi_invalid_trigger01 test Samir Mulani
2026-10-23 17:55   ` [LTP] " linuxtestproject.agent
2026-10-24  2:30 ` [LTP] [PATCH v1 2/4] sched/psi: Add psi_multiple_trigger01 test Samir Mulani
2026-10-24  2:30 ` [LTP] [PATCH v1 3/4] sched/psi: Add psi_proc_format01 test Samir Mulani
2026-10-24  2:30 ` [LTP] [PATCH v1 4/4] sched/psi: Add psi_accounting01 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=20261024023044.80055-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.