From: Yafang Shao <laoar.shao@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, quentin@isovalent.com,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 2/6] bpftool: Show probed function in kprobe_multi link info
Date: Sun, 4 Jun 2023 11:26:14 +0800 [thread overview]
Message-ID: <CALOAHbAf=X05fqCz1ABX3pzc60QE5ax=pEfuGxhFkqJQT7Md6g@mail.gmail.com> (raw)
In-Reply-To: <CAEf4BzbJCCxj-0CCy_xsiJKk1Re_iXNGH95j9ChnOwSeeLUYEQ@mail.gmail.com>
On Sat, Jun 3, 2023 at 6:16 AM Andrii Nakryiko
<andrii.nakryiko@gmail.com> wrote:
>
> On Fri, Jun 2, 2023 at 1:52 AM Yafang Shao <laoar.shao@gmail.com> wrote:
> >
> > Show the already expose kprobe_multi link info in bpftool. The result as
> > follows,
> > $ tools/bpf/bpftool/bpftool link show
> > 1: kprobe_multi prog 5
> > func_cnt 4 addrs symbols
> > ffffffffb4d465b0 schedule_timeout_interruptible
> > ffffffffb4d465f0 schedule_timeout_killable
> > ffffffffb4d46630 schedule_timeout_uninterruptible
> > ffffffffb4d46670 schedule_timeout_idle
> > pids trace(8729)
> >
> > $ tools/bpf/bpftool/bpftool link show -j
> > [{"id":1,"type":"kprobe_multi","prog_id":5,"func_cnt":4,"addrs":[{"addr":18446744072448402864,"symbol":"schedule_timeout_interruptible"},{"addr":18446744072448402928,"symbol":"schedule_timeout_killable"},{"addr":18446744072448402992,"symbol":"schedule_timeout_uninterruptible"},{"addr":18446744072448403056,"symbol":"schedule_timeout_idle"}],"pids":[{"pid":8729,"comm":"trace"}]}]
>
>
> probably a good idea to also show whether it's retprobe or not?
Good point. Will add it.
--
Regards
Yafang
next prev parent reply other threads:[~2023-06-04 3:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 8:52 [PATCH bpf-next 0/6] bpf: Support ->fill_link_info for kprobe prog Yafang Shao
2023-06-02 8:52 ` [PATCH bpf-next 1/6] bpf: Support ->fill_link_info for kprobe_multi Yafang Shao
2023-06-02 16:45 ` Stanislav Fomichev
2023-06-04 3:21 ` Yafang Shao
2023-06-03 6:38 ` kernel test robot
2023-06-04 3:22 ` Yafang Shao
2023-06-02 8:52 ` [PATCH bpf-next 2/6] bpftool: Show probed function in kprobe_multi link info Yafang Shao
2023-06-02 20:36 ` Alexei Starovoitov
2023-06-04 3:24 ` Yafang Shao
2023-06-02 22:16 ` Andrii Nakryiko
2023-06-04 3:26 ` Yafang Shao [this message]
2023-06-02 8:52 ` [PATCH bpf-next 3/6] bpf: Always expose the probed address Yafang Shao
2023-06-02 8:52 ` [PATCH bpf-next 4/6] bpf: Add a common helper bpf_copy_to_user() Yafang Shao
2023-06-02 8:52 ` [PATCH bpf-next 5/6] bpf: Support ->fill_link_info for perf_event Yafang Shao
2023-06-02 22:19 ` Andrii Nakryiko
2023-06-04 3:28 ` Yafang Shao
2023-06-02 8:52 ` [PATCH bpf-next 6/6] bpftool: Show probed function in perf_event link info Yafang Shao
2023-06-02 20:38 ` Alexei Starovoitov
2023-06-04 3:23 ` Yafang Shao
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='CALOAHbAf=X05fqCz1ABX3pzc60QE5ax=pEfuGxhFkqJQT7Md6g@mail.gmail.com' \
--to=laoar.shao@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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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).