diff options
| author |   Menglong Dong <imagedong@tencent.com> | 2023-03-06 14:48:31 +0800 |
|---|---|---|
| committer |   Andrii Nakryiko <andrii@kernel.org> | 2023-03-06 09:38:04 -0800 |
| commit | f8b299bc6a0f8695d4005ecff29773c79a1d29af (patch) | |
| tree | 53a17be54b077eafeb7b1075c52e52002d058334 /scripts/generate_rust_analyzer.py | |
| parent | tools/resolve_btfids: Add /libsubcmd to .gitignore (diff) | |
| download | linux-rng-f8b299bc6a0f8695d4005ecff29773c79a1d29af.tar.xz linux-rng-f8b299bc6a0f8695d4005ecff29773c79a1d29af.zip | |
libbpf: Add support to set kprobe/uprobe attach mode
By default, libbpf will attach the kprobe/uprobe BPF program in the
latest mode that supported by kernel. In this patch, we add the support
to let users manually attach kprobe/uprobe in legacy or perf mode.
There are 3 mode that supported by the kernel to attach kprobe/uprobe:
LEGACY: create perf event in legacy way and don't use bpf_link
PERF: create perf event with perf_event_open() and don't use bpf_link
Signed-off-by: Menglong Dong <imagedong@tencent.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Reviewed-by: Biao Jiang <benbjiang@tencent.com>
Link: create perf event with perf_event_open() and use bpf_link
Link: https://lore.kernel.org/bpf/20230113093427.1666466-1-imagedong@tencent.com/
Link: https://lore.kernel.org/bpf/20230306064833.7932-2-imagedong@tencent.com
Users now can manually choose the mode with
bpf_program__attach_uprobe_opts()/bpf_program__attach_kprobe_opts().
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions