From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: andrii@kernel.org, olsajiri@gmail.com, eddyz87@gmail.com,
mykolal@fb.com, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
yikai.lin@vivo.com, memxor@gmail.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/3] selftests/bpf: benchmark all symbols for kprobe-multi
Date: Wed, 3 Sep 2025 16:50:00 -0700 [thread overview]
Message-ID: <CAEf4BzZVTr26Uogf8uh=7HmgG6Qo_uVy3fX8bQgC+Xs63wZcCA@mail.gmail.com> (raw)
In-Reply-To: <20250901034252.26121-1-dongml2@chinatelecom.cn>
On Sun, Aug 31, 2025 at 8:43 PM Menglong Dong <menglong8.dong@gmail.com> wrote:
>
> Add the benchmark testcase "kprobe-multi-all", which will hook all the
> kernel functions during the testing.
>
> This series is separated out from [1].
>
> Changes since V2:
> * add some comment to attach_ksyms_all, which notes that don't run the
> testing on a debug kernel
>
> Changes since V1:
> * introduce trace_blacklist instead of copy-pasting strcmp in the 2nd
> patch
> * use fprintf() instead of printf() in 3rd patch
>
> Link: https://lore.kernel.org/bpf/20250817024607.296117-1-dongml2@chinatelecom.cn/ [1]
> Menglong Dong (3):
> selftests/bpf: move get_ksyms and get_addrs to trace_helpers.c
> selftests/bpf: skip recursive functions for kprobe_multi
> selftests/bpf: add benchmark testing for kprobe-multi-all
>
this doesn't apply cleanly over bpf-next, can you please rebase and
resend to let CI run?
> tools/testing/selftests/bpf/bench.c | 4 +
> .../selftests/bpf/benchs/bench_trigger.c | 61 +++++
> .../selftests/bpf/benchs/run_bench_trigger.sh | 4 +-
> .../bpf/prog_tests/kprobe_multi_test.c | 220 +---------------
> .../selftests/bpf/progs/trigger_bench.c | 12 +
> tools/testing/selftests/bpf/trace_helpers.c | 234 ++++++++++++++++++
> tools/testing/selftests/bpf/trace_helpers.h | 3 +
> 7 files changed, 319 insertions(+), 219 deletions(-)
>
> --
> 2.51.0
>
next prev parent reply other threads:[~2025-09-03 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 3:42 [PATCH bpf-next v3 0/3] selftests/bpf: benchmark all symbols for kprobe-multi Menglong Dong
2025-09-01 3:42 ` [PATCH bpf-next v3 1/3] selftests/bpf: move get_ksyms and get_addrs to trace_helpers.c Menglong Dong
2025-09-01 3:42 ` [PATCH bpf-next v3 2/3] selftests/bpf: skip recursive functions for kprobe_multi Menglong Dong
2025-09-01 3:42 ` [PATCH bpf-next v3 3/3] selftests/bpf: add benchmark testing for kprobe-multi-all Menglong Dong
2025-09-03 23:50 ` Andrii Nakryiko [this message]
2025-09-04 1:12 ` [PATCH bpf-next v3 0/3] selftests/bpf: benchmark all symbols for kprobe-multi Menglong Dong
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='CAEf4BzZVTr26Uogf8uh=7HmgG6Qo_uVy3fX8bQgC+Xs63wZcCA@mail.gmail.com' \
--to=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-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=menglong8.dong@gmail.com \
--cc=mykolal@fb.com \
--cc=olsajiri@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yikai.lin@vivo.com \
--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).