From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
Quentin Monnet <qmo@kernel.org>
Subject: Re: [PATCHv2 bpf-next 0/3] bpf: tracing_multi link info support
Date: Wed, 24 Jun 2026 11:29:19 +0200 [thread overview]
Message-ID: <ajujb-Fdsf-zTIp7@krava> (raw)
In-Reply-To: <CAEf4BzbLUzTfvf4pVTOCoOM5AdiS1wkbmuK3R3L+fFZLuF7n+g@mail.gmail.com>
On Tue, Jun 23, 2026 at 01:51:29PM -0700, Andrii Nakryiko wrote:
> On Tue, Jun 23, 2026 at 7:24 AM Jiri Olsa <jolsa@kernel.org> wrote:
> >
> > hi,
> > adding link info support for tracing_multi link.
> >
> > Adding the kernel support with related selftests and bpftool support
> > to display the tracing_multi link info, the output looks like:
> >
> > # bpftool link
> > ...
> > 27: tracing_multi prog 93
> > attach_type trace_fentry_multi obj_id 1 count 3
> > btf_id addr cookie func [module]
> > 91984 ffffffff824f4a24 a bpf_fentry_test1
> > 91986 ffffffff824f6a84 1e bpf_fentry_test2
> > 91987 ffffffff824f6a94 14 bpf_fentry_test3
>
> kernel's bpf_tracing_link_show_fdinfo() emits cookie as decimal
> number, why go with hex here?
true, will switch to dec, thanks
jirka
>
> > pids test_progs(1462)
> >
> > thanks,
> > jirka
> >
> >
> > v1: https://lore.kernel.org/bpf/20260621204524.61067-1-jolsa@kernel.org/
> >
> > v2 changes:
> > - fix kernel symbol search logic [sashiko]
> > - typo fixes [bots]
> >
> >
> > ---
> > Jiri Olsa (3):
> > bpf: Add tracing_multi link info support
> > selftests/bpf: Add tracing_multi link info tests
> > bpftool: Add tracing_multi link info output
> >
> > include/uapi/linux/bpf.h | 9 +++
> > kernel/trace/bpf_trace.c | 55 +++++++++++++++++
> > tools/bpf/bpftool/link.c | 137 +++++++++++++++++++++++++++++++++++++++++
> > tools/include/uapi/linux/bpf.h | 9 +++
> > tools/testing/selftests/bpf/prog_tests/fill_link_info.c | 242 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > tools/testing/selftests/bpf/progs/test_fill_link_info.c | 6 ++
> > 6 files changed, 458 insertions(+)
prev parent reply other threads:[~2026-06-24 9:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 14:24 [PATCHv2 bpf-next 0/3] bpf: tracing_multi link info support Jiri Olsa
2026-06-23 14:24 ` [PATCHv2 bpf-next 1/3] bpf: Add " Jiri Olsa
2026-06-23 15:32 ` Leon Hwang
2026-06-23 21:01 ` Andrii Nakryiko
2026-06-24 9:36 ` Jiri Olsa
2026-06-23 14:24 ` [PATCHv2 bpf-next 2/3] selftests/bpf: Add tracing_multi link info tests Jiri Olsa
2026-06-23 14:39 ` sashiko-bot
2026-06-23 14:24 ` [PATCHv2 bpf-next 3/3] bpftool: Add tracing_multi link info output Jiri Olsa
2026-06-23 14:38 ` sashiko-bot
2026-06-23 21:11 ` Andrii Nakryiko
2026-06-24 11:32 ` Jiri Olsa
2026-06-23 20:51 ` [PATCHv2 bpf-next 0/3] bpf: tracing_multi link info support Andrii Nakryiko
2026-06-24 9:29 ` Jiri Olsa [this message]
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=ajujb-Fdsf-zTIp7@krava \
--to=olsajiri@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=martin.lau@linux.dev \
--cc=qmo@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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