All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH 0/3] selftests/bpf: Fix a few issues in arena_spin_lock
Date: Thu, 24 Apr 2025 18:41:24 +0200	[thread overview]
Message-ID: <20250424165525.154403-1-iii@linux.ibm.com> (raw)

Hi,

I tried running the arena_spin_lock test on s390x and ran into the
following issues:

* Changing the header file does not lead to rebuilding the test.
* The checked for number of CPUs and the actually required number of
  CPUs are different.
* Endianness issue in spinlock definition.

This series fixes all three.

Best regards,
Ilya

Ilya Leoshkevich (3):
  selftests/bpf: Fix arena_spin_lock.c build dependency
  selftests/bpf: Fix arena_spin_lock on systems with less than 16 CPUs
  selftests/bpf: Fix endianness issue in __qspinlock declaration

 .../selftests/bpf/prog_tests/arena_spin_lock.c     | 14 ++++++++------
 .../bpf/{ => progs}/bpf_arena_spin_lock.h          | 12 ++++++++++++
 2 files changed, 20 insertions(+), 6 deletions(-)
 rename tools/testing/selftests/bpf/{ => progs}/bpf_arena_spin_lock.h (98%)

-- 
2.49.0


             reply	other threads:[~2025-04-24 16:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 16:41 Ilya Leoshkevich [this message]
2025-04-24 16:41 ` [PATCH 1/3] selftests/bpf: Fix arena_spin_lock.c build dependency Ilya Leoshkevich
2025-04-24 16:41 ` [PATCH 2/3] selftests/bpf: Fix arena_spin_lock on systems with less than 16 CPUs Ilya Leoshkevich
2025-04-24 16:41 ` [PATCH 3/3] selftests/bpf: Fix endianness issue in __qspinlock declaration Ilya Leoshkevich
2025-04-24 18:33 ` [PATCH 0/3] selftests/bpf: Fix a few issues in arena_spin_lock patchwork-bot+netdevbpf
2025-04-24 18:41   ` Alexei Starovoitov
2025-04-24 18:51     ` Konstantin Ryabitsev
2025-04-25 16:25       ` Jakub Kicinski
2025-04-25 17:18         ` Konstantin Ryabitsev
2025-04-25 18:58     ` Konstantin Ryabitsev
2025-04-26  0:32       ` Alexei Starovoitov
2025-04-25  0:10 ` patchwork-bot+netdevbpf
2025-04-25  0:16   ` Alexei Starovoitov
2025-04-25  0:40 ` patchwork-bot+netdevbpf
2025-04-25  1:14   ` Alexei Starovoitov

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=20250424165525.154403-1-iii@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.