summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorAlexei Starovoitov <ast@kernel.org>2019-10-30 23:32:11 +0100
committerDaniel Borkmann <daniel@iogearbox.net>2019-10-31 15:16:59 +0100
commitf1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 (patch)
treeafe8d1f028f919eee5aca4321d544cd24fe465a3 /tools
parentbpf: Fix bpf jit kallsym access (diff)
downloadlinux-f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6.tar.xz
linux-f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6.zip
bpf: Replace prog_raw_tp+btf_id with prog_tracing
The bpf program type raw_tp together with 'expected_attach_type' was the most appropriate api to indicate BTF-enabled raw_tp programs. But during development it became apparent that 'expected_attach_type' cannot be used and new 'attach_btf_id' field had to be introduced. Which means that the information is duplicated in two fields where one of them is ignored. Clean it up by introducing new program type where both 'expected_attach_type' and 'attach_btf_id' fields have specific meaning. In the future 'expected_attach_type' will be extended with other attach points that have similar semantics to raw_tp. This patch is replacing BTF-enabled BPF_PROG_TYPE_RAW_TRACEPOINT with prog_type = BPF_RPOG_TYPE_TRACING expected_attach_type = BPF_TRACE_RAW_TP attach_btf_id = btf_id of raw tracepoint inside the kernel Future patches will add expected_attach_type = BPF_TRACE_FENTRY or BPF_TRACE_FEXIT where programs have the same input context and the same helpers, but different attach points. Signed-off-by: Alexei Starovoitov <ast@kernel.org> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Acked-by: Andrii Nakryiko <andriin@fb.com> Acked-by: Martin KaFai Lau <kafai@fb.com> Link: https://lore.kernel.org/bpf/20191030223212.953010-2-ast@kernel.org
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions