diff options
| author | Alexei Starovoitov <ast@kernel.org> | 2023-05-19 10:06:45 -0700 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2023-05-19 10:06:53 -0700 |
| commit | 9343184cb31fef673566ff37c41a9f418deb9de3 (patch) | |
| tree | b728ae6b18abafff2ada4dcf683230c1b929ebad /tools/bpf/bpftool/bash-completion | |
| parent | effcf62416240e5ec0eded0ea2644c48d2c7c9f1 (diff) | |
| parent | d7e45eb4802bbb3343624711e43d23b22fe7cc55 (diff) | |
Merge branch 'bpf: Show target_{obj,btf}_id for tracing link'
Yafang Shao says:
====================
The target_btf_id can help us understand which kernel function is
linked by a tracing prog. The target_btf_id and target_obj_id have
already been exposed to userspace, so we just need to show them.
For some other link types like perf_event and kprobe_multi, it is not
easy to find which functions are attached either. We may support
->fill_link_info for them in the future.
v1->v2:
- Skip showing them in the plain output for the old kernels. (Quentin)
- Coding improvement. (Andrii)
====================
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/bpf/bpftool/bash-completion')
0 files changed, 0 insertions, 0 deletions