From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com
Subject: Re: [PATCH bpf-next v5 00/17] bpf: Add 64bit enum value support
Date: Tue, 07 Jun 2022 17:40:17 +0000 [thread overview]
Message-ID: <165462361769.5218.5561986964163226721.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220607062554.3716237-1-yhs@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 6 Jun 2022 23:25:54 -0700 you wrote:
> Currently, btf only supports upto 32bit enum value with BTF_KIND_ENUM.
> But in kernel, some enum has 64bit values, e.g., in uapi bpf.h, we have
> enum {
> BPF_F_INDEX_MASK = 0xffffffffULL,
> BPF_F_CURRENT_CPU = BPF_F_INDEX_MASK,
> BPF_F_CTXLEN_MASK = (0xfffffULL << 32),
> };
> With BTF_KIND_ENUM, the value for BPF_F_CTXLEN_MASK will be encoded
> as 0 which is incorrect.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,01/17] bpf: Add btf enum64 support
https://git.kernel.org/bpf/bpf-next/c/6089fb325cf7
- [bpf-next,v5,02/17] libbpf: Permit 64bit relocation value
https://git.kernel.org/bpf/bpf-next/c/776281652ddc
- [bpf-next,v5,03/17] libbpf: Fix an error in 64bit relocation value computation
https://git.kernel.org/bpf/bpf-next/c/b58b2b3a3122
- [bpf-next,v5,04/17] libbpf: Refactor btf__add_enum() for future code sharing
https://git.kernel.org/bpf/bpf-next/c/8479aa752226
- [bpf-next,v5,05/17] libbpf: Add enum64 parsing and new enum64 public API
https://git.kernel.org/bpf/bpf-next/c/dffbbdc2d988
- [bpf-next,v5,06/17] libbpf: Add enum64 deduplication support
https://git.kernel.org/bpf/bpf-next/c/2ef2026349cf
- [bpf-next,v5,07/17] libbpf: Add enum64 support for btf_dump
https://git.kernel.org/bpf/bpf-next/c/d90ec262b35b
- [bpf-next,v5,08/17] libbpf: Add enum64 sanitization
https://git.kernel.org/bpf/bpf-next/c/f2a625889bb8
- [bpf-next,v5,09/17] libbpf: Add enum64 support for bpf linking
https://git.kernel.org/bpf/bpf-next/c/6ec7d79be202
- [bpf-next,v5,10/17] libbpf: Add enum64 relocation support
https://git.kernel.org/bpf/bpf-next/c/23b2a3a8f63a
- [bpf-next,v5,11/17] bpftool: Add btf enum64 support
https://git.kernel.org/bpf/bpf-next/c/58a53978fdf6
- [bpf-next,v5,12/17] selftests/bpf: Fix selftests failure
https://git.kernel.org/bpf/bpf-next/c/d932815a4394
- [bpf-next,v5,13/17] selftests/bpf: Test new enum kflag and enum64 API functions
https://git.kernel.org/bpf/bpf-next/c/2b7301457ffe
- [bpf-next,v5,14/17] selftests/bpf: Add BTF_KIND_ENUM64 unit tests
https://git.kernel.org/bpf/bpf-next/c/3b5325186dfa
- [bpf-next,v5,15/17] selftests/bpf: Test BTF_KIND_ENUM64 for deduplication
https://git.kernel.org/bpf/bpf-next/c/adc26d134ef3
- [bpf-next,v5,16/17] selftests/bpf: Add a test for enum64 value relocations
https://git.kernel.org/bpf/bpf-next/c/f4db3dd5284d
- [bpf-next,v5,17/17] docs/bpf: Update documentation for BTF_KIND_ENUM64 support
https://git.kernel.org/bpf/bpf-next/c/61dbd5982964
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-07 17:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 6:25 [PATCH bpf-next v5 00/17] bpf: Add 64bit enum value support Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 01/17] bpf: Add btf enum64 support Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 02/17] libbpf: Permit 64bit relocation value Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 03/17] libbpf: Fix an error in 64bit relocation value computation Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 04/17] libbpf: Refactor btf__add_enum() for future code sharing Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 05/17] libbpf: Add enum64 parsing and new enum64 public API Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 06/17] libbpf: Add enum64 deduplication support Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 07/17] libbpf: Add enum64 support for btf_dump Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 08/17] libbpf: Add enum64 sanitization Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 09/17] libbpf: Add enum64 support for bpf linking Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 10/17] libbpf: Add enum64 relocation support Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 11/17] bpftool: Add btf enum64 support Yonghong Song
2022-06-07 6:26 ` [PATCH bpf-next v5 12/17] selftests/bpf: Fix selftests failure Yonghong Song
2022-06-07 6:27 ` [PATCH bpf-next v5 13/17] selftests/bpf: Test new enum kflag and enum64 API functions Yonghong Song
2022-06-07 6:27 ` [PATCH bpf-next v5 14/17] selftests/bpf: Add BTF_KIND_ENUM64 unit tests Yonghong Song
2022-06-07 6:27 ` [PATCH bpf-next v5 15/17] selftests/bpf: Test BTF_KIND_ENUM64 for deduplication Yonghong Song
2022-06-07 6:27 ` [PATCH bpf-next v5 16/17] selftests/bpf: Add a test for enum64 value relocations Yonghong Song
2022-06-07 6:27 ` [PATCH bpf-next v5 17/17] docs/bpf: Update documentation for BTF_KIND_ENUM64 support Yonghong Song
2022-06-07 17:40 ` 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=165462361769.5218.5561986964163226721.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=kernel-team@fb.com \
--cc=yhs@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