Andrii Nakryiko 44ad23dfbc libbpf: Handle BTF pointer sizes more carefully ... With libbpf and BTF it is pretty common to have libbpf built for one architecture, while BTF information was generated for a different architecture (typically, but not always, BPF). In such case, the size of a pointer might differ betweem architectures. libbpf previously was always making an assumption that pointer size for BTF is the same as native architecture pointer size, but that breaks for cases where libbpf is built as 32-bit library, while BTF is for 64-bit architecture. To solve this, add heuristic to determine pointer size by searching for `long` or `unsigned long` integer type and using its size as a pointer size. Also, allow to override the pointer size with a new API btf__set_pointer_size(), for cases where application knows which pointer size should be used. User application can check what libbpf "guessed" by looking at the result of btf__pointer_size(). If it's not 0, then libbpf successfully determined a pointer size, otherwise native arch pointer size will be used. For cases where BTF is parsed from ELF file, use ELF's class (32-bit or 64-bit) to determine pointer size. Fixes: 8a138aed4a ("bpf: btf: Add BTF support to libbpf") Fixes: 351131b51c ("libbpf: add btf_dump API for BTF-to-C conversion") Signed-off-by: Andrii Nakryiko <andriin@fb.com> Signed-off-by: Alexei Starovoitov <ast@kernel.org> Link: https://lore.kernel.org/bpf/20200813204945.1020225-5-andriin@fb.com		2020-08-13 16:45:41 -07:00
..
api
bpf	libbpf: Handle BTF pointer sizes more carefully	2020-08-13 16:45:41 -07:00
lockdep
perf
subcmd	libsubcmd: Fix OPT_CALLBACK_SET()	2020-07-17 09:33:06 -03:00
symbol
traceevent	libtraceevent: Fix build with binutils 2.35	2020-07-31 09:31:55 -03:00
argv_split.c
bitmap.c
ctype.c
find_bit.c
hweight.c
rbtree.c
str_error_r.c
string.c
vsprintf.c
zalloc.c