From: Jiri Olsa <jolsa@kernel.org>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, linux-perf-users@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>,
Hao Luo <haoluo@google.com>, Yafang Shao <laoar.shao@gmail.com>,
Quentin Monnet <qmo@kernel.org>
Subject: [PATCHv2 bpf-next 0/3] bpf: Retrieve ref_ctr_offset from uprobe perf link
Date: Fri, 9 May 2025 17:35:36 +0200 [thread overview]
Message-ID: <20250509153539.779599-1-jolsa@kernel.org> (raw)
hi,
adding ref_ctr_offset retrieval for uprobe perf link info.
v2 changes:
- display ref_ctr_offset as hex number [Andrii]
- added acks
thanks,
jirka
---
Jiri Olsa (3):
bpf: Add support to retrieve ref_ctr_offset for uprobe perf link
selftests/bpf: Add link info test for ref_ctr_offset retrieval
bpftool: Display ref_ctr_offset for uprobe link info
include/uapi/linux/bpf.h | 1 +
kernel/bpf/syscall.c | 5 +++--
kernel/trace/trace_uprobe.c | 2 +-
tools/bpf/bpftool/link.c | 3 +++
tools/include/uapi/linux/bpf.h | 1 +
tools/testing/selftests/bpf/prog_tests/fill_link_info.c | 18 ++++++++++++++++--
6 files changed, 25 insertions(+), 5 deletions(-)
next reply other threads:[~2025-05-09 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 15:35 Jiri Olsa [this message]
2025-05-09 15:35 ` [PATCHv2 bpf-next 1/3] bpf: Add support to retrieve ref_ctr_offset for uprobe perf link Jiri Olsa
2025-05-09 15:35 ` [PATCHv2 bpf-next 2/3] selftests/bpf: Add link info test for ref_ctr_offset retrieval Jiri Olsa
2025-05-09 15:35 ` [PATCHv2 bpf-next 3/3] bpftool: Display ref_ctr_offset for uprobe link info Jiri Olsa
2025-05-09 20:05 ` [PATCHv2 bpf-next 0/3] bpf: Retrieve ref_ctr_offset from uprobe perf link patchwork-bot+netdevbpf
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=20250509153539.779599-1-jolsa@kernel.org \
--to=jolsa@kernel.org \
--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=laoar.shao@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).