From: Yonghong Song <yhs@fb.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf-next 05/12] bpftool: Add btf enum64 support
Date: Tue, 10 May 2022 15:43:31 -0700 [thread overview]
Message-ID: <a4f05ee9-f192-c3b5-6961-0db80755d5fd@fb.com> (raw)
In-Reply-To: <CAEf4BzY51u6GW7Sj8vNBsvcu7Gt1h13v8bWz=qb2p6vsGcaqEQ@mail.gmail.com>
On 5/9/22 4:31 PM, Andrii Nakryiko wrote:
> On Sun, May 1, 2022 at 12:00 PM Yonghong Song <yhs@fb.com> wrote:
>>
>> Add BTF_KIND_ENUM64 support.
>> For example, the following enum is defined in uapi bpf.h.
>> $ cat core.c
>> enum A {
>> BPF_F_INDEX_MASK = 0xffffffffULL,
>> BPF_F_CURRENT_CPU = BPF_F_INDEX_MASK,
>> BPF_F_CTXLEN_MASK = (0xfffffULL << 32),
>> } g;
>> Compiled with
>> clang -target bpf -O2 -g -c core.c
>> Using bpftool to dump types and generate format C file:
>> $ bpftool btf dump file core.o
>> ...
>> [1] ENUM64 'A' size=8 vlen=3
>> 'BPF_F_INDEX_MASK' val=4294967295ULL
>> 'BPF_F_CURRENT_CPU' val=4294967295ULL
>> 'BPF_F_CTXLEN_MASK' val=4503595332403200ULL
>> $ bpftool btf dump file core.o format c
>> ...
>> enum A {
>> BPF_F_INDEX_MASK = 4294967295ULL,
>> BPF_F_CURRENT_CPU = 4294967295ULL,
>> BPF_F_CTXLEN_MASK = 4503595332403200ULL,
>
> maybe we should have some heuristic that if the value is "big enough"
> (e.g., larger than 1-128 millions) and is unsigned we should emit it
> as hex?
I thought about this. But since you are also suggesting this, I will
do this (greater than 1 million).
>
>> };
>> ...
>>
>> The 64bit value is represented properly in BTF and C dump.
>>
>> Signed-off-by: Yonghong Song <yhs@fb.com>
>> ---
>
> just minor nits, LGTM
>
> Acked-by: Andrii Nakryiko <andrii@kernel.org>
>
>> tools/bpf/bpftool/btf.c | 47 ++++++++++++++++++++++++++++++++--
>> tools/bpf/bpftool/btf_dumper.c | 32 +++++++++++++++++++++++
>> tools/bpf/bpftool/gen.c | 1 +
>> 3 files changed, 78 insertions(+), 2 deletions(-)
>>
>
> [...]
>> + case BTF_KIND_ENUM64: {
>> + const struct btf_enum64 *v = (const void *)(t + 1);
>
> can use btf_enum64() helper from libbpf?
>
>> + __u16 vlen = BTF_INFO_VLEN(t->info);
>
> btf_vlen(t)
I copied the code from above BTF_KIND_ENUM. But I certainly can do this.
>
>> + int i;
>> +
>> + if (json_output) {
>> + jsonw_uint_field(w, "size", t->size);
>> + jsonw_uint_field(w, "vlen", vlen);
>> + jsonw_name(w, "values");
>> + jsonw_start_array(w);
>> + } else {
>> + printf(" size=%u vlen=%u", t->size, vlen);
>> + }
>> + for (i = 0; i < vlen; i++, v++) {
>> + const char *name = btf_str(btf, v->name_off);
>> + __u64 val = (__u64)v->hi32 << 32 | v->lo32;
>
> () ?
okay.
>
>> +
>> + if (json_output) {
>> + jsonw_start_object(w);
>> + jsonw_string_field(w, "name", name);
>> + if (btf_kflag(t))
>> + jsonw_uint_field(w, "val", val);
>> + else
>> + jsonw_int_field(w, "val", val);
>> + jsonw_end_object(w);
>> + } else {
>> + if (btf_kflag(t))
>> + printf("\n\t'%s' val=%lluULL", name, val);
>> + else
>> + printf("\n\t'%s' val=%lldLL", name, val);
>> }
>> }
>> if (json_output)
>> diff --git a/tools/bpf/bpftool/btf_dumper.c b/tools/bpf/bpftool/btf_dumper.c
>> index f5dddf8ef404..f9f38384b9a6 100644
>> --- a/tools/bpf/bpftool/btf_dumper.c
>> +++ b/tools/bpf/bpftool/btf_dumper.c
>> @@ -182,6 +182,35 @@ static int btf_dumper_enum(const struct btf_dumper *d,
>> return 0;
>> }
>>
>> +static int btf_dumper_enum64(const struct btf_dumper *d,
>> + const struct btf_type *t,
>> + const void *data)
>> +{
>> + const struct btf_enum64 *enums = btf_enum64(t);
>> + __u32 hi32, lo32;
>> + __u64 value;
>> + __u16 i;
>> +
>> + if (t->size != 8)
>> + return -EINVAL;
>
> no need
sure.
>
>> +
>> + value = *(__u64 *)data;
>> + hi32 = value >> 32;
>> + lo32 = (__u32)value;
>> +
>
> [...]
next prev parent reply other threads:[~2022-05-10 22:43 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 19:00 [PATCH bpf-next 00/12] bpf: Add 64bit enum value support Yonghong Song
2022-05-01 19:00 ` [PATCH bpf-next 01/12] bpf: Add btf enum64 support Yonghong Song
2022-05-09 0:33 ` Dave Marchevsky
2022-05-09 22:29 ` Andrii Nakryiko
2022-05-10 22:06 ` Yonghong Song
2022-05-10 23:18 ` Andrii Nakryiko
2022-05-11 0:17 ` Yonghong Song
2022-05-01 19:00 ` [PATCH bpf-next 02/12] libbpf: Permit 64bit relocation value Yonghong Song
2022-05-09 1:06 ` Dave Marchevsky
2022-05-10 19:35 ` Yonghong Song
2022-05-09 22:37 ` Andrii Nakryiko
2022-05-10 22:14 ` Yonghong Song
2022-05-10 23:19 ` Andrii Nakryiko
2022-05-01 19:00 ` [PATCH bpf-next 03/12] libbpf: Fix an error in 64bit relocation value computation Yonghong Song
2022-05-09 0:55 ` Dave Marchevsky
2022-05-09 0:56 ` Dave Marchevsky
2022-05-09 22:37 ` Andrii Nakryiko
2022-05-10 22:11 ` Yonghong Song
2022-05-01 19:00 ` [PATCH bpf-next 04/12] libbpf: Add btf enum64 support Yonghong Song
2022-05-03 17:22 ` kernel test robot
2022-05-05 22:44 ` Yonghong Song
2022-05-09 23:25 ` Andrii Nakryiko
2022-05-10 22:40 ` Yonghong Song
2022-05-10 23:02 ` Yonghong Song
2022-05-10 23:40 ` Andrii Nakryiko
2022-05-10 23:38 ` Andrii Nakryiko
2022-05-11 0:39 ` Yonghong Song
2022-05-11 17:43 ` Andrii Nakryiko
2022-05-11 18:56 ` Yonghong Song
2022-05-01 19:00 ` [PATCH bpf-next 05/12] bpftool: " Yonghong Song
2022-05-09 23:31 ` Andrii Nakryiko
2022-05-10 22:43 ` Yonghong Song [this message]
2022-05-01 19:00 ` [PATCH bpf-next 06/12] selftests/bpf: Fix selftests failure Yonghong Song
2022-05-09 2:21 ` Dave Marchevsky
2022-05-10 19:40 ` Yonghong Song
2022-05-09 23:34 ` Andrii Nakryiko
2022-05-10 22:44 ` Yonghong Song
2022-05-01 19:00 ` [PATCH bpf-next 07/12] selftests/bpf: Test new libbpf enum32/enum64 API functions Yonghong Song
2022-05-01 19:00 ` [PATCH bpf-next 08/12] selftests/bpf: Add BTF_KIND_ENUM64 unit tests Yonghong Song
2022-05-01 19:00 ` [PATCH bpf-next 09/12] selftests/bpf: Test BTF_KIND_ENUM64 for deduplication Yonghong Song
2022-05-09 23:37 ` Andrii Nakryiko
2022-05-10 22:44 ` Yonghong Song
2022-05-01 19:00 ` [PATCH bpf-next 10/12] selftests/bpf: add a test for enum64 value relocation Yonghong Song
2022-05-09 23:38 ` Andrii Nakryiko
2022-05-10 22:45 ` Yonghong Song
2022-05-01 19:00 ` [PATCH bpf-next 11/12] selftests/bpf: Clarify llvm dependency with possible selftest failures Yonghong Song
2022-05-01 19:01 ` [PATCH bpf-next 12/12] docs/bpf: Update documentation for BTF_KIND_ENUM64 support Yonghong Song
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=a4f05ee9-f192-c3b5-6961-0db80755d5fd@fb.com \
--to=yhs@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@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