samples/hw_breakpoint/data_breakpoint.c

File Facts

System

Linux kernel

Corpus path

samples/hw_breakpoint/data_breakpoint.c

Extension

.c

Size

2343 bytes

Lines

85

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/kernel.h
• linux/init.h
• linux/kallsyms.h
• linux/perf_event.h
• linux/hw_breakpoint.h

Detected Declarations

• function sample_hbp_handler
• function hw_break_module_init
• function hw_break_module_exit
• module init hw_break_module_init

Annotated Snippet

module_init(hw_break_module_init);
module_exit(hw_break_module_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("K.Prasad");
MODULE_DESCRIPTION("ksym breakpoint");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/init.h`, `linux/kallsyms.h`, `linux/perf_event.h`, `linux/hw_breakpoint.h`.
• Detected declarations: `function sample_hbp_handler`, `function hw_break_module_init`, `function hw_break_module_exit`, `module init hw_break_module_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.