[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<176919661035.2689746.16918451024463235457.git-patchwork-notify@kernel.org>
Date: Fri, 23 Jan 2026 19:30:10 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Sitnicki <jakub@...udflare.com>
Cc: bpf@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
john.fastabend@...il.com, andrii@...nel.org, martin.lau@...ux.dev,
eddyz87@...il.com, song@...nel.org, yonghong.song@...ux.dev,
kpsingh@...nel.org, sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org,
ameryhung@...il.com, netdev@...r.kernel.org, kernel-team@...udflare.com,
martin.lau@...nel.org
Subject: Re: [PATCH bpf-next v2 0/4] Switch from kfuncs to direct helper calls
in prologue/epilogue
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Fri, 23 Jan 2026 18:05:17 +0100 you wrote:
> This series enables direct helper calls using BPF_EMIT_CALL from prologue
> and epilogue code generated by verifier ops. The goal is to simplify the
> calling convention and remove kfunc support from prologue/epilogue, as
> suggested by Alexei [1].
>
> Patch 1 adds the infrastructure to mark direct helper calls as finalized
> (already resolved) so the verifier skips the imm fixup.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/4] bpf, verifier: Support direct helper calls from prologue/epilogue
https://git.kernel.org/bpf/bpf-next/c/af46ae41da7c
- [bpf-next,v2,2/4] bpf: net_sched: Use direct helper calls instead of kfuncs in pro/epilogue
https://git.kernel.org/bpf/bpf-next/c/5c2106d44168
- [bpf-next,v2,3/4] selftests/bpf: Remove tests for prologue/epilogue with kfuncs
https://git.kernel.org/bpf/bpf-next/c/d3ddc749df28
- [bpf-next,v2,4/4] bpf: Remove kfunc support in prologue and epilogue
https://git.kernel.org/bpf/bpf-next/c/68d23a660c4f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists