From: Steven Rostedt <rostedt@goodmis.org>
To: Song Liu <song@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
live-patching@vger.kernel.org, mhiramat@kernel.org,
mark.rutland@arm.com, kernel-team@meta.com
Subject: Re: [PATCH v2 07/16] tracepoint: Mark __do_trace_##name() notrace
Date: Thu, 29 Oct 2026 13:47:21 -0400 [thread overview]
Message-ID: <20261029134721.66bb584c@gandalf.local.home> (raw)
In-Reply-To: <CAPhsuW54Tco1Y_khWHeomq_ZTxvDoHFuX77w9cqojuXCrhGKWg@mail.gmail.com>
On Thu, 29 Oct 2026 10:40:57 -0700
Song Liu <song@kernel.org> wrote:
> Hi Steven,
>
> On Wed, Oct 28, 2026 at 6:08 PM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > On Wed, 28 Oct 2026 15:20:37 -0700
> > Song Liu <song@kernel.org> wrote:
> >
> > > Do you plan to apply this set to the trace tree (after the merge window,
> > > I guess)? If not, how should we proceed?
> >
> > I can take it if we get all the necessary acks, or it can go through
> > the BPF tree. Either way is fine with me.
>
> > If you prefer me to take it (as I do have a lot of ftrace specific
> > tests), I'll do it. But I'd like acks from maintainers of all the code
> > this touches.
>
> I think this should go through the ftrace tree. It has very little to do with
> BPF. We discovered the need for this change when building live patches.
>
> Regarding ACKs, it is a bit tricky. For the code we touched in this set,
> there is actually no behavior change at all. OTOH, the real change
> happens to "inline"s that we didn't touch in this set. If such a function
> was left out-of-line by the compiler, it was not traceable before, but is
> traceable after this set. How should we approach this? Maybe we can
> just ask ACKs from the maintainers of all the code touched here.
>
OK, I'll just add it to Linux next around -rc2 then.
-- Steve
next prev parent reply other threads:[~2026-10-29 17:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 1:10 [PATCH v2 00/16] Move notrace from inline to __always_inline Song Liu
2026-10-23 1:10 ` [PATCH v2 01/16] x86/paravirt: Mark native pv_ops helpers notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 02/16] x86: Mark CPU state helpers used by resume and kexec notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 03/16] bpf: Mark bpf_spin_lock helpers notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 04/16] bpf: Mark the BPF trampoline " Song Liu
2026-10-23 1:10 ` [PATCH v2 05/16] bpf: Mark the bpf_mem_alloc fast path " Song Liu
2026-10-23 1:10 ` [PATCH v2 06/16] u64_stats: Mark the update helpers used by BPF notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 07/16] tracepoint: Mark __do_trace_##name() notrace Song Liu
2026-10-23 13:32 ` Steven Rostedt
2026-10-23 18:04 ` Song Liu
2026-10-28 22:20 ` Song Liu
2026-10-29 1:08 ` Steven Rostedt
2026-10-29 17:40 ` Song Liu
2026-10-29 17:47 ` Steven Rostedt [this message]
2026-10-23 1:10 ` [PATCH v2 08/16] srcu: Mark the fast notrace read-side helpers notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 09/16] arm64: Mark the preempt count " Song Liu
2026-10-23 1:10 ` [PATCH v2 10/16] powerpc, csky, mips, sh: Mark the accessors behind current notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 11/16] rcu: Mark the Tiny RCU rcu_is_watching() notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 12/16] tracing: Mark the tracing_gen_ctx helpers notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 13/16] ktime: Mark ktime_to_ns() notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 14/16] kallsyms: Mark the kernel text address checks notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 15/16] uaccess: Mark pagefault_disable() and pagefault_enable() notrace Song Liu
2026-10-23 1:10 ` [PATCH v2 16/16] compiler_types: Move notrace from inline to __always_inline Song Liu
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=20261029134721.66bb584c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=song@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
all inboxes | Powered by JetHome®