Yonghong Song 9d100a19ff tools/bpf: print out btf log at LIBBPF_WARN level ... Currently, the btf log is allocated and printed out in case of error at LIBBPF_DEBUG level. Such logs from kernel are very important for debugging. For example, bpf syscall BPF_PROG_LOAD command can get verifier logs back to user space. In function load_program() of libbpf.c, the log buffer is allocated unconditionally and printed out at pr_warning() level. Let us do the similar thing here for btf. Allocate buffer unconditionally and print out error logs at pr_warning() level. This can reduce one global function and optimize for common situations where pr_warning() is activated either by default or by user supplied debug output function. Signed-off-by: Yonghong Song <yhs@fb.com> Signed-off-by: Alexei Starovoitov <ast@kernel.org>		2019-02-04 09:40:58 -08:00
..
api	perf tools: Fix tracing_path_mount proper path	2018-10-16 12:27:46 -03:00
bpf	tools/bpf: print out btf log at LIBBPF_WARN level	2019-02-04 09:40:58 -08:00
lockdep	tools/lib/lockdep/tests: Test the lockdep_reset_lock() implementation	2018-12-11 14:54:51 +01:00
subcmd	tools lib subcmd: Don't add the kernel sources to the include path	2018-12-18 12:23:56 -03:00
symbol	tools lib symbols: Introduce kallsyms__is_function()	2018-04-26 13:47:14 -03:00
traceevent	tools lib traceevent: Remove tep_data_event_from_type() API	2019-01-08 13:28:13 -03:00
bitmap.c
find_bit.c	lib: optimize cpumask_next_and()	2018-02-06 18:32:44 -08:00
hweight.c
rbtree.c
str_error_r.c	objtool, perf: Fix GCC 8 -Wrestrict error	2018-03-19 13:51:54 -03:00
string.c
vsprintf.c