tools/include/uapi/asm/bpf_perf_event.h

File Facts

System

Linux kernel

Corpus path

tools/include/uapi/asm/bpf_perf_event.h

Extension

.h

Size

493 bytes

Lines

14

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

• ../../arch/arm64/include/uapi/asm/bpf_perf_event.h
• ../../arch/arc/include/uapi/asm/bpf_perf_event.h
• ../../arch/s390/include/uapi/asm/bpf_perf_event.h
• ../../arch/riscv/include/uapi/asm/bpf_perf_event.h
• ../../arch/loongarch/include/uapi/asm/bpf_perf_event.h
• uapi/asm-generic/bpf_perf_event.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#if defined(__aarch64__)
#include "../../arch/arm64/include/uapi/asm/bpf_perf_event.h"
#elif defined(__arc__)
#include "../../arch/arc/include/uapi/asm/bpf_perf_event.h"
#elif defined(__s390__)
#include "../../arch/s390/include/uapi/asm/bpf_perf_event.h"
#elif defined(__riscv)
#include "../../arch/riscv/include/uapi/asm/bpf_perf_event.h"
#elif defined(__loongarch__)
#include "../../arch/loongarch/include/uapi/asm/bpf_perf_event.h"
#else
#include <uapi/asm-generic/bpf_perf_event.h>
#endif

Annotation

• Immediate include surface: `../../arch/arm64/include/uapi/asm/bpf_perf_event.h`, `../../arch/arc/include/uapi/asm/bpf_perf_event.h`, `../../arch/s390/include/uapi/asm/bpf_perf_event.h`, `../../arch/riscv/include/uapi/asm/bpf_perf_event.h`, `../../arch/loongarch/include/uapi/asm/bpf_perf_event.h`, `uapi/asm-generic/bpf_perf_event.h`.
• 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.