public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Nam Cao <namcao@linutronix.de>,
	Gabriele Monaco <gmonaco@redhat.com>,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	john.ogness@linutronix.de,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 17/22] arm64: mm: Add page fault trace points
Date: Tue, 20 May 2025 15:04:54 +0100	[thread overview]
Message-ID: <20250520140453.GA18711@willie-the-truck> (raw)
In-Reply-To: <20250519120837.794f6738@batman.local.home>

On Mon, May 19, 2025 at 12:08:37PM -0400, Steven Rostedt wrote:
> On Mon, 19 May 2025 16:12:39 +0100
> Will Deacon <will@kernel.org> wrote:
> 
> > > Perf events work for perf only. My question is why isn't this a tracepoint
> > > that perf could hook into?  
> > 
> > Well, the perf event came first in this case, so we're stuck with it :/
> 
> I wonder what effort it will take to convert perf events to tracepoints ;-)
> 
> Note, I'm talking about tracepoints and not trace events, where the
> latter is exposed to tracefs and the former is not.
> 
> > 
> > I was hoping we could settle for a generic helper that could emit both
> > the trace event and the perf event (so that the ordering of the two is
> > portable across architectures) but, judging by Nam's reply, the trace
> > event is needed before kprobes gets a look in.
> 
> Perhaps we could add a helper function that does both (perf and
> tracepoint) and hide the implementation from the code that calls it?

Something like that sounds like a good idea, yes.

> But I'm currently still on PTO so I haven't looked at the details yet.

Enjoy!

Will

  reply	other threads:[~2025-05-20 14:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 11:02 [PATCH v6 00/22] RV: Linear temporal logic monitors for RT application Nam Cao
2025-04-30 11:02 ` [PATCH v6 01/22] rv: Add #undef TRACE_INCLUDE_FILE Nam Cao
2025-04-30 11:02 ` [PATCH v6 02/22] printk: Make vprintk_deferred() public Nam Cao
2025-04-30 11:02 ` [PATCH v6 03/22] panic: Add vpanic() Nam Cao
2025-05-05 12:24   ` Petr Mladek
2025-04-30 11:02 ` [PATCH v6 04/22] rv: Let the reactors take care of buffers Nam Cao
2025-05-05 12:25   ` Petr Mladek
2025-04-30 11:02 ` [PATCH v6 05/22] verification/dot2k: Make a separate dot2k_templates/Kconfig_container Nam Cao
2025-04-30 11:02 ` [PATCH v6 06/22] verification/dot2k: Remove __buff_to_string() Nam Cao
2025-04-30 11:02 ` [PATCH v6 07/22] verification/dot2k: Replace is_container() hack with subparsers Nam Cao
2025-04-30 11:02 ` [PATCH v6 08/22] rv: rename CONFIG_DA_MON_EVENTS to CONFIG_RV_MON_EVENTS Nam Cao
2025-04-30 11:02 ` [PATCH v6 09/22] verification/dot2k: Prepare the frontend for LTL inclusion Nam Cao
2025-04-30 11:02 ` [PATCH v6 10/22] Documentation/rv: Prepare monitor synthesis document " Nam Cao
2025-04-30 11:02 ` [PATCH v6 11/22] verification/rvgen: Restructure the templates files Nam Cao
2025-04-30 11:02 ` [PATCH v6 12/22] verification/rvgen: Restructure the classes to prepare for LTL inclusion Nam Cao
2025-04-30 11:02 ` [PATCH v6 13/22] rv: Add support for LTL monitors Nam Cao
2025-05-07 21:00   ` Steven Rostedt
2025-04-30 11:02 ` [PATCH v6 14/22] rv: Add rtapp container monitor Nam Cao
2025-04-30 11:02 ` [PATCH v6 15/22] x86/tracing: Remove redundant trace_pagefault_key Nam Cao
2025-04-30 11:02 ` [PATCH v6 16/22] x86/tracing: Move page fault trace points to generic Nam Cao
2025-05-07 21:03   ` Steven Rostedt
2025-04-30 11:02 ` [PATCH v6 17/22] arm64: mm: Add page fault trace points Nam Cao
2025-05-07 21:23   ` Steven Rostedt
2025-05-16 14:04   ` Will Deacon
2025-05-16 14:42     ` Steven Rostedt
2025-05-19 15:12       ` Will Deacon
2025-05-19 16:08         ` Steven Rostedt
2025-05-20 14:04           ` Will Deacon [this message]
2025-05-16 15:09     ` Nam Cao
2025-05-19 16:17     ` Mark Rutland
2025-05-20 12:32       ` Will Deacon
2025-04-30 11:02 ` [PATCH v6 18/22] riscv: " Nam Cao
2025-04-30 11:02 ` [PATCH v6 19/22] rv: Add rtapp_pagefault monitor Nam Cao
2025-04-30 11:02 ` [PATCH v6 20/22] rv: Add rtapp_sleep monitor Nam Cao
2025-04-30 11:02 ` [PATCH v6 21/22] rv: Add documentation for rtapp monitor Nam Cao
2025-04-30 11:02 ` [PATCH v6 22/22] rv: Allow to configure the number of per-task monitor Nam Cao
2025-04-30 12:17 ` [PATCH v6 00/22] RV: Linear temporal logic monitors for RT application Gabriele Monaco
2025-04-30 19:18   ` Steven Rostedt
2025-08-10 21:12 ` patchwork-bot+linux-riscv

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=20250520140453.GA18711@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=gmonaco@redhat.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=namcao@linutronix.de \
    --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