From: Jiri Olsa <olsajiri@gmail.com>
To: Yafang Shao <laoar.shao@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 <kafai@fb.com>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Quentin Monnet <quentin@isovalent.com>
Subject: Re: [PATCH bpf-next 0/8] bpf: Add cookies retrieval for perf/kprobe multi links
Date: Fri, 19 Jan 2024 09:03:25 +0100 [thread overview]
Message-ID: <ZaoszTLcNmbz9Mck@krava> (raw)
In-Reply-To: <CALOAHbD6B+xG=Cn1za8QKf5MvodM7xUDUxkuM7YT-0emhh2e1g@mail.gmail.com>
On Thu, Jan 18, 2024 at 08:42:29PM +0800, Yafang Shao wrote:
> On Thu, Jan 18, 2024 at 5:54 PM Jiri Olsa <jolsa@kernel.org> wrote:
> >
> > hi,
> > this patchset adds support to retrieve cookies from existing tracing
> > links that still did not support it plus changes to bpftool to display
> > them. It's leftover we discussed some time ago [1].
>
> Thanks for your work.
>
> bpf cookie is also displayed in the pid_iter [0]. After we add support
> for the cookie for other progs like kprobe_multi and uprobe_multi, I
> think we should update this file as well.
ok, I'll check
thanks,
jirka
>
> [0]. tools/bpf/bpftool/skeleton/pid_iter.bpf.c
>
> >
> > thanks,
> > jirka
> >
> >
> > [1] https://lore.kernel.org/bpf/CALOAHbAZ6=A9j3VFCLoAC_WhgQKU7injMf06=cM2sU4Hi4Sx+Q@mail.gmail.com/
> > ---
> > Jiri Olsa (8):
> > bpf: Add cookie to perf_event bpf_link_info records
> > bpf: Store cookies in kprobe_multi bpf_link_info data
> > bpftool: Fix wrong free call in do_show_link
> > selftests/bpf: Add cookies check for kprobe_multi fill_link_info test
> > selftests/bpf: Add cookies check for perf_event fill_link_info test
> > selftests/bpf: Add fill_link_info test for perf event
> > bpftool: Display cookie for perf event link probes
> > bpftool: Display cookie for kprobe multi link
> >
> > include/uapi/linux/bpf.h | 5 +++++
> > kernel/bpf/syscall.c | 4 ++++
> > kernel/trace/bpf_trace.c | 15 +++++++++++++
> > tools/bpf/bpftool/link.c | 87 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------
> > tools/include/uapi/linux/bpf.h | 5 +++++
> > tools/testing/selftests/bpf/prog_tests/fill_link_info.c | 114 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------
> > tools/testing/selftests/bpf/progs/test_fill_link_info.c | 6 +++++
> > 7 files changed, 204 insertions(+), 32 deletions(-)
>
>
>
> --
> Regards
> Yafang
prev parent reply other threads:[~2024-01-19 8:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 9:54 [PATCH bpf-next 0/8] bpf: Add cookies retrieval for perf/kprobe multi links Jiri Olsa
2024-01-18 9:54 ` [PATCH bpf-next 1/8] bpf: Add cookie to perf_event bpf_link_info records Jiri Olsa
2024-01-18 12:24 ` Yafang Shao
2024-01-19 8:03 ` Jiri Olsa
2024-01-18 9:54 ` [PATCH bpf-next 2/8] bpf: Store cookies in kprobe_multi bpf_link_info data Jiri Olsa
2024-01-18 13:21 ` Yafang Shao
2024-01-18 9:54 ` [PATCH bpf-next 3/8] bpftool: Fix wrong free call in do_show_link Jiri Olsa
2024-01-18 12:29 ` Yafang Shao
2024-01-18 17:51 ` Quentin Monnet
2024-01-18 9:54 ` [PATCH bpf-next 4/8] selftests/bpf: Add cookies check for kprobe_multi fill_link_info test Jiri Olsa
2024-01-18 9:54 ` [PATCH bpf-next 5/8] selftests/bpf: Add cookies check for perf_event " Jiri Olsa
2024-01-18 9:54 ` [PATCH bpf-next 6/8] selftests/bpf: Add fill_link_info test for perf event Jiri Olsa
2024-01-18 9:54 ` [PATCH bpf-next 7/8] bpftool: Display cookie for perf event link probes Jiri Olsa
2024-01-18 17:51 ` Quentin Monnet
2024-01-18 9:54 ` [PATCH bpf-next 8/8] bpftool: Display cookie for kprobe multi link Jiri Olsa
2024-01-18 17:51 ` Quentin Monnet
2024-01-19 8:03 ` Jiri Olsa
2024-01-18 12:42 ` [PATCH bpf-next 0/8] bpf: Add cookies retrieval for perf/kprobe multi links Yafang Shao
2024-01-19 8:03 ` 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=ZaoszTLcNmbz9Mck@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=laoar.shao@gmail.com \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--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;
as well as URLs for NNTP newsgroup(s).