From: patchwork-bot+netdevbpf@kernel.org
To: Johan Almbladh <johan.almbladh@anyfinetworks.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, iii@linux.ibm.com,
paul@cilium.io, yangtiezhu@loongson.cn, netdev@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 00/10] bpf/tests: Extend eBPF JIT test suite
Date: Fri, 01 Oct 2021 15:10:08 +0000 [thread overview]
Message-ID: <163310100819.11228.15860171916823233197.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211001130348.3670534-1-johan.almbladh@anyfinetworks.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 1 Oct 2021 15:03:38 +0200 you wrote:
> This patch set adds a number of new tests to the test_bpf.ko test suite.
> The new tests focus on the behaviour of operations with different
> combinations of register operands, and in particular, when two or more
> register operands are in fact the same register. It also verifies things
> like a src register not being zero-extended in-place in ALU32 operations,
> and that operations implemented with function calls do not clobber any
> other eBPF registers.
>
> [...]
Here is the summary with links:
- [bpf-next,01/10] bpf/tests: Add tests of BPF_LDX and BPF_STX with small sizes
https://git.kernel.org/bpf/bpf-next/c/caaaa1667bf1
- [bpf-next,02/10] bpf/tests: Add zero-extension checks in BPF_ATOMIC tests
https://git.kernel.org/bpf/bpf-next/c/89b63462765c
- [bpf-next,03/10] bpf/tests: Add exhaustive tests of BPF_ATOMIC magnitudes
https://git.kernel.org/bpf/bpf-next/c/f68e8efd7fa5
- [bpf-next,04/10] bpf/tests: Add tests to check source register zero-extension
https://git.kernel.org/bpf/bpf-next/c/0bbaa02b4816
- [bpf-next,05/10] bpf/tests: Add more tests for ALU and ATOMIC register clobbering
https://git.kernel.org/bpf/bpf-next/c/e2f9797b3c73
- [bpf-next,06/10] bpf/tests: Minor restructuring of ALU tests
https://git.kernel.org/bpf/bpf-next/c/e42fc3c2c40e
- [bpf-next,07/10] bpf/tests: Add exhaustive tests of ALU register combinations
https://git.kernel.org/bpf/bpf-next/c/daed6083f4fb
- [bpf-next,08/10] bpf/tests: Add exhaustive tests of BPF_ATOMIC register combinations
https://git.kernel.org/bpf/bpf-next/c/6fae2e8a1d9e
- [bpf-next,09/10] bpf/tests: Add test of ALU shifts with operand register aliasing
https://git.kernel.org/bpf/bpf-next/c/68813605dea6
- [bpf-next,10/10] bpf/tests: Add test of LDX_MEM with operand aliasing
https://git.kernel.org/bpf/bpf-next/c/7bceeb95726b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-10-01 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 13:03 Johan Almbladh
2021-10-01 13:03 ` [PATCH bpf-next 01/10] bpf/tests: Add tests of BPF_LDX and BPF_STX with small sizes Johan Almbladh
2021-10-01 13:03 ` [PATCH bpf-next 02/10] bpf/tests: Add zero-extension checks in BPF_ATOMIC tests Johan Almbladh
2021-10-01 13:03 ` [PATCH bpf-next 03/10] bpf/tests: Add exhaustive tests of BPF_ATOMIC magnitudes Johan Almbladh
2021-10-01 13:03 ` [PATCH bpf-next 04/10] bpf/tests: Add tests to check source register zero-extension Johan Almbladh
2021-10-01 13:03 ` [PATCH bpf-next 05/10] bpf/tests: Add more tests for ALU and ATOMIC register clobbering Johan Almbladh
2021-10-01 13:03 ` [PATCH bpf-next 06/10] bpf/tests: Minor restructuring of ALU tests Johan Almbladh
2021-10-01 13:03 ` [PATCH bpf-next 07/10] bpf/tests: Add exhaustive tests of ALU register combinations Johan Almbladh
2021-10-01 13:03 ` [PATCH bpf-next 08/10] bpf/tests: Add exhaustive tests of BPF_ATOMIC " Johan Almbladh
2021-10-01 13:03 ` [PATCH bpf-next 09/10] bpf/tests: Add test of ALU shifts with operand register aliasing Johan Almbladh
2021-10-01 13:03 ` [PATCH bpf-next 10/10] bpf/tests: Add test of LDX_MEM with operand aliasing Johan Almbladh
2021-10-01 15:10 ` patchwork-bot+netdevbpf [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=163310100819.11228.15860171916823233197.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=iii@linux.ibm.com \
--cc=johan.almbladh@anyfinetworks.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@cilium.io \
--cc=songliubraving@fb.com \
--cc=yangtiezhu@loongson.cn \
--cc=yhs@fb.com \
--subject='Re: [PATCH bpf-next 00/10] bpf/tests: Extend eBPF JIT test suite' \
/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
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).