[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a90f134-82ac-428e-be5b-916cf031157e@cs.wisc.edu>
Date: Fri, 11 Apr 2025 12:41:37 -0500
From: Junxuan Liao <ljx@...wisc.edu>
To: Steven Rostedt <rostedt@...dmis.org>,
"Paul E. McKenney" <paulmck@...nel.org>
Cc: Frederic Weisbecker <frederic@...nel.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: Interface for enabling context tracking
>> 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
Powered by blists - more mailing lists