From: Hui Su <sh_def@163.com>
To: hannes@cmpxchg.org, surenb@google.com, peterz@infradead.org,
mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org
Cc: dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
sh_def@163.com
Subject: [PATCH 0/2] sched/psi: Preserve RT poll notifications
Date: Mon, 19 Oct 2026 19:46:57 +0900 [thread overview]
Message-ID: <20261019104700.3296133-1-sh_def@163.com> (raw)
Privileged RT trigger registration can consume pressure accounting before
existing triggers evaluate it. A separate worker shutdown path can leave a
rate-limited event pending after active polling expires.
Patch 1 preserves registration-time pressure changes for existing triggers
and advances the consumed total after due evaluation.
Patch 2 derives pending notification deadlines from the trigger list instead
of storing a duplicate deadline in psi_group. It preserves pending trigger
windows, resumes active polling when watched pressure returns, and lets the
worker return to idle after the notification is delivered.
Testing:
- x86_64 KASAN/lockdep KUnit: candidate PSI 10/10 passed; baseline PSI had
1/10 pass and 9 candidate-dependent failures. Refcount tests passed 4/4
on both sides; no KASAN report.
- QEMU cgroup PSI_POLL: baseline pressure qualified but the second long event
was absent by 2500 ms; the worker log showed pending=1 and timer_pending=0.
Candidate delivered the second event after 2004.4 ms; pending cleared and
the worker returned to idle. Both runs had zero quiet-period pressure and
no unexpected third event.
Hui Su (2):
sched/psi: Preserve pressure accounting across RT trigger registration
sched/psi: Deliver pending RT poll events after polling expires
include/linux/psi_types.h | 1 +
kernel/sched/psi.c | 206 +++++++++++++++++++++++++++++---------
2 files changed, 157 insertions(+), 50 deletions(-)
base-commit: b99b7f60c5b473d374c68b53753153b4aa9e0702
--
2.55.0
next reply other threads:[~2026-10-19 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 10:46 Hui Su [this message]
2026-10-19 10:46 ` [PATCH 1/2] sched/psi: Preserve pressure accounting across RT trigger registration Hui Su
2026-10-19 10:46 ` [PATCH 2/2] sched/psi: Deliver pending RT poll events after polling expires Hui Su
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=20261019104700.3296133-1-sh_def@163.com \
--to=sh_def@163.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=surenb@google.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®