[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEf4BzZBztC69GFDuA4YJHPmWOXuq3+tSNMspPNA3tksGaEi=A@mail.gmail.com>
Date: Wed, 20 Aug 2025 15:47:29 -0700
From: Andrii Nakryiko <andrii.nakryiko@...il.com>
To: Menglong Dong <menglong8.dong@...il.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org, mykolal@...com,
shuah@...nel.org, davem@...emloft.net, kuba@...nel.org, hawk@...nel.org,
nathan@...nel.org, nick.desaulniers+lkml@...il.com, morbo@...gle.com,
justinstitt@...gle.com, bpf@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH bpf-next 2/3] selftests/bpf: skip recursive functions for kprobe_multi
On Mon, Aug 18, 2025 at 8:40 PM Menglong Dong <menglong8.dong@...il.com> wrote:
>
> Some functions is recursive for the kprobe_multi and impact the benchmark
> results. So just skip them.
>
> Signed-off-by: Menglong Dong <dongml2@...natelecom.cn>
> ---
> tools/testing/selftests/bpf/trace_helpers.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/trace_helpers.c b/tools/testing/selftests/bpf/trace_helpers.c
> index d24baf244d1f..9da9da51b132 100644
> --- a/tools/testing/selftests/bpf/trace_helpers.c
> +++ b/tools/testing/selftests/bpf/trace_helpers.c
> @@ -559,6 +559,22 @@ static bool skip_entry(char *name)
> if (!strncmp(name, "__ftrace_invalid_address__",
> sizeof("__ftrace_invalid_address__") - 1))
> return true;
> +
> + if (!strcmp(name, "migrate_disable"))
> + return true;
> + if (!strcmp(name, "migrate_enable"))
> + return true;
> + if (!strcmp(name, "rcu_read_unlock_strict"))
> + return true;
> + if (!strcmp(name, "preempt_count_add"))
> + return true;
> + if (!strcmp(name, "preempt_count_sub"))
> + return true;
> + if (!strcmp(name, "__rcu_read_lock"))
> + return true;
> + if (!strcmp(name, "__rcu_read_unlock"))
> + return true;
> +
static const char *trace_blacklist[] = {
"migrate_disable",
"migrate_enable",
...
};
it's not like it's one or two functions where copy-pasting strcmp might be fine
pw-bot: cr
> return false;
> }
>
> --
> 2.50.1
>
Powered by blists - more mailing lists