All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Vincent Donnefort <vdonnefort@google.com>,
	arnd@arndb.de, nathan@kernel.org,
	linux-trace-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
	kernel-team@android.com
Subject: Re: [PATCH v3] tracing: Generate undef symbols allowlist for simple_ring_buffer
Date: Tue, 17 Mar 2026 09:04:27 +0000	[thread overview]
Message-ID: <86qzpi6d44.wl-maz@kernel.org> (raw)
In-Reply-To: <20260316100929.5402a335@gandalf.local.home>

On Mon, 16 Mar 2026 14:09:29 +0000,
Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> On Mon, 16 Mar 2026 09:28:45 +0000
> Vincent Donnefort <vdonnefort@google.com> wrote:
> 
> > Compiler and tooling-generated symbols are difficult to maintain
> > across all supported architectures. Make the allowlist more robust by
> > replacing the harcoded list with a mechanism that automatically detects
> > these symbols.
> > 
> > This mechanism generates a C function designed to trigger common
> > compiler-inserted symbols.
> > 
> > Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
> > Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> > Tested-by: Nathan Chancellor <nathan@kernel.org>
> 
> I take it that Marc will take this?

Yup, now merged.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2026-03-17  9:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16  9:28 [PATCH v3] tracing: Generate undef symbols allowlist for simple_ring_buffer Vincent Donnefort
2026-03-16 11:06 ` Arnd Bergmann
2026-03-16 14:09 ` Steven Rostedt
2026-03-17  9:04   ` Marc Zyngier [this message]
2026-03-16 20:47 ` Arnd Bergmann
2026-03-16 20:48   ` Arnd Bergmann
2026-03-17  9:04     ` Marc Zyngier
2026-03-17  9:03 ` Marc Zyngier

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=86qzpi6d44.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=arnd@arndb.de \
    --cc=kernel-team@android.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=vdonnefort@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.