From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: [for-next][PATCH 0/4] tracing: Updates for v6.20
Date: Fri, 30 Jan 2026 10:46:07 -0500 [thread overview]
Message-ID: <20260130154607.755725833@kernel.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/for-next
Head SHA1: a46023d5616ed3ed781e56ca93400eb9490e3646
Paul E. McKenney (1):
srcu: Fix warning to permit SRCU-fast readers in NMI handlers
Steven Rostedt (3):
tracing: perf: Have perf tracepoint callbacks always disable preemption
bpf: Have __bpf_trace_run() use rcu_read_lock_dont_migrate()
tracing: Guard __DECLARE_TRACE() use of __DO_TRACE_CALL() with SRCU-fast
----
include/linux/tracepoint.h | 9 +++++----
include/trace/perf.h | 4 ++--
include/trace/trace_events.h | 4 ++--
kernel/rcu/srcutree.c | 3 ++-
kernel/trace/bpf_trace.c | 5 ++---
kernel/tracepoint.c | 18 ++++++++++++++----
6 files changed, 27 insertions(+), 16 deletions(-)
next reply other threads:[~2026-01-30 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 15:46 Steven Rostedt [this message]
2026-01-30 15:46 ` [for-next][PATCH 1/4] tracing: perf: Have perf tracepoint callbacks always disable preemption Steven Rostedt
2026-01-30 15:46 ` [for-next][PATCH 2/4] bpf: Have __bpf_trace_run() use rcu_read_lock_dont_migrate() Steven Rostedt
2026-01-30 15:46 ` [for-next][PATCH 3/4] srcu: Fix warning to permit SRCU-fast readers in NMI handlers Steven Rostedt
2026-01-30 15:51 ` Boqun Feng
2026-01-30 17:17 ` Paul E. McKenney
2026-01-30 17:28 ` Steven Rostedt
2026-01-30 15:46 ` [for-next][PATCH 4/4] tracing: Guard __DECLARE_TRACE() use of __DO_TRACE_CALL() with SRCU-fast Steven Rostedt
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=20260130154607.755725833@kernel.org \
--to=rostedt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@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 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.