Linux Trace Kernel
 help / color / mirror / Atom feed
From: Junxuan Liao <ljx@cs.wisc.edu>
To: Steven Rostedt <rostedt@goodmis.org>,
	"Paul E. McKenney" <paulmck@kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: Interface for enabling context tracking
Date: Fri, 11 Apr 2025 12:41:37 -0500	[thread overview]
Message-ID: <4a90f134-82ac-428e-be5b-916cf031157e@cs.wisc.edu> (raw)
In-Reply-To: <20250410153244.6b20e328@gandalf.local.home>


>> Are you interested in working on joining the noble quest of getting the
>> rest of the nohz_full support in place?  (Full disclosure: This stuff
>> is non-trivial.)
> 
> I believe the request is more of just tracing entry and exit from the
> kernel, which just needs a simple trace event at the border crossings.

Yeah I'm more interested in just tracing this for now.

> It's been on my todo list to add one for page
> fault exit (as I do care for how long they last.

I've added a tracepoint similar to page_fault_user for that but I'm not
sure if it's the best way to do it. Should I send a patch for review?

Thanks,
Junxuan

  reply	other threads:[~2025-04-11 18:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 18:51 Interface for enabling context tracking Junxuan Liao
2025-04-10 19:05 ` Steven Rostedt
2025-04-10 20:31   ` Junxuan Liao
2025-04-17 19:10   ` Junxuan Liao
2025-04-17 20:34     ` Steven Rostedt
2025-04-10 19:10 ` Paul E. McKenney
2025-04-10 19:32   ` Steven Rostedt
2025-04-11 17:41     ` Junxuan Liao [this message]
2025-04-11 21:51       ` Frederic Weisbecker

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=4a90f134-82ac-428e-be5b-916cf031157e@cs.wisc.edu \
    --to=ljx@cs.wisc.edu \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rostedt@goodmis.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