Re: [PATCH 2/2] tracing: resolve enum names for function arguments via BTF

From: Google

Date: Thu Feb 05 2026 - 19:12:22 EST


On Mon, 2 Feb 2026 19:15:48 +0800
Donglin Peng <dolinux.peng@xxxxxxxxx> wrote:

> From: Donglin Peng <pengdonglin@xxxxxxxxxx>
>
> Use BTF to print symbolic names for enum-type function arguments,
> improving trace readability.
>
> Before:
> count_memcg_events(memcg=0xffff..., idx=20, count=0x1) {
>
> After:
> count_memcg_events(memcg=0xffff..., idx=20 [PGFAULT], count=0x1) {

Hmm, it is interesting idea. Maybe I can also introduce the same
feature to fetcharg for fprobe/kprobes as a new type.
Since the enum type should be solved in parsing the event definition,
for fprobe/kprobes the performance will not be a performance problem.

Thanks,

>
> Cc: Steven Rostedt <rostedt@xxxxxxxxxxx>
> Cc: Masami Hiramatsu <mhiramat@xxxxxxxxxx>
> Cc: linux-trace-kernel@xxxxxxxxxxxxxxx
> Signed-off-by: Donglin Peng <pengdonglin@xxxxxxxxxx>
> ---
> kernel/trace/trace_output.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/trace/trace_output.c b/kernel/trace/trace_output.c
> index cc2d3306bb60..c395f768c3b8 100644
> --- a/kernel/trace/trace_output.c
> +++ b/kernel/trace/trace_output.c
> @@ -695,12 +695,13 @@ void print_function_args(struct trace_seq *s, unsigned long *args,
> {
> const struct btf_param *param;
> const struct btf_type *t;
> + const struct btf_enum *enump;
> const char *param_name;
> char name[KSYM_NAME_LEN];
> unsigned long arg;
> struct btf *btf;
> s32 tid, nr = 0;
> - int a, p, x;
> + int a, p, x, i;
> u16 encode;
>
> trace_seq_printf(s, "(");
> @@ -754,6 +755,14 @@ void print_function_args(struct trace_seq *s, unsigned long *args,
> break;
> case BTF_KIND_ENUM:
> trace_seq_printf(s, "%ld", arg);
> + for_each_enum(i, t, enump) {
> + if (arg == enump->val) {
> + trace_seq_printf(s, " [%s]",
> + btf_name_by_offset(btf,
> + enump->name_off));
> + break;
> + }
> + }
> break;
> default:
> /* This does not handle complex arguments */
> --
> 2.34.1
>


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