Thread (7 messages) flat view 7 messages, 3 authors, 2020-03-23

Re: [PATCH bpf-next v5 0/2] Refactor perf_event sample user program with libbpf bpf_link

From: Daniel Borkmann <daniel@iogearbox.net>
Date: 2020-03-23 21:39:01
Also in: bpf

On 3/21/20 11:04 AM, Daniel T. Lee wrote:
Currently, some samples are using ioctl for enabling perf_event and
attaching BPF programs to this event. However, the bpf_program__attach
of libbpf(using bpf_link) is much more intuitive than the previous
method using ioctl.

bpf_program__attach_perf_event manages the enable of perf_event and
attach of BPF programs to it, so there's no neeed to do this
directly with ioctl.

In addition, bpf_link provides consistency in the use of API because it
allows disable (detach, destroy) for multiple events to be treated as
one bpf_link__destroy.

To refactor samples with using this libbpf API, the bpf_load in the
samples were removed and migrated to libbbpf. Because read_trace_pipe
is used in bpf_load, multiple samples cannot be migrated to libbpf,
this function was moved to trace_helpers.
Applied, thanks!
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help