diff options
author | Alexei Starovoitov <ast@fb.com> | 2016-09-02 03:37:24 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-09-02 19:46:44 +0200 |
commit | aa6a5f3cb2b2edc5b9aab0b4fdfdfa9c3b5096a8 (patch) | |
tree | 8cf03de3cadf8e080094e1d1c671ada0d85d1ec2 /samples | |
parent | bpf: perf_event progs should only use preallocated maps (diff) | |
download | linux-aa6a5f3cb2b2edc5b9aab0b4fdfdfa9c3b5096a8.tar.xz linux-aa6a5f3cb2b2edc5b9aab0b4fdfdfa9c3b5096a8.zip |
perf, bpf: add perf events core support for BPF_PROG_TYPE_PERF_EVENT programs
Allow attaching BPF_PROG_TYPE_PERF_EVENT programs to sw and hw perf events
via overflow_handler mechanism.
When program is attached the overflow_handlers become stacked.
The program acts as a filter.
Returning zero from the program means that the normal perf_event_output handler
will not be called and sampling event won't be stored in the ring buffer.
The overflow_handler_context==NULL is an additional safety check
to make sure programs are not attached to hw breakpoints and watchdog
in case other checks (that prevent that now anyway) get accidentally
relaxed in the future.
The program refcnt is incremented in case perf_events are inhereted
when target task is forked.
Similar to kprobe and tracepoint programs there is no ioctl to
detach the program or swap already attached program. The user space
expected to close(perf_event_fd) like it does right now for kprobe+bpf.
That restriction simplifies the code quite a bit.
The invocation of overflow_handler in __perf_event_overflow() is now
done via READ_ONCE, since that pointer can be replaced when the program
is attached while perf_event itself could have been active already.
There is no need to do similar treatment for event->prog, since it's
assigned only once before it's accessed.
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions