lib/math/test_div64.c

File Facts

System

Linux kernel

Corpus path

lib/math/test_div64.c

Extension

.c

Size

10372 bytes

Lines

331

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.

• Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
• 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/init.h
• linux/ktime.h
• linux/module.h
• linux/printk.h
• linux/time64.h
• linux/types.h
• asm/div64.h

Detected Declarations

• function test_div64_verify
• function test_div64
• function test_div64_init
• function test_div64_exit
• module init test_div64_init

Annotated Snippet

module_init(test_div64_init);
module_exit(test_div64_exit);

MODULE_AUTHOR("Maciej W. Rozycki <macro@orcam.me.uk>");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("64bit/32bit division and modulo test module");

Annotation

• Immediate include surface: `linux/init.h`, `linux/ktime.h`, `linux/module.h`, `linux/printk.h`, `linux/time64.h`, `linux/types.h`, `asm/div64.h`.
• Detected declarations: `function test_div64_verify`, `function test_div64`, `function test_div64_init`, `function test_div64_exit`, `module init test_div64_init`.
• Atlas domain: Kernel Services / lib.
• 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.