From: Steven Rostedt <rostedt@goodmis.org>
To: Junxuan Liao <ljx@cs.wisc.edu>
Cc: Frederic Weisbecker <frederic@kernel.org>,
"Paul E. McKenney" <paulmck@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: Thu, 10 Apr 2025 15:05:55 -0400 [thread overview]
Message-ID: <20250410150555.7797d195@gandalf.local.home> (raw)
In-Reply-To: <9e2ac1e3-d07d-4f17-970e-6b7a5248a5bb@cs.wisc.edu>
On Thu, 10 Apr 2025 13:51:39 -0500
Junxuan Liao <ljx@cs.wisc.edu> wrote:
> Hi all,
>
> From what I can tell, tracepoints context_tracking:user_enter and
> user_exit might be useful for performance analysis. e.g. Figuring out how
> much time is spent handling page faults or in system calls. However
> context tracking is by default inactive and the only way to enable it is
> to turn on nohz_full for some CPUs.
>
> Is it a good idea to support turning on and off context tracking through
> some interface accessible from the userspace?
>
I think the best thing to do is to add trace events in all areas that enter
and exit the kernel normally (where noinstr is turned off). There's already
one for page faults on entry. It's been on my todo list to add one for page
fault exit (as I do care for how long they last.
I believe the irq vectors also have entry and exits trace events.
What else is missing?
-- Steve
next prev parent reply other threads:[~2025-04-10 19:04 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 [this message]
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
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=20250410150555.7797d195@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=frederic@kernel.org \
--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=paulmck@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