From: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
To: bpf@vger.kernel.org
Cc: andrii@kernel.org, jolsa@redhat.com,
Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
Subject: [PATCH bpf-next v3 0/8] bpf/selftests: page size fixes
Date: Wed, 31 Mar 2021 19:44:33 +0300 [thread overview]
Message-ID: <20210331164433.320534-1-yauheni.kaliuta@redhat.com> (raw)
A set of fixes for selftests to make them working on systems with PAGE_SIZE > 4K
--
v2->v3:
- reorder: move version removing patch first to keep main patches in
one group;
- rename "selftests/bpf: pass page size from userspace in sockopt_sk"
as suggested;
- convert sockopt_sk test to use ASSERT macros;
- set page size from userspace
- split patches to pairs userspace/bpf. It's easier to check that
every conversion works as expected;
v1->v2:
- add missed 'selftests/bpf: test_progs/sockopt_sk: Convert to use BPF skeleton'
Yauheni Kaliuta (8):
selftests/bpf: test_progs/sockopt_sk: remove version
selftests/bpf: test_progs/sockopt_sk: Convert to use BPF skeleton
selftests/bpf: pass page size from userspace in sockopt_sk
selftests/bpf: pass page size from userspace in map_ptr
selftests/bpf: mmap: use runtime page size
selftests/bpf: ringbuf: use runtime page size
libbpf: add bpf_map__inner_map API
selftests/bpf: ringbuf_multi: use runtime page size
tools/lib/bpf/libbpf.c | 10 +++
tools/lib/bpf/libbpf.h | 1 +
tools/lib/bpf/libbpf.map | 1 +
.../selftests/bpf/prog_tests/map_ptr.c | 15 ++++-
tools/testing/selftests/bpf/prog_tests/mmap.c | 24 +++++--
.../selftests/bpf/prog_tests/ringbuf.c | 17 +++--
.../selftests/bpf/prog_tests/ringbuf_multi.c | 23 ++++++-
.../selftests/bpf/prog_tests/sockopt_sk.c | 65 +++++--------------
.../selftests/bpf/progs/map_ptr_kern.c | 4 +-
.../testing/selftests/bpf/progs/sockopt_sk.c | 11 ++--
tools/testing/selftests/bpf/progs/test_mmap.c | 2 -
.../selftests/bpf/progs/test_ringbuf.c | 1 -
.../selftests/bpf/progs/test_ringbuf_multi.c | 1 -
13 files changed, 101 insertions(+), 74 deletions(-)
--
2.31.1
next reply other threads:[~2021-03-31 16:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 16:44 Yauheni Kaliuta [this message]
2021-03-31 16:44 ` [PATCH bpf-next v3 1/8] selftests/bpf: test_progs/sockopt_sk: remove version Yauheni Kaliuta
2021-03-31 16:44 ` [PATCH bpf-next v3 2/8] selftests/bpf: test_progs/sockopt_sk: Convert to use BPF skeleton Yauheni Kaliuta
2021-03-31 16:44 ` [PATCH bpf-next v3 3/8] selftests/bpf: pass page size from userspace in sockopt_sk Yauheni Kaliuta
2021-03-31 18:44 ` Andrii Nakryiko
2021-03-31 16:45 ` [PATCH bpf-next v3 4/8] selftests/bpf: pass page size from userspace in map_ptr Yauheni Kaliuta
2021-03-31 16:45 ` [PATCH bpf-next v3 5/8] selftests/bpf: mmap: use runtime page size Yauheni Kaliuta
2021-03-31 16:45 ` [PATCH bpf-next v3 6/8] selftests/bpf: ringbuf: " Yauheni Kaliuta
2021-03-31 16:45 ` [PATCH bpf-next v3 7/8] libbpf: add bpf_map__inner_map API Yauheni Kaliuta
2021-03-31 18:48 ` Andrii Nakryiko
2021-03-31 16:45 ` [PATCH bpf-next v3 8/8] selftests/bpf: ringbuf_multi: use runtime page size Yauheni Kaliuta
2021-03-31 18:52 ` Andrii Nakryiko
2021-04-07 16:36 ` Yauheni Kaliuta
2021-04-07 18:05 ` Andrii Nakryiko
2021-04-07 18:17 ` Andrii Nakryiko
2021-04-08 5:56 ` Yauheni Kaliuta
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=20210331164433.320534-1-yauheni.kaliuta@redhat.com \
--to=yauheni.kaliuta@redhat.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jolsa@redhat.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 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).