samples/ftrace/ftrace-direct.c
Source file repositories/reference/linux-study-clean/samples/ftrace/ftrace-direct.c
File Facts
- System
- Linux kernel
- Corpus path
samples/ftrace/ftrace-direct.c- Extension
.c- Size
- 5214 bytes
- Lines
- 224
- 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.hlinux/sched.hlinux/ftrace.hasm/asm-offsets.hasm/asm.hasm/ibt.hasm/nospec-branch.hasm/ppc_asm.h
Detected Declarations
function my_direct_funcfunction ftrace_direct_initfunction ftrace_direct_exitmodule init ftrace_direct_init
Annotated Snippet
module_init(ftrace_direct_init);
module_exit(ftrace_direct_exit);
MODULE_AUTHOR("Steven Rostedt");
MODULE_DESCRIPTION("Example use case of using register_ftrace_direct()");
MODULE_LICENSE("GPL");Annotation
- Immediate include surface: `linux/module.h`, `linux/sched.h`, `linux/ftrace.h`, `asm/asm-offsets.h`, `asm/asm.h`, `asm/ibt.h`, `asm/nospec-branch.h`, `asm/ppc_asm.h`.
- Detected declarations: `function my_direct_func`, `function ftrace_direct_init`, `function ftrace_direct_exit`, `module init ftrace_direct_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.