linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@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, Petr Mladek <pmladek@suse.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
	Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH v8 00/22] RV: Linear temporal logic monitors for RT application
Date: Fri, 16 May 2025 11:12:37 +0200	[thread overview]
Message-ID: <aCcBhY3zYpuH_oIr@gmail.com> (raw)
In-Reply-To: <20250516085522.g9Uq2WBN@linutronix.de>


* Nam Cao <namcao@linutronix.de> wrote:

> On Fri, May 16, 2025 at 10:21:36AM +0200, Ingo Molnar wrote:
> > 
> > * Nam Cao <namcao@linutronix.de> wrote:
> > 
> > > Nam Cao (22):
> > >   x86/tracing: Remove redundant trace_pagefault_key
> > >   x86/tracing: Move page fault trace points to generic
> > 
> > Does the renaming of the tracepoint class from 'x86_exceptions' to
> > 'exceptions' have any negative effects on tooling?
> 
> No, tracepoint class name doesn't affect userspace. The tracepoints' names
> seen from userspace are the same after the patches:
> 	exceptions:page_fault_kernel
> 	exceptions:page_fault_user

Perfect, thank you!

Since there's been no new review feedback about these two patches since 
-v5, I've applied them to tip:x86/debug, with a v6.15-rc6 base, because 
IMO they make sense independently of your series as well.

Thanks,

	Ingo

  parent reply	other threads:[~2025-05-16  9:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 10:50 [PATCH v8 00/22] RV: Linear temporal logic monitors for RT application Nam Cao
2025-05-12 10:50 ` [PATCH v8 01/22] rv: Add #undef TRACE_INCLUDE_FILE Nam Cao
2025-05-12 10:50 ` [PATCH v8 02/22] printk: Make vprintk_deferred() public Nam Cao
2025-05-12 10:50 ` [PATCH v8 03/22] panic: Add vpanic() Nam Cao
2025-05-12 10:50 ` [PATCH v8 04/22] rv: Let the reactors take care of buffers Nam Cao
2025-05-12 10:50 ` [PATCH v8 05/22] verification/dot2k: Make a separate dot2k_templates/Kconfig_container Nam Cao
2025-05-12 10:50 ` [PATCH v8 06/22] verification/dot2k: Remove __buff_to_string() Nam Cao
2025-05-12 10:50 ` [PATCH v8 07/22] verification/dot2k: Replace is_container() hack with subparsers Nam Cao
2025-05-12 10:50 ` [PATCH v8 08/22] rv: rename CONFIG_DA_MON_EVENTS to CONFIG_RV_MON_EVENTS Nam Cao
2025-05-12 10:50 ` [PATCH v8 09/22] verification/dot2k: Prepare the frontend for LTL inclusion Nam Cao
2025-05-12 10:50 ` [PATCH v8 10/22] Documentation/rv: Prepare monitor synthesis document " Nam Cao
2025-05-12 10:50 ` [PATCH v8 11/22] verification/rvgen: Restructure the templates files Nam Cao
2025-05-12 10:50 ` [PATCH v8 12/22] verification/rvgen: Restructure the classes to prepare for LTL inclusion Nam Cao
2025-05-12 10:50 ` [PATCH v8 13/22] rv: Add support for LTL monitors Nam Cao
2025-05-12 10:50 ` [PATCH v8 14/22] rv: Add rtapp container monitor Nam Cao
2025-05-12 10:50 ` [PATCH v8 15/22] x86/tracing: Remove redundant trace_pagefault_key Nam Cao
2025-05-12 10:50 ` [PATCH v8 16/22] x86/tracing: Move page fault trace points to generic Nam Cao
2025-05-12 10:51 ` [PATCH v8 17/22] arm64: mm: Add page fault trace points Nam Cao
2025-05-19 14:49   ` Catalin Marinas
2025-05-20 12:25     ` Nam Cao
2025-05-20 14:15       ` Catalin Marinas
2025-05-21  9:03         ` Nam Cao
2025-05-12 10:51 ` [PATCH v8 18/22] riscv: " Nam Cao
2025-05-12 10:51 ` [PATCH v8 19/22] rv: Add rtapp_pagefault monitor Nam Cao
2025-05-12 10:51 ` [PATCH v8 20/22] rv: Add rtapp_sleep monitor Nam Cao
2025-05-16 16:31   ` Gabriele Monaco
2025-05-19  7:04     ` Nam Cao
2025-05-19  7:54       ` Gabriele Monaco
2025-05-12 10:51 ` [PATCH v8 21/22] rv: Add documentation for rtapp monitor Nam Cao
2025-05-12 10:51 ` [PATCH v8 22/22] rv: Allow to configure the number of per-task monitor Nam Cao
2025-05-16  8:21 ` [PATCH v8 00/22] RV: Linear temporal logic monitors for RT application Ingo Molnar
2025-05-16  8:55   ` Nam Cao
2025-05-16  9:07     ` Nam Cao
2025-05-16  9:12     ` Ingo Molnar [this message]
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=aCcBhY3zYpuH_oIr@gmail.com \
    --to=mingo@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=gmonaco@redhat.com \
    --cc=hpa@zytor.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).