tools/tracing/rtla/example/timerlat_bpf_action.c
Source file repositories/reference/linux-study-clean/tools/tracing/rtla/example/timerlat_bpf_action.c
File Facts
- System
- Linux kernel
- Corpus path
tools/tracing/rtla/example/timerlat_bpf_action.c- Extension
.c- Size
- 413 bytes
- Lines
- 17
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/bpf.hbpf/bpf_tracing.h
Detected Declarations
struct trace_event_raw_timerlat_samplefunction action_handler
Annotated Snippet
struct trace_event_raw_timerlat_sample {
unsigned long long timer_latency;
} __attribute__((preserve_access_index));
SEC("tp/timerlat_action")
int action_handler(struct trace_event_raw_timerlat_sample *tp_args)
{
bpf_printk("Latency: %lld\n", tp_args->timer_latency);
return 0;
}
Annotation
- Immediate include surface: `linux/bpf.h`, `bpf/bpf_tracing.h`.
- Detected declarations: `struct trace_event_raw_timerlat_sample`, `function action_handler`.
- 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.