linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v3 0/5] tracepoints: Add warnings for unused tracepoints and trace events
@ 2025-07-22 15:20 Steven Rostedt
  2025-07-22 15:20 ` [PATCH v3 1/5] tracepoints: Add verifier that makes sure all defined tracepoints are used Steven Rostedt
                   ` (4 more replies)
  0 siblings, 5 replies; 9+ messages in thread
From: Steven Rostedt @ 2025-07-22 15:20 UTC (permalink / raw)
  To: linux-kernel, linux-trace-kernel, linux-kbuild, llvm
  Cc: Masami Hiramatsu, Mark Rutland, Mathieu Desnoyers, Andrew Morton,
	Arnd Bergmann, Masahiro Yamada, Nathan Chancellor, Nicolas Schier,
	Nick Desaulniers, Catalin Marinas, Linus Torvalds

Every trace event can take up to 5K of memory in text and metadata regardless
if they are used or not. Trace events should not be created if they are not
used.  Currently there's over a hundred events in the kernel that are defined
but unused, either because their callers were removed without removing the
trace event with it, or a config hides the trace event caller but not the
trace event itself. And in some cases, trace events were simply added but were
never called for whatever reason. The number of unused trace events continues
to grow.

This patch series aims to fix this.

The first patch creates a new section called __tracepoint_check, where all
callers of a tracepoint creates a variable that is placed in this section with
a pointer to the tracepoint they use. Then on boot up, it iterates this
section and will modify the tracepoint's "func" field to a value of 1 (all
tracepoints "func" fields are initialized to NULL and is only set when they
are registered). This takes place before any tracepoint can be registered.

Then each tracepoint is iterated on and if any tracepoint does not have its
"func" field set to 1 a warning is triggered and every tracepoint that doesn't
have that field set is printed. The "func" field is then reset back to NULL.

The second patch modifies scripts/sorttable.c to read the __tracepoint_check
section. It sorts it, and then reads the __tracepoint_ptr section that has all
compiled in tracepoints. It makes sure that every tracepoint is found in the
check section and if not, it prints a warning message about it. This lists the
missing tracepoints at build time.

The third patch updates sorttable to work for arm64 when compiled with gcc. As
gcc's arm64 build doesn't put addresses in their section but saves them off in
the RELA sections. This mostly takes the work done that was needed to do the
mcount sorting at boot up on arm64.

The fourth patch adds EXPORT_TRACEPOINT() to the __tracepoint_check section as
well. There was several locations that adds tracepoints in the kernel proper
that are only used in modules. It was getting quite complex trying to move
things around that I just decided to make any tracepoint in a
EXPORT_TRACEPOINT "used". I'm using the analogy of static and global
functions. An unused static function gets a warning but an unused global one
does not.

The last patch updates the trace_ftrace_test_filter boot up self test. That
selftest creates a trace event to run a bunch of filter tests on it without
actually calling the tracepoint. To quiet the warning, the selftest tracepoint
is called within a if (!trace_<event>_enabled()) section, where it will not be
optimized out, nor will it be called.

Changes since v2: https://lore.kernel.org/all/20250612235827.011358765@goodmis.org/

- Fixed some typos in the above change log, and in comments within patches.

- Have the build warning on unused events be default off. There is still too
  many events that are unused to make a warning a default. But after all
  current offenders are fixed, I plan on making it default enabled to prevent
  new trace events from being added when they are unused.

Steven Rostedt (5):
      tracepoints: Add verifier that makes sure all defined tracepoints are used
      tracing: sorttable: Add a tracepoint verification check at build time
      tracing: sorttable: Find unused tracepoints for arm64 that uses reloc for address
      tracepoint: Do not warn for unused event that is exported
      tracing: Call trace_ftrace_test_filter() for the event

----
 include/asm-generic/vmlinux.lds.h  |   1 +
 include/linux/tracepoint.h         |  13 ++
 kernel/trace/Kconfig               |  30 +++
 kernel/trace/trace_events_filter.c |   4 +
 kernel/tracepoint.c                |  26 +++
 scripts/Makefile                   |   4 +
 scripts/sorttable.c                | 444 ++++++++++++++++++++++++++++++-------
 7 files changed, 436 insertions(+), 86 deletions(-)

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2025-07-22 18:19 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-07-22 15:20 [PATCH v3 0/5] tracepoints: Add warnings for unused tracepoints and trace events Steven Rostedt
2025-07-22 15:20 ` [PATCH v3 1/5] tracepoints: Add verifier that makes sure all defined tracepoints are used Steven Rostedt
2025-07-22 16:16   ` Linus Torvalds
2025-07-22 17:04     ` Steven Rostedt
2025-07-22 18:12       ` Linus Torvalds
2025-07-22 15:20 ` [PATCH v3 2/5] tracing: sorttable: Add a tracepoint verification check at build time Steven Rostedt
2025-07-22 15:20 ` [PATCH v3 3/5] tracing: sorttable: Find unused tracepoints for arm64 that uses reloc for address Steven Rostedt
2025-07-22 15:20 ` [PATCH v3 4/5] tracepoint: Do not warn for unused event that is exported Steven Rostedt
2025-07-22 15:20 ` [PATCH v3 5/5] tracing: Call trace_ftrace_test_filter() for the event Steven Rostedt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).