samples/ftrace/sample-trace-array.c

File Facts

System

Linux kernel

Corpus path

samples/ftrace/sample-trace-array.c

Extension

.c

Size

3607 bytes

Lines

144

Domain

Support Tooling And Documentation

Bucket

samples

Inferred role

Support Tooling And Documentation: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/kthread.h
• linux/trace.h
• linux/trace_events.h
• linux/timer.h
• linux/err.h
• linux/jiffies.h
• linux/workqueue.h
• sample-trace-array.h

Detected Declarations

• function trace_work_fn
• function mytimer_handler
• function simple_thread_func
• function simple_thread
• function sample_trace_array_init
• function sample_trace_array_exit
• module init sample_trace_array_init

Annotated Snippet

module_init(sample_trace_array_init);
module_exit(sample_trace_array_exit);

MODULE_AUTHOR("Divya Indi");
MODULE_DESCRIPTION("Sample module for kernel access to Ftrace instances");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kthread.h`, `linux/trace.h`, `linux/trace_events.h`, `linux/timer.h`, `linux/err.h`, `linux/jiffies.h`, `linux/workqueue.h`.
• Detected declarations: `function trace_work_fn`, `function mytimer_handler`, `function simple_thread_func`, `function simple_thread`, `function sample_trace_array_init`, `function sample_trace_array_exit`, `module init sample_trace_array_init`.
• Atlas domain: Support Tooling And Documentation / samples.
• 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.