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 10:21:36 +0200 [thread overview]
Message-ID: <aCb1kBEkiriPbMo4@gmail.com> (raw)
In-Reply-To: <cover.1747046848.git.namcao@linutronix.de>
* 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?
Thanks,
Ingo
next prev parent reply other threads:[~2025-05-16 8:25 UTC|newest]
Thread overview: 11+ 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: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-16 8:21 ` Ingo Molnar [this message]
2025-05-16 8:55 ` [PATCH v8 00/22] RV: Linear temporal logic monitors for RT application Nam Cao
2025-05-16 9:07 ` Nam Cao
2025-05-16 9:12 ` Ingo Molnar
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=aCb1kBEkiriPbMo4@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).