From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Junxuan Liao <ljx@cs.wisc.edu>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH] x86/tracing: introduce enter/exit tracepoint pairs for page faults
Date: Mon, 14 Apr 2025 18:20:50 -0400 [thread overview]
Message-ID: <20250414182050.213480aa@gandalf.local.home> (raw)
In-Reply-To: <20250414205441.GGZ_12Eew18bGcPTG0@fat_crate.local>
On Mon, 14 Apr 2025 22:54:41 +0200
Borislav Petkov <bp@alien8.de> wrote:
> On Mon, Apr 14, 2025 at 03:35:41PM -0500, Junxuan Liao wrote:
> > Rename page_fault_{user,kernel} to page_fault_{user,kernel}_enter, and
> > add the exit counterparts. This might be useful for measuring page fault
> ^^^^^^^^^^^^^^^^
>
> Well, come back when it really becomes useful.
It's useful for me ;-)
# cd /sys/kernel/tracing
# echo 's:user_faults u64 delta;' >> dynamic_events
# echo 'hist:keys=common_pid:ts0=common_timestamp.usecs' >> events/exceptions/page_fault_user_enter/trigger
# echo 'hist:keys=common_pid:delta=common_timestamp.usecs-$ts0:onmatch(exceptions.page_fault_user_enter).trace(user_faults,$delta)' >> events/exceptions/page_fault_user_exit/trigger
# cd /work/git/trace-cmd.git
# echo 'hist:keys=delta.log2:sort=delta if COMM == "cc1"' > /sys/kernel/tracing/events/synthetic/user_faults/trigger
# make
[..]
# cat /sys/kernel/tracing/events/synthetic/user_faults/hist
# event histogram
#
# trigger info: hist:keys=delta.log2:vals=hitcount:sort=delta.log2:size=2048 if COMM == "cc1" [active]
#
{ delta: ~ 2^0 } hitcount: 1
{ delta: ~ 2^1 } hitcount: 334
{ delta: ~ 2^2 } hitcount: 4090
{ delta: ~ 2^3 } hitcount: 86037
{ delta: ~ 2^4 } hitcount: 108790
{ delta: ~ 2^5 } hitcount: 27387
{ delta: ~ 2^6 } hitcount: 6015
{ delta: ~ 2^7 } hitcount: 481
{ delta: ~ 2^8 } hitcount: 134
{ delta: ~ 2^9 } hitcount: 74
{ delta: ~ 2^10 } hitcount: 54
{ delta: ~ 2^11 } hitcount: 6
Totals:
Hits: 233403
Entries: 12
Dropped: 0
The above shows a histogram in microseconds where the buckets increase in a
power of two. The biggest bucket is between 2^4 (16) and 2^5 (32) microseconds
with 108790 hits.
The longest bucket of 2^11 (2ms) to 2^12 (4ms) had 6 hits.
And when sframes is supported, it will be able to show the user space stack
trace of where the longest page faults occur.
-- Steve
next prev parent reply other threads:[~2025-04-14 22:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 20:35 [PATCH] x86/tracing: introduce enter/exit tracepoint pairs for page faults Junxuan Liao
2025-04-14 20:42 ` Dave Hansen
2025-04-14 20:57 ` Steven Rostedt
2025-04-14 23:14 ` Junxuan Liao
2025-04-14 23:22 ` Junxuan Liao
2025-04-14 23:37 ` Dave Hansen
2025-04-14 23:43 ` Steven Rostedt
2025-04-14 23:48 ` Junxuan Liao
2025-04-14 20:54 ` Borislav Petkov
2025-04-14 22:20 ` Steven Rostedt [this message]
2025-04-15 1:23 ` Junxuan Liao
2025-04-16 17:47 ` Borislav Petkov
2025-04-16 18:01 ` Steven Rostedt
2025-04-16 18:06 ` Steven Rostedt
2025-04-18 21:39 ` Borislav Petkov
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=20250414182050.213480aa@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=ljx@cs.wisc.edu \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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