tools/testing/selftests/bpf/progs/timer_interrupt.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/timer_interrupt.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/timer_interrupt.c- Extension
.c- Size
- 982 bytes
- Lines
- 49
- 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
vmlinux.hbpf/bpf_helpers.hbpf/bpf_tracing.hbpf_experimental.h
Detected Declarations
struct elemfunction timer_in_interruptfunction BPF_PROG
Annotated Snippet
struct elem {
struct bpf_timer t;
};
struct {
__uint(type, BPF_MAP_TYPE_ARRAY);
__uint(max_entries, 1);
__type(key, int);
__type(value, struct elem);
} array SEC(".maps");
static int timer_in_interrupt(void *map, int *key, struct bpf_timer *timer)
{
preempt_count = get_preempt_count();
in_interrupt_cb = bpf_in_interrupt();
return 0;
}
SEC("fentry/bpf_fentry_test1")
int BPF_PROG(test_timer_interrupt)
{
struct bpf_timer *timer;
int key = 0;
timer = bpf_map_lookup_elem(&array, &key);
if (!timer)
return 0;
in_interrupt = bpf_in_interrupt();
bpf_timer_init(timer, &array, CLOCK_MONOTONIC);
bpf_timer_set_callback(timer, timer_in_interrupt);
bpf_timer_start(timer, 0, 0);
return 0;
}
Annotation
- Immediate include surface: `vmlinux.h`, `bpf/bpf_helpers.h`, `bpf/bpf_tracing.h`, `bpf_experimental.h`.
- Detected declarations: `struct elem`, `function timer_in_interrupt`, `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.