From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, mykolal@fb.com,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next] bpf: define KF_ARENA_* flags for bpf_arena kfuncs
Date: Sat, 08 Feb 2025 02:30:31 +0000 [thread overview]
Message-ID: <173898183127.2461149.14441400262793958042.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250206003148.2308659-1-ihor.solodrai@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 5 Feb 2025 16:31:48 -0800 you wrote:
> bpf_arena_alloc_pages() and bpf_arena_free_pages() work with the
> bpf_arena pointers [1], which is indicated by the __arena macro in the
> kernel source code:
>
> #define __arena __attribute__((address_space(1)))
>
> However currently this information is absent from the debug data in
> the vmlinux binary. As a consequence, bpf_arena_* kfuncs declarations
> in vmlinux.h (produced by bpftool) do not match prototypes expected by
> the BPF programs attempting to use these functions.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: define KF_ARENA_* flags for bpf_arena kfuncs
https://git.kernel.org/bpf/bpf-next/c/ea145d530a2d
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:[~2025-02-08 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 0:31 [PATCH bpf-next] bpf: define KF_ARENA_* flags for bpf_arena kfuncs Ihor Solodrai
2025-02-08 2:30 ` 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=173898183127.2461149.14441400262793958042.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=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=kernel-team@meta.com \
--cc=mykolal@fb.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