Re: [PATCH 1/2] tools/bootconfig: Use the registered global tracing parameter names

From: Masami Hiramatsu (Google)

Date: Sun Nov 22 2026 - 04:37:28 EST


On Sun, 22 Nov 2026 01:34:58 +0100, Eduardo Mucelli Rezende Oliveira <edumucelli@xxxxxxxxx> wrote:
> The boot-time tracing guide lists four kernel.* keys that do not match
> the parameters registered by the tracing code. For example,
> ftrace2bconf.sh emits kernel.fgraph_max_depth, which bootconfig passes
> as fgraph_max_depth on the kernel command line. The function-graph
> tracer registers ftrace_graph_max_depth.
>
> Use the registered names in the guide and the exporter. Teach
> bconf2ftrace.sh to read those names, with the previous script keys as
> fallbacks so existing replay configurations still work.
>
> Fixes: 47781947947a ("Documentation: tracing: Add boot-time tracing document")

Since this patch also fixes the key names in bconf2ftrace.sh and
ftrace2bconf.sh (which were added later than the documentation), consider
adding the corresponding Fixes tags as well:

Fixes: 7e66ef0046cc ("tools/bootconfig: Add a script to generate ftrace
shell-command from bootconfig")
Fixes: 2b86062a34a8 ("tools/bootconfig: Add a script to generates
bootconfig from ftrace")

Thanks,

> Signed-off-by: Eduardo Mucelli Rezende Oliveira <edumucelli@xxxxxxxxx>
> ---
> Documentation/trace/boottime-trace.rst | 8 ++++----
> tools/bootconfig/scripts/bconf2ftrace.sh | 21 ++++++++++++++++-----
> tools/bootconfig/scripts/ftrace2bconf.sh | 5 +++--
> 3 files changed, 23 insertions(+), 11 deletions(-)

--
Masami Hiramatsu (Google) <mhiramat@xxxxxxxxxx>