From: Dave Hansen <dave.hansen@intel.com>
To: Junxuan Liao <ljx@cs.wisc.edu>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Steven Rostedt <rostedt@goodmis.org>,
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 13:42:23 -0700 [thread overview]
Message-ID: <214abd94-7fb3-4515-a1ae-a60abe81af88@intel.com> (raw)
In-Reply-To: <e7d4cd81-c0a5-446c-95d2-6142d660c15b@cs.wisc.edu>
On 4/14/25 13:35, 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
> handling latencies.
Is there a reason kprobes don't work for this?
next prev parent reply other threads:[~2025-04-14 20:42 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 [this message]
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
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=214abd94-7fb3-4515-a1ae-a60abe81af88@intel.com \
--to=dave.hansen@intel.com \
--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=rostedt@goodmis.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