[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250416140611.17a87271@gandalf.local.home>
Date: Wed, 16 Apr 2025 14:06:11 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Junxuan Liao <ljx@...wisc.edu>, linux-trace-kernel@...r.kernel.org,
linux-kernel@...r.kernel.org, x86@...nel.org, Thomas Gleixner
<tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Dave Hansen
<dave.hansen@...ux.intel.com>, "H. Peter Anvin" <hpa@...or.com>, Masami
Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, "Paul E. McKenney" <paulmck@...nel.org>
Subject: Re: [PATCH] x86/tracing: introduce enter/exit tracepoint pairs for
page faults
On Wed, 16 Apr 2025 14:01:15 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> > Ok, so AFAIU, this gives you how long user page faults take and apparently for
> > someone this is important info.
>
> This was just a simple example. I rather see where in the kernel it happens.
^^^^^^^^^^^^
user space
> I can still use the synthetic events and user stack trace to find where the
> big faults occur.
Powered by blists - more mailing lists