Linux Trace Kernel
 help / color / mirror / Atom feed
From: Junxuan Liao <ljx@cs.wisc.edu>
To: Steven Rostedt <rostedt@goodmis.org>,
	Dave Hansen <dave.hansen@intel.com>
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>,
	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:48:32 -0500	[thread overview]
Message-ID: <5fd0a429-95b8-4ed6-9e2a-83887b40bf54@cs.wisc.edu> (raw)
In-Reply-To: <20250414194346.060f96c6@gandalf.local.home>

>>> I think it might be good to add a field to the tracepoints to indicate
>>> whether it's in user space or not.  
>>
>> seems highly superior to having two sets of tracepoints and static keys.
> 
> I agree.

I'll implement this and delete the extra stuff then.

Thanks,
Junxuan

  reply	other threads:[~2025-04-14 23:49 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 [this message]
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=5fd0a429-95b8-4ed6-9e2a-83887b40bf54@cs.wisc.edu \
    --to=ljx@cs.wisc.edu \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.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=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