From: Yonghong Song <yhs@fb.com>
To: <netdev@vger.kernel.org>
Cc: Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>, <kernel-team@fb.com>,
Yonghong Song <yhs@fb.com>
Subject: [PATCH bpf-next 0/5] bpf: support __int128 in BTF
Date: Tue, 15 Jan 2019 17:07:46 -0800 [thread overview]
Message-ID: <20190116010746.3620112-1-yhs@fb.com> (raw)
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
next reply other threads:[~2019-01-16 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 1:07 Yonghong Song [this message]
2019-01-16 1:07 ` [PATCH bpf-next 1/5] bpf: btf: support 128 bit integer type Yonghong Song
2019-01-16 1:07 ` [PATCH bpf-next 2/5] tools/bpf: add int128 raw test in test_btf Yonghong Song
2019-01-16 1:07 ` [PATCH bpf-next 3/5] tools/bpf: refactor test_btf pretty printing for multiple map value formats Yonghong Song
2019-01-16 1:07 ` [PATCH bpf-next 4/5] tools/bpf: add bpffs pretty print test for int128 Yonghong Song
2019-01-16 1:07 ` [PATCH bpf-next 5/5] tools/bpf: support __int128 in bpftool map pretty dumper Yonghong Song
2019-01-16 22:01 ` [PATCH bpf-next 0/5] bpf: support __int128 in BTF Daniel Borkmann
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=20190116010746.3620112-1-yhs@fb.com \
--to=yhs@fb.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).