diff options
| author | Hoyeon Lee <hoyeon.lee@suse.com> | 2026-04-01 23:29:30 +0900 |
|---|---|---|
| committer | Andrii Nakryiko <andrii@kernel.org> | 2026-04-02 13:23:19 -0700 |
| commit | e1621c752865dcd682d9f52c3566ba3c6b9ee589 (patch) | |
| tree | 79e58d5b851165f27415bd76596c56c08072a5ef /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | f547cf79475fdfee39dcab07a2b381026427a0b3 (diff) | |
libbpf: Clarify raw-address single kprobe attach behavior
bpf_program__attach_kprobe_opts() documents single-kprobe attach
through func_name, with an optional offset. For the PMU-based path,
func_name = NULL with an absolute address in offset already works as
well, but that is not described in the API.
This commit clarifies this existing non-legacy behavior. For PMU-based
attach, callers can use func_name = NULL with an absolute address in
offset as the raw-address form. For legacy tracefs/debugfs kprobes,
reject this form explicitly.
Signed-off-by: Hoyeon Lee <hoyeon.lee@suse.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: Jiri Olsa <jolsa@kernel.org>
Link: https://lore.kernel.org/bpf/20260401143116.185049-3-hoyeon.lee@suse.com
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
