diff options
author | Quentin Monnet | 2019-05-24 12:36:47 +0200 |
---|---|---|
committer | Daniel Borkmann | 2019-05-28 11:03:26 +0200 |
commit | 60276f9849988d3d3a54943c9ec27222c5819dae (patch) | |
tree | 8da64a5ab5620886f7e3d1c88f877f44828e3720 /tools/bpf | |
parent | tools: bpftool: add -d option to get debug output from libbpf (diff) | |
download | kernel-qcow2-linux-60276f9849988d3d3a54943c9ec27222c5819dae.tar.gz kernel-qcow2-linux-60276f9849988d3d3a54943c9ec27222c5819dae.tar.xz kernel-qcow2-linux-60276f9849988d3d3a54943c9ec27222c5819dae.zip |
libbpf: add bpf_object__load_xattr() API function to pass log_level
libbpf was recently made aware of the log_level attribute for programs,
used to specify the level of information expected to be dumped by the
verifier. Function bpf_prog_load_xattr() got support for this log_level
parameter.
But some applications using libbpf rely on another function to load
programs, bpf_object__load(), which does accept any parameter for log
level. Create an API function based on bpf_object__load(), but accepting
an "attr" object as a parameter. Then add a log_level field to that
object, so that applications calling the new bpf_object__load_xattr()
can pick the desired log level.
v3:
- Rewrite commit log.
v2:
- We are in a new cycle, bump libbpf extraversion number.
Signed-off-by: Quentin Monnet <quentin.monnet@netronome.com>
Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'tools/bpf')
0 files changed, 0 insertions, 0 deletions