TRACE-CMD-LIST(1)

✨ trace-cmd-list ✨ (that's the TRACE-CMD-LIST(1) page, bestie, from the libtracefs manual 💖)

Okay so picture this: you just wanna know what your machine's ftrace setup is actually giving, right? That's literally this whole command. 🫶

🌸 SYNOPSIS 🌸

trace-cmd list [OPTIONS]

💅 DESCRIPTION 💅

trace-cmd(1) list shows you the available plugins, events, or Ftrace options that are configured on the machine you're sitting at right now. No cap.

And here's the cute part — if you give it no option at all, it just dumps everything to standard output: all plugins, event systems, events, and Ftrace options. The whole buffet. 🍓

🎀 OPTIONS 🎀

• -e [regex] — lists the available events that are enabled on the local system. It takes an optional argument that uses regcomp(3) expressions to search. Obsessed with a good regex, ngl:

trace-cmd list -e '^sys.*'

• -F — used with -e regex to show the fields of the event. 👑
• --full — used with -F, and it shows the "print fmt" of the event along with the fields. The full lore, basically.
• -l — used with -e regex to show those events filters.
• -R — used with -e regex to show those events triggers.
• -s — lists the available event systems. ✨
• -t — lists the available tracers that are enabled on the local system.
• -p — same as -t, and it's only there for legacy purposes. Vintage, iconic, but like… just use -t. 💀
• -o — lists the available Ftrace options that are configured on the local system.
• -f [regex] — lists the available filter functions. These are the list of functions on the system that you can trace, or filter on. It takes an optional argument that uses regcomp(3) expressions to search. Like so:

trace-cmd list -f '^sched.*'

If --proto is also added to the command line, the functions will also have show their prototypes if BTF is available. 🦋

• --proto — if BTF is available on the running kernel, it will also show the function parameters with -f. Big fan.
• -P — lists the plugin files that get loaded on trace-cmd report.
• -O — lists plugin options that can be used by the trace-cmd report -O option.
• -B — lists defined buffer instances (sub buffers). 🌈
• -C — lists defined clocks that can be used with trace-cmd record -C. The one in brackets ([]) is the active clock — that's your main character right there. 👑
• -c — lists the available trace file compression algorithms.

---

🦋 SEE ALSO 🦋

trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1), trace-cmd-split(1), trace-cmd-listen(1) — go read the whole friend group, fr fr.

💜 AUTHOR 💜

Written by Steven Rostedt, <rostedt@goodmis.org[1]> 🫶

🌸 RESOURCES 🌸

https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/

🎀 COPYING 🎀

Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).

⭐ NOTES ⭐

1. rostedt@goodmis.org mailto:rostedt@goodmis.org

---

Okay that's the whole page, you ate that 💅 This was libtracefs, dated 03/09/2026 — and no, I'm not copying the footer line, I'm giving it a cute little send-off instead. Slay. 💖✨