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 16:37:19 -0700 [thread overview]
Message-ID: <d64ec287-c85e-4b50-beac-4517462882f6@intel.com> (raw)
In-Reply-To: <41e7d947-d59f-41a9-a540-d3c07e4678c4@cs.wisc.edu>
On 4/14/25 16:22, Junxuan Liao wrote:
> On 4/14/25 6:14 PM, Junxuan Liao wrote:
>> Do people find separate user/kernel tracepoints useful? For me, I can
>> check regs in eBPF tracing code instead.
> I think it might be good to add a field to the tracepoints to indicate
> whether it's in user space or not.
Sounds sane to me. Doing something like this:
TP_STRUCT__entry(
__field( unsigned long, address )
__field( unsigned long, ip )
+ __field( bool , user_mode)
__field( unsigned long, error_code )
),
TP_fast_assign(
__entry->address = address;
__entry->ip = regs->ip;
+ __entry->user_mode = user_mode(regs);
__entry->error_code = error_code;
),
seems highly superior to having two sets of tracepoints and static keys.
next prev parent reply other threads:[~2025-04-14 23:37 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 [this message]
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=d64ec287-c85e-4b50-beac-4517462882f6@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