From: patchwork-bot+netdevbpf@kernel.org
To: Jose E. Marchesi <jose.marchesi@oracle.com>
Cc: bpf@vger.kernel.org, alexei.starovoitov@gmail.com,
yonghong.song@linux.dev, eddyz87@gmail.com,
cupertino.miranda@oracle.com, david.faust@oracle.com
Subject: Re: [PATCH] bpf: generate const static pointers for kernel helpers
Date: Tue, 30 Jan 2024 02:00:24 +0000 [thread overview]
Message-ID: <170658002471.10245.3725937330436462463.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240127185031.29854-1-jose.marchesi@oracle.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sat, 27 Jan 2024 19:50:31 +0100 you wrote:
> The generated bpf_helper_defs.h file currently contains definitions
> like this for the kernel helpers, which are static objects:
>
> static void *(*bpf_map_lookup_elem)(void *map, const void *key) = (void *) 1;
>
> These work well in both clang and GCC because both compilers do
> constant propagation with -O1 and higher optimization, resulting in
> `call 1' BPF instructions being generated, which are calls to kernel
> helpers.
>
> [...]
Here is the summary with links:
- bpf: generate const static pointers for kernel helpers
https://git.kernel.org/bpf/bpf-next/c/ff2071a7b7fd
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:[~2024-01-30 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 18:50 [PATCH] bpf: generate const static pointers for kernel helpers Jose E. Marchesi
2024-01-27 20:29 ` Yonghong Song
2024-01-28 11:57 ` Jose E. Marchesi
2024-01-30 2: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=170658002471.10245.3725937330436462463.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--cc=eddyz87@gmail.com \
--cc=jose.marchesi@oracle.com \
--cc=yonghong.song@linux.dev \
/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.