diff options
| author |   Daniel Borkmann <daniel@iogearbox.net> | 2019-10-31 15:16:59 +0100 |
|---|---|---|
| committer | Daniel Borkmann <daniel@iogearbox.net> | 2019-10-31 15:17:14 +0100 |
| commit | 06087114606c416892bd67c5fde9f0d498afb287 (patch) | |
| tree | 6193b759236e868ec2bdc75f9107a43123dbca13 /tools/testing/selftests/bpf/test_offload.py | |
| parent | bpf: Fix bpf jit kallsym access (diff) | |
| parent | libbpf: Add support for prog_tracing (diff) | |
| download | linux-dev-06087114606c416892bd67c5fde9f0d498afb287.tar.xz linux-dev-06087114606c416892bd67c5fde9f0d498afb287.zip | |
Merge branch 'bpf-cleanup-btf-raw-tp'
Alexei Starovoitov says:
====================
v1->v2: addressed Andrii's feedback
When BTF-enabled raw_tp were introduced the plan was to follow up
with BTF-enabled kprobe and kretprobe reusing PROG_RAW_TRACEPOINT
and PROG_KPROBE types. But k[ret]probe expect pt_regs while
BTF-enabled program ctx will be the same as raw_tp.
kretprobe is indistinguishable from kprobe while BTF-enabled
kretprobe will have access to retval while kprobe will not.
Hence PROG_KPROBE type is not reusable and reusing
PROG_RAW_TRACEPOINT no longer fits well.
Hence introduce 'umbrella' prog type BPF_PROG_TYPE_TRACING
that will cover different BTF-enabled tracing attach points.
The changes make libbpf side cleaner as well.
check_attach_btf_id() is cleaner too.
====================
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'tools/testing/selftests/bpf/test_offload.py')
0 files changed, 0 insertions, 0 deletions