tools/testing/selftests/bpf/progs/test_trampoline_count.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/bpf/progs/test_trampoline_count.c

Extension

.c

Size

448 bytes

Lines

25

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

• linux/bpf.h
• bpf/bpf_helpers.h
• bpf/bpf_tracing.h

Detected Declarations

• function BPF_PROG
• function BPF_PROG
• function BPF_PROG

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
#include <linux/bpf.h>
#include <bpf/bpf_helpers.h>
#include <bpf/bpf_tracing.h>

SEC("fentry/bpf_testmod_trampoline_count_test")
int BPF_PROG(fentry_test)
{
	return 0;
}

SEC("fmod_ret/bpf_testmod_trampoline_count_test")
int BPF_PROG(fmod_ret_test, int ret)
{
	return 0;
}

SEC("fexit/bpf_testmod_trampoline_count_test")
int BPF_PROG(fexit_test, int ret)
{
	return 0;
}

char _license[] SEC("license") = "GPL";

Annotation

• Immediate include surface: `linux/bpf.h`, `bpf/bpf_helpers.h`, `bpf/bpf_tracing.h`.
• Detected declarations: `function BPF_PROG`, `function BPF_PROG`, `function BPF_PROG`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.