From: Tao Chen <chen.dylane@linux.dev>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
mattbobrowski@google.com, rostedt@goodmis.org,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v6 3/3] bpf: Add show_fdinfo for kprobe_multi
Date: Wed, 2 Jul 2025 10:48:23 +0800 [thread overview]
Message-ID: <0a303984-e316-413e-a3d0-54912b19b7b7@linux.dev> (raw)
In-Reply-To: <CAEf4BzZYS52gztmLgQtsehNDVwv7NBETh97zMk73ZqLL9uJ50Q@mail.gmail.com>
在 2025/7/2 04:37, Andrii Nakryiko 写道:
> On Fri, Jun 27, 2025 at 1:23 AM Tao Chen <chen.dylane@linux.dev> wrote:
>>
>> Show kprobe_multi link info with fdinfo, the info as follows:
>>
>> link_type: kprobe_multi
>> link_id: 1
>> prog_tag: 33be53a4fd673e1d
>> prog_id: 21
>> kprobe_cnt: 8
>> missed: 0
>> cookie func
>> 1 bpf_fentry_test1+0x0/0x20
>> 7 bpf_fentry_test2+0x0/0x20
>> 2 bpf_fentry_test3+0x0/0x20
>> 3 bpf_fentry_test4+0x0/0x20
>> 4 bpf_fentry_test5+0x0/0x20
>> 5 bpf_fentry_test6+0x0/0x20
>> 6 bpf_fentry_test7+0x0/0x20
>> 8 bpf_fentry_test8+0x0/0x10
>
> two nits:
>
> 1) order of cookie. For uprobes you have cookie at the end, here in
> the front. Given variable-sized func name, I'd move cookie to the
> front for uprobes for consistency.
>
Ok, will change it in v7.
> 2) field sizing for cookie (16) is a) not sufficient for maximum
> possible u64 (20 digits) and b) very wasteful in common case of small
> numbers. So use tab instead of fixed-sized column? And why 16
> character sizing for the func column? Just to have more spaces
> emitted?
>
I just referred to the implementation in bpftool/link.c, i will use tab
format in v7. "16 character sizing for the func" just keeps consistency
with cookie, " %s" for func name maybe better.
>
> Other than that the series looks good to me.
>
> pw-bot: cr
>
>
>>
>> Signed-off-by: Tao Chen <chen.dylane@linux.dev>
>> ---
>> kernel/trace/bpf_trace.c | 27 +++++++++++++++++++++++++++
>> 1 file changed, 27 insertions(+)
>>
>> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
>> index 1c75f9c6c66..e8f070504c4 100644
>> --- a/kernel/trace/bpf_trace.c
>> +++ b/kernel/trace/bpf_trace.c
>> @@ -2622,10 +2622,37 @@ static int bpf_kprobe_multi_link_fill_link_info(const struct bpf_link *link,
>> return err;
>> }
>>
>> +#ifdef CONFIG_PROC_FS
>> +static void bpf_kprobe_multi_show_fdinfo(const struct bpf_link *link,
>> + struct seq_file *seq)
>> +{
>> + struct bpf_kprobe_multi_link *kmulti_link;
>> +
>> + kmulti_link = container_of(link, struct bpf_kprobe_multi_link, link);
>> +
>> + seq_printf(seq,
>> + "kprobe_cnt:\t%u\n"
>> + "missed:\t%lu\n",
>> + kmulti_link->cnt,
>> + kmulti_link->fp.nmissed);
>> +
>> + seq_printf(seq, "%-16s %-16s\n", "cookie", "func");
>> + for (int i = 0; i < kmulti_link->cnt; i++) {
>> + seq_printf(seq,
>> + "%-16llu %-16pS\n",
>> + kmulti_link->cookies[i],
>> + (void *)kmulti_link->addrs[i]);
>> + }
>> +}
>> +#endif
>> +
>> static const struct bpf_link_ops bpf_kprobe_multi_link_lops = {
>> .release = bpf_kprobe_multi_link_release,
>> .dealloc_deferred = bpf_kprobe_multi_link_dealloc,
>> .fill_link_info = bpf_kprobe_multi_link_fill_link_info,
>> +#ifdef CONFIG_PROC_FS
>> + .show_fdinfo = bpf_kprobe_multi_show_fdinfo,
>> +#endif
>> };
>>
>> static void bpf_kprobe_multi_cookie_swap(void *a, void *b, int size, const void *priv)
>> --
>> 2.48.1
>>
--
Best Regards
Tao Chen
next prev parent reply other threads:[~2025-07-02 2:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 8:22 [PATCH bpf-next v6 1/3] bpf: Show precise link_type for {uprobe,kprobe}_multi fdinfo Tao Chen
2025-06-27 8:22 ` [PATCH bpf-next v6 2/3] bpf: Add show_fdinfo for uprobe_multi Tao Chen
2025-06-27 8:22 ` [PATCH bpf-next v6 3/3] bpf: Add show_fdinfo for kprobe_multi Tao Chen
2025-07-01 20:37 ` Andrii Nakryiko
2025-07-02 2:48 ` Tao Chen [this message]
2025-07-01 20:39 ` [PATCH bpf-next v6 1/3] bpf: Show precise link_type for {uprobe,kprobe}_multi fdinfo Alexei Starovoitov
2025-07-02 2:14 ` Tao Chen
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=0a303984-e316-413e-a3d0-54912b19b7b7@linux.dev \
--to=chen.dylane@linux.dev \
--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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mattbobrowski@google.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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).