From: Will Deacon <will@kernel.org>
To: Nam Cao <namcao@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
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 v9 17/22] arm64: mm: Add page fault trace points
Date: Tue, 8 Jul 2025 14:16:16 +0100 [thread overview]
Message-ID: <aG0aIKzxApp9j7X0@willie-the-truck> (raw)
In-Reply-To: <61063f55e2c2df6db69cb63eac9d6653f38fbfbd.1747649899.git.namcao@linutronix.de>
On Mon, May 19, 2025 at 12:27:35PM +0200, Nam Cao wrote:
> Add page fault trace points, which are useful to implement RV monitor which
> watches page faults.
>
> Signed-off-by: Nam Cao <namcao@linutronix.de>
> ---
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: linux-arm-kernel@lists.infradead.org
> ---
> arch/arm64/mm/fault.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
> index ec0a337891dd..d917556869f9 100644
> --- a/arch/arm64/mm/fault.c
> +++ b/arch/arm64/mm/fault.c
> @@ -44,6 +44,9 @@
> #include <asm/tlbflush.h>
> #include <asm/traps.h>
>
> +#define CREATE_TRACE_POINTS
> +#include <trace/events/exceptions.h>
> +
> struct fault_info {
> int (*fn)(unsigned long far, unsigned long esr,
> struct pt_regs *regs);
> @@ -556,6 +559,11 @@ static int __kprobes do_page_fault(unsigned long far, unsigned long esr,
> int si_code;
> int pkey = -1;
>
> + if (user_mode(regs))
> + trace_page_fault_user(addr, regs, esr);
> + else
> + trace_page_fault_kernel(addr, regs, esr);
> +
> if (kprobe_page_fault(regs, esr))
> return 0;
As per the discussion with Steve on v6, I still object to relying on the
arch code to call all these different trace helpers (rv, kprobes, perf)
in the right place and consistently with each other.
In:
https://lore.kernel.org/r/20250519120837.794f6738@batman.local.home
Steve suggested wrapping some of this up in a core function to help with
that.
Will
next prev parent reply other threads:[~2025-07-08 13:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 10:27 [PATCH v9 00/22] RV: Linear temporal logic monitors for RT application Nam Cao
2025-05-19 10:27 ` [PATCH v9 01/22] rv: Add #undef TRACE_INCLUDE_FILE Nam Cao
2025-05-19 10:27 ` [PATCH v9 02/22] printk: Make vprintk_deferred() public Nam Cao
2025-05-19 10:27 ` [PATCH v9 03/22] panic: Add vpanic() Nam Cao
2025-05-19 10:27 ` [PATCH v9 04/22] rv: Let the reactors take care of buffers Nam Cao
2025-05-19 10:27 ` [PATCH v9 05/22] verification/dot2k: Make a separate dot2k_templates/Kconfig_container Nam Cao
2025-05-19 10:27 ` [PATCH v9 06/22] verification/dot2k: Remove __buff_to_string() Nam Cao
2025-05-19 10:27 ` [PATCH v9 07/22] verification/dot2k: Replace is_container() hack with subparsers Nam Cao
2025-05-19 10:27 ` [PATCH v9 08/22] rv: rename CONFIG_DA_MON_EVENTS to CONFIG_RV_MON_EVENTS Nam Cao
2025-05-19 10:27 ` [PATCH v9 09/22] verification/dot2k: Prepare the frontend for LTL inclusion Nam Cao
2025-05-19 10:27 ` [PATCH v9 10/22] Documentation/rv: Prepare monitor synthesis document " Nam Cao
2025-05-19 10:27 ` [PATCH v9 11/22] verification/rvgen: Restructure the templates files Nam Cao
2025-05-19 10:27 ` [PATCH v9 12/22] verification/rvgen: Restructure the classes to prepare for LTL inclusion Nam Cao
2025-05-27 9:15 ` Gabriele Monaco
2025-05-27 9:27 ` Nam Cao
2025-05-27 9:32 ` Gabriele Monaco
2025-05-27 14:39 ` Steven Rostedt
2025-05-19 10:27 ` [PATCH v9 13/22] rv: Add support for LTL monitors Nam Cao
2025-05-19 10:27 ` [PATCH v9 14/22] rv: Add rtapp container monitor Nam Cao
2025-05-19 10:27 ` [PATCH v9 15/22] x86/tracing, x86/mm: Remove redundant trace_pagefault_key Nam Cao
2025-05-19 10:27 ` [PATCH v9 16/22] x86/tracing, x86/mm: Move page fault tracepoints to generic Nam Cao
2025-05-19 10:27 ` [PATCH v9 17/22] arm64: mm: Add page fault trace points Nam Cao
2025-07-08 13:16 ` Will Deacon [this message]
2025-07-08 13:31 ` Nam Cao
2025-05-19 10:27 ` [PATCH v9 18/22] riscv: " Nam Cao
2025-05-19 10:27 ` [PATCH v9 19/22] rv: Add rtapp_pagefault monitor Nam Cao
2025-05-19 10:27 ` [PATCH v9 20/22] rv: Add rtapp_sleep monitor Nam Cao
2025-05-19 10:27 ` [PATCH v9 21/22] rv: Add documentation for rtapp monitor Nam Cao
2025-05-19 10:27 ` [PATCH v9 22/22] rv: Allow to configure the number of per-task monitor Nam Cao
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=aG0aIKzxApp9j7X0@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