From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org,
kernel-team@cloudflare.com, tony.ambardar@gmail.com
Subject: Re: [PATCH bpf-next 0/2] Allow mixing bpf2bpf calls with tail calls on arm64
Date: Tue, 21 Jun 2022 17:00:15 +0000 [thread overview]
Message-ID: <165583081558.23938.2888618327676957069.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220617105735.733938-1-jakub@cloudflare.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 17 Jun 2022 12:57:33 +0200 you wrote:
> This patch set enables using bpf2bpf calls together with tail calls on arm64.
> Patch 1 was borrowed from an RFC series for MIPS JIT [1].
> Patch 2 gives an explanation of tweaks needed to arm64 BPF JIT.
>
> [1] https://lore.kernel.org/bpf/77dfea2d224e7545e5e4d3f350721d27e5a77b0d.1633392335.git.Tony.Ambardar@gmail.com/#r
>
> Jakub Sitnicki (1):
> bpf: arm64: Keep tail call count across bpf2bpf calls
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: x64: Add predicate for bpf2bpf with tailcalls support in JIT
https://git.kernel.org/bpf/bpf-next/c/95acd8817e66
- [bpf-next,2/2] bpf: arm64: Keep tail call count across bpf2bpf calls
https://git.kernel.org/bpf/bpf-next/c/d4609a5d8c70
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:[~2022-06-21 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:57 [PATCH bpf-next 0/2] Allow mixing bpf2bpf calls with tail calls on arm64 Jakub Sitnicki
2022-06-17 10:57 ` [PATCH bpf-next 1/2] bpf: x64: Add predicate for bpf2bpf with tailcalls support in JIT Jakub Sitnicki
2022-06-17 10:57 ` [PATCH bpf-next 2/2] bpf: arm64: Keep tail call count across bpf2bpf calls Jakub Sitnicki
2022-06-21 17:00 ` 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=165583081558.23938.2888618327676957069.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=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=tony.ambardar@gmail.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).