samples/trace_events/trace_custom_sched.c

File Facts

System

Linux kernel

Corpus path

samples/trace_events/trace_custom_sched.c

Extension

.c

Size

1442 bytes

Lines

60

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/trace_events.h
• linux/module.h
• linux/sched.h
• trace/events/sched.h
• trace_custom_sched.h

Detected Declarations

• function Copyright
• function trace_sched_init
• function trace_sched_exit
• module init trace_sched_init

Annotated Snippet

module_init(trace_sched_init);
module_exit(trace_sched_exit);

MODULE_AUTHOR("Steven Rostedt");
MODULE_DESCRIPTION("Custom scheduling events");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/trace_events.h`, `linux/module.h`, `linux/sched.h`, `trace/events/sched.h`, `trace_custom_sched.h`.
• Detected declarations: `function Copyright`, `function trace_sched_init`, `function trace_sched_exit`, `module init trace_sched_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.