kernel/trace/kprobe_event_gen_test.c

File Facts

System

Linux kernel

Corpus path

kernel/trace/kprobe_event_gen_test.c

Extension

.c

Size

7289 bytes

Lines

277

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

Inferred role

Core OS: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/trace_events.h

Detected Declarations

• function trace_event_file_is_valid
• function test_gen_kprobe_cmd
• function test_gen_kretprobe_cmd
• function kprobe_event_gen_test_init
• function kprobe_event_gen_test_exit
• module init kprobe_event_gen_test_init

Annotated Snippet

module_init(kprobe_event_gen_test_init)
module_exit(kprobe_event_gen_test_exit)

MODULE_AUTHOR("Tom Zanussi");
MODULE_DESCRIPTION("kprobe event generation test");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/module.h`, `linux/trace_events.h`.
• Detected declarations: `function trace_event_file_is_valid`, `function test_gen_kprobe_cmd`, `function test_gen_kretprobe_cmd`, `function kprobe_event_gen_test_init`, `function kprobe_event_gen_test_exit`, `module init kprobe_event_gen_test_init`.
• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• Implementation status: integration 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.