[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190116010746.3620112-1-yhs@fb.com>
Date: Tue, 15 Jan 2019 17:07:46 -0800
From: Yonghong Song <yhs@...com>
To: <netdev@...r.kernel.org>
CC: Alexei Starovoitov <ast@...com>,
Daniel Borkmann <daniel@...earbox.net>, <kernel-team@...com>,
Yonghong Song <yhs@...com>
Subject: [PATCH bpf-next 0/5] bpf: support __int128 in BTF
Previous maximum supported integer bit width is 64. But
the __int128 type has been supported by most (if not all)
64bit architectures including bpf for both gcc and clang.
The kernel itself uses __int128 for x64 and arm64. Some bcc tools
are using __int128 in bpf programs to describe ipv6 addresses.
Without 128bit int support, the vmlinux BTF won't work and
those bpf programs using __int128 cannot utilize BTF.
This patch set implemented BTF __int128 support.
Patch #1 added __int128 support in the kernel.
Patch #2 added raw test for __int128 in test_btf.
Patch #3 refactored test_btf bpffs pretty print test to
allow different map value structures.
Patch #4 added bpffs pretty print test for __int128.
Patch #5 added __int128 support in bpftool map pretty dumper.
Yonghong Song (5):
bpf: btf: support 128 bit integer type
tools/bpf: add int128 raw test in test_btf
tools/bpf: refactor test_btf pretty printing for multiple map value
formats
tools/bpf: add bpffs pretty print test for int128
tools/bpf: support __int128 in bpftool map pretty dumper
kernel/bpf/btf.c | 104 +++++++--
tools/bpf/bpftool/btf_dumper.c | 98 +++++++--
tools/testing/selftests/bpf/test_btf.c | 284 +++++++++++++++++++++----
3 files changed, 418 insertions(+), 68 deletions(-)
--
2.17.1
Powered by blists - more mailing lists