From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
bpf <bpf@vger.kernel.org>, Heiko Carstens <hca@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Hari Bathini <hbathini@linux.ibm.com>
Subject: Re: [PATCH bpf-next 0/3] selftests/bpf: Fix tests on non-x86 architectures
Date: Sat, 5 Feb 2022 12:46:39 -0800 [thread overview]
Message-ID: <CAEf4BzYAK3g1ELm7UeTDMJWquX2CUS3PJnzRx4i-LLBTVKH2mA@mail.gmail.com> (raw)
In-Reply-To: <cover.1643973917.git.naveen.n.rao@linux.vnet.ibm.com>
On Fri, Feb 4, 2022 at 3:36 AM Naveen N. Rao
<naveen.n.rao@linux.vnet.ibm.com> wrote:
>
> The first patch fixes an issue with bpf_syscall_macro test to work
> properly on architectures that don't have a syscall wrapper. The second
> patch updates SYS_PREFIX for architectures without a syscall wrapper.
> The final patch fixes some of the tests to use correct syscall entry
> names on non-x86 architectures.
>
> - Naveen
>
>
> Naveen N. Rao (3):
> selftests/bpf: Use correct pt_regs on architectures without syscall
> wrapper
> selftests/bpf: Use "__se_" prefix on architectures without syscall
> wrapper
> selftests/bpf: Fix tests to use arch-dependent syscall entry points
>
Ilya's patch set made the first patch unnecessary, but I've applied
2nd and 3rd to bpf-next, thanks!
> tools/testing/selftests/bpf/progs/bloom_filter_bench.c | 7 ++++---
> tools/testing/selftests/bpf/progs/bloom_filter_map.c | 5 +++--
> tools/testing/selftests/bpf/progs/bpf_loop.c | 9 +++++----
> tools/testing/selftests/bpf/progs/bpf_loop_bench.c | 3 ++-
> tools/testing/selftests/bpf/progs/bpf_misc.h | 2 +-
> tools/testing/selftests/bpf/progs/bpf_syscall_macro.c | 4 ++++
> tools/testing/selftests/bpf/progs/fexit_sleep.c | 9 +++++----
> tools/testing/selftests/bpf/progs/perfbuf_bench.c | 3 ++-
> tools/testing/selftests/bpf/progs/ringbuf_bench.c | 3 ++-
> tools/testing/selftests/bpf/progs/test_ringbuf.c | 3 ++-
> tools/testing/selftests/bpf/progs/trace_printk.c | 3 ++-
> tools/testing/selftests/bpf/progs/trace_vprintk.c | 3 ++-
> tools/testing/selftests/bpf/progs/trigger_bench.c | 9 +++++----
> 13 files changed, 39 insertions(+), 24 deletions(-)
>
>
> base-commit: 227a0713b319e7a8605312dee1c97c97a719a9fc
> --
> 2.34.1
>
prev parent reply other threads:[~2022-02-05 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 11:35 [PATCH bpf-next 0/3] selftests/bpf: Fix tests on non-x86 architectures Naveen N. Rao
2022-02-04 11:35 ` [PATCH bpf-next 1/3] selftests/bpf: Use correct pt_regs on architectures without syscall wrapper Naveen N. Rao
2022-02-04 11:35 ` [PATCH bpf-next 2/3] selftests/bpf: Use "__se_" prefix " Naveen N. Rao
2022-02-04 11:35 ` [PATCH bpf-next 3/3] selftests/bpf: Fix tests to use arch-dependent syscall entry points Naveen N. Rao
2022-02-05 20:46 ` Andrii Nakryiko [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=CAEf4BzYAK3g1ELm7UeTDMJWquX2CUS3PJnzRx4i-LLBTVKH2mA@mail.gmail.com \
--to=andrii.nakryiko@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hbathini@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.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.