From: "Emil Tsalapatis" <emil@etsalapatis.com>
To: "Qiliang Yuan" <odys.yuan@gmail.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Kumar Kartikeya Dwivedi" <memxor@gmail.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Song Liu" <song@kernel.org>,
"Yonghong Song" <yonghong.song@linux.dev>,
"Jiri Olsa" <jolsa@kernel.org>,
"Emil Tsalapatis" <emil@etsalapatis.com>,
"Ihor Solodrai" <ihor.solodrai@linux.dev>,
"Shuah Khan" <shuah@kernel.org>
Cc: <bpf@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next 0/2] selftests/bpf: Skip libarena when arena spin locks are unsupported
Date: Wed, 14 Oct 2026 19:51:26 +0000 [thread overview]
Message-ID: <DM4TMYJX3BXY.15067Y489FKUR@etsalapatis.com> (raw)
In-Reply-To: <20261009-selftests-bpf-libarena-nr-cpus-v1-0-e726ccc66fc6@gmail.com>
On Fri Oct 9, 2026 at 1:49 AM UTC, Qiliang Yuan wrote:
> serial_test_libarena runs the test programs of libarena, whose buddy
> allocator serializes its operations with an arena spin lock.
>
> arena_spin_lock() fails with -EOPNOTSUPP on kernels built with more
> than 1024 possible CPUs, as distributions commonly configure them.
> buddy_init() reports that as -EINVAL, and every test then fails at
> arena_buddy_reset.
>
> Patch 1 makes buddy_init() return the error of the lock, patch 2 skips
> the tests when resetting the allocator fails with -EOPNOTSUPP.
>
If new kernels expect more than 1024 CPUs, we should update libarena and
arena_spin_lock() to support them instead of returning EOPNOTSUPP.
pw-bot: cr
> Signed-off-by: Qiliang Yuan <odys.yuan@gmail.com>
> ---
> Qiliang Yuan (2):
> selftests/bpf: Return the lock error from buddy_init() of libarena
> selftests/bpf: Skip libarena on kernels with too many possible CPUs
>
> tools/testing/selftests/bpf/libarena/src/buddy.bpf.c | 5 +++--
> tools/testing/selftests/bpf/prog_tests/libarena.c | 9 +++++++++
> 2 files changed, 12 insertions(+), 2 deletions(-)
> ---
> base-commit: e1d84a37cba984388988d2f1ddc84561413f0db2
> change-id: 20261009-selftests-bpf-libarena-nr-cpus-50fc5dd00fe2
>
> Best regards,
prev parent reply other threads:[~2026-10-14 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 1:49 Qiliang Yuan
2026-10-09 1:49 ` [PATCH bpf-next 1/2] selftests/bpf: Return the lock error from buddy_init() of libarena Qiliang Yuan
2026-10-09 2:37 ` bot+bpf-ci
2026-10-09 1:49 ` [PATCH bpf-next 2/2] selftests/bpf: Skip libarena on kernels with too many possible CPUs Qiliang Yuan
2026-10-09 2:37 ` bot+bpf-ci
2026-10-14 19:51 ` Emil Tsalapatis [this message]
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=DM4TMYJX3BXY.15067Y489FKUR@etsalapatis.com \
--to=emil@etsalapatis.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=odys.yuan@gmail.com \
--cc=shuah@kernel.org \
--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
all inboxes | Powered by JetHome®