diff options
| author | Daniel Borkmann <daniel@iogearbox.net> | 2019-01-16 22:53:45 +0100 |
|---|---|---|
| committer | Daniel Borkmann <daniel@iogearbox.net> | 2019-01-16 22:53:46 +0100 |
| commit | e13279e21183667e5462546ffbfeab2764be631b (patch) | |
| tree | f6ff1ab57a61c0dfe884634943c0bd16fd93e922 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | libbpf: don't define CC and AR (diff) | |
| parent | tools/bpf: support __int128 in bpftool map pretty dumper (diff) | |
| download | linux-e13279e21183667e5462546ffbfeab2764be631b.tar.gz linux-e13279e21183667e5462546ffbfeab2764be631b.zip | |
Merge branch 'bpf-int128-btf'
Yonghong Song says:
====================
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 therefore implements BTF __int128 support.
====================
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions