mm/cma_sysfs.c

File Facts

System

Linux kernel

Corpus path

mm/cma_sysfs.c

Extension

.c

Size

3495 bytes

Lines

152

Domain

Core OS

Bucket

Memory Management

Inferred role

Core OS: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/cma.h
• linux/kernel.h
• linux/slab.h
• cma.h

Detected Declarations

• function Copyright
• function cma_sysfs_account_fail_pages
• function cma_sysfs_account_release_pages
• function alloc_pages_success_show
• function alloc_pages_fail_show
• function release_pages_success_show
• function total_pages_show
• function available_pages_show
• function cma_kobj_release
• function cma_sysfs_init
• module init cma_sysfs_init

Annotated Snippet

subsys_initcall(cma_sysfs_init);

Annotation

• Immediate include surface: `linux/cma.h`, `linux/kernel.h`, `linux/slab.h`, `cma.h`.
• Detected declarations: `function Copyright`, `function cma_sysfs_account_fail_pages`, `function cma_sysfs_account_release_pages`, `function alloc_pages_success_show`, `function alloc_pages_fail_show`, `function release_pages_success_show`, `function total_pages_show`, `function available_pages_show`, `function cma_kobj_release`, `function cma_sysfs_init`.
• Atlas domain: Core OS / Memory Management.
• 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.