From: Xuewen Yan <xuewen.yan@unisoc.com>
To: <rostedt@goodmis.org>, <surenb@google.com>, <hannes@cmpxchg.org>,
<peterz@infradead.org>, <mingo@redhat.com>
Cc: <mhiramat@kernel.org>, <mathieu.desnoyers@efficios.com>,
<juri.lelli@redhat.com>, <vincent.guittot@linaro.org>,
<dietmar.eggemann@arm.com>, <bsegall@google.com>,
<andrii@kernel.org>, <vschneid@redhat.com>,
<linux-kernel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>, <yuming.han@unisoc.com>,
<ke.wang@unisoc.com>, <xuewen.yan94@gmail.com>
Subject: [RFC PATCH] sched: psi: Add psi events trace point
Date: Thu, 14 Aug 2025 15:07:19 +0800 [thread overview]
Message-ID: <20250814070719.865-1-xuewen.yan@unisoc.com> (raw)
Add trace point to psi triggers. This is useful to
observe the psi events in the kernel space.
Signed-off-by: Xuewen Yan <xuewen.yan@unisoc.com>
---
include/trace/events/sched.h | 5 +++++
kernel/sched/psi.c | 2 ++
2 files changed, 7 insertions(+)
diff --git a/include/trace/events/sched.h b/include/trace/events/sched.h
index 7b2645b50e78..c23cb2bc76fd 100644
--- a/include/trace/events/sched.h
+++ b/include/trace/events/sched.h
@@ -896,6 +896,11 @@ DECLARE_TRACE(sched_set_need_resched,
TP_PROTO(struct task_struct *tsk, int cpu, int tif),
TP_ARGS(tsk, cpu, tif));
+struct psi_trigger *t
+DECLARE_TRACE(psi_event,
+ TP_PROTO(struct psi_trigger *t),
+ TP_ARGS(t));
+
#endif /* _TRACE_SCHED_H */
/* This part must be outside protection */
diff --git a/kernel/sched/psi.c b/kernel/sched/psi.c
index 59fdb7ebbf22..268fc1b9cf1d 100644
--- a/kernel/sched/psi.c
+++ b/kernel/sched/psi.c
@@ -509,6 +509,8 @@ static void update_triggers(struct psi_group *group, u64 now,
if (now < t->last_event_time + t->win.size)
continue;
+ trace_psi_event_tp(t);
+
/* Generate an event */
if (cmpxchg(&t->event, 0, 1) == 0) {
if (t->of)
--
2.25.1
next reply other threads:[~2025-08-14 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 7:07 Xuewen Yan [this message]
2025-08-14 13:55 ` Johannes Weiner
2025-08-15 6:54 ` Xuewen Yan
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=20250814070719.865-1-xuewen.yan@unisoc.com \
--to=xuewen.yan@unisoc.com \
--cc=andrii@kernel.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--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 \
--cc=xuewen.yan94@gmail.com \
--cc=yuming.han@unisoc.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®