From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mark Rutland <mark.rutland@arm.com>,
Artem Sadovnikov <a.sadovnikov@ispras.ru>
Subject: [GIT PULL] ftrace: Changes for v6.17
Date: Tue, 29 Jul 2025 14:42:26 -0400 [thread overview]
Message-ID: <20250729144226.6b72dca7@batman.local.home> (raw)
Linus,
ftrace changes for v6.17:
- Keep track of when fgraph_ops are registered or not
Keep accounting of when fgraph_ops are registered as if a fgraph_ops is
registered twice it can mess up the accounting and it will not work as
expected later. Trigger a warning if something registers it twice as to
catch bugs before they are found by things just not working as expected.
- Make DYNAMIC_FTRACE always enabled for architectures that support it
As static ftrace (where all functions are always traced) is very expensive
and only exists to help architectures support ftrace, do not make it an
option. As soon as an architecture supports DYNAMIC_FTRACE make it use it.
This simplifies the code.
- Remove redundant config HAVE_FTRACE_MCOUNT_RECORD
The CONFIG_HAVE_FTRACE_MCOUNT was added to help simplify the
DYNAMIC_FTRACE work, but now every architecture that implements
DYNAMIC_FTRACE also has HAVE_FTRACE_MCOUNT set too, making it redundant
with the HAVE_DYNAMIC_FTRACE.
- Make pid_ptr string size match the comment
In print_graph_proc() the pid_ptr string is of size 11, but the comment says
/* sign + log10(MAX_INT) + '\0' */ which is actually 12.
Please pull the latest ftrace-v6.17 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
ftrace-v6.17
Tag SHA1: 58cc39c90ea0e6a1213b565a4859ed6f2a9a0b1a
Head SHA1: 4d6d0a6263babf7c43faa55de4fa3c6637dec624
Artem Sadovnikov (1):
fgraph: Make pid_str size match the comment
Steven Rostedt (3):
fgraph: Keep track of when fgraph_ops are registered or not
ftrace: Make DYNAMIC_FTRACE always enabled for architectures that support it
tracing: Remove redundant config HAVE_FTRACE_MCOUNT_RECORD
----
Documentation/trace/ftrace-design.rst | 12 ++++--------
arch/arm/Kconfig | 1 -
arch/arm64/Kconfig | 1 -
arch/csky/Kconfig | 1 -
arch/loongarch/Kconfig | 1 -
arch/microblaze/Kconfig | 1 -
arch/mips/Kconfig | 1 -
arch/parisc/Kconfig | 1 -
arch/powerpc/Kconfig | 1 -
arch/riscv/Kconfig | 1 -
arch/s390/Kconfig | 1 -
arch/sh/Kconfig | 1 -
arch/sparc/Kconfig | 1 -
arch/x86/Kconfig | 1 -
include/asm-generic/vmlinux.lds.h | 2 +-
include/linux/ftrace.h | 2 +-
include/linux/kernel.h | 6 +++---
include/linux/module.h | 2 +-
kernel/module/main.c | 2 +-
kernel/trace/Kconfig | 20 +++++---------------
kernel/trace/fgraph.c | 16 +++++++++++++---
kernel/trace/ftrace.c | 4 ----
kernel/trace/trace_functions_graph.c | 2 +-
scripts/recordmcount.pl | 2 +-
24 files changed, 31 insertions(+), 52 deletions(-)
---------------------------
next reply other threads:[~2025-07-29 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 18:42 Steven Rostedt [this message]
2025-07-30 23:15 ` Linus Torvalds
2025-07-31 11:53 ` Steven Rostedt
2025-07-31 11:55 ` Steven Rostedt
2025-07-31 0:35 ` pr-tracker-bot
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=20250729144226.6b72dca7@batman.local.home \
--to=rostedt@goodmis.org \
--cc=a.sadovnikov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=torvalds@linux-foundation.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®