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>
Subject: [for-next][PATCH 0/5] tracing: Updates for v6.19
Date: Sat, 15 Nov 2025 09:09:10 -0500 [thread overview]
Message-ID: <20251115140910.386662473@kernel.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/for-next
Head SHA1: bc089c47250e8923892873809471e54e05919d80
Steven Rostedt (4):
tracing: Have function graph tracer option funcgraph-irqs be per instance
tracing: Move graph-time out of function graph options
tracing: Have function graph tracer option sleep-time be per instance
tracing: Convert function graph set_flags() to use a switch() statement
Yongliang Gao (1):
trace/pid_list: optimize pid_list->lock contention
----
kernel/trace/fgraph.c | 10 +--
kernel/trace/ftrace.c | 4 +-
kernel/trace/pid_list.c | 30 ++++++---
kernel/trace/pid_list.h | 1 +
kernel/trace/trace.c | 14 +++--
kernel/trace/trace.h | 18 ++++--
kernel/trace/trace_functions_graph.c | 115 ++++++++++++++++++++++++++---------
7 files changed, 137 insertions(+), 55 deletions(-)
next reply other threads:[~2025-11-15 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 14:09 Steven Rostedt [this message]
2025-11-15 14:09 ` [for-next][PATCH 1/5] trace/pid_list: optimize pid_list->lock contention Steven Rostedt
2025-11-15 14:09 ` [for-next][PATCH 2/5] tracing: Have function graph tracer option funcgraph-irqs be per instance Steven Rostedt
2025-11-15 14:09 ` [for-next][PATCH 3/5] tracing: Move graph-time out of function graph options Steven Rostedt
2025-11-15 14:09 ` [for-next][PATCH 4/5] tracing: Have function graph tracer option sleep-time be per instance Steven Rostedt
2025-11-15 14:09 ` [for-next][PATCH 5/5] tracing: Convert function graph set_flags() to use a switch() statement 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=20251115140910.386662473@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 \
/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.