From: Nam Cao <namcao@linutronix.de>
To: Junxuan Liao <ljx@cs.wisc.edu>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, 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 v3 RESEND] x86/tracing: introduce enter/exit tracepoint pairs for page faults
Date: Mon, 23 Jun 2025 15:57:18 +0200 [thread overview]
Message-ID: <20250623135718.Zc4hKa-u@linutronix.de> (raw)
In-Reply-To: <2dda8c03-072a-43b2-af0c-bb996d64c388@cs.wisc.edu>
On Sun, Jun 15, 2025 at 07:32:00PM -0500, Junxuan Liao wrote:
> Merge page_fault_{user,kernel}, rename it page_fault_enter, and add
> page_fault_exit. This pair is useful for measuring page fault handling
> latencies.
>
> Add a new field to the merged tracepoints to indicate whether the page
> fault happened in userspace. We no longer need the static key associated,
> since it was used just to avoid checking user_mode when the tracepoints
> were disabled.
(I think) this breaks lttng which uses the old tracepoint names [1]. But
I'm not sure if we should worry about that.
Do you plan to add this to other architectures?
Perhaps it is better to implement the other approach suggested by Frederic
[2], using trace_user_exit/trace_user_enter? So that more architectures are
covered, and avoid breaking user tools?
(Btw, you would need to rebase this patch. The tracepoint has been moved,
and the static key has been deleted.)
Best regards,
Nam
[1] https://github.com/lttng/lttng-modules/blob/master/include/instrumentation/events/arch/x86/exceptions.h#L88C48-L88C63
[2] https://lore.kernel.org/lkml/Z_mO6_m0bV-Q8NEa@pavilion.home/#t
prev parent reply other threads:[~2025-06-23 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 0:32 Junxuan Liao
2025-06-23 13:57 ` Nam Cao [this message]
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=20250623135718.Zc4hKa-u@linutronix.de \
--to=namcao@linutronix.de \
--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
all inboxes | Powered by JetHome®