drivers/acpi/acpi_mrrm.c

File Facts

System

Linux kernel

Corpus path

drivers/acpi/acpi_mrrm.c

Extension

.c

Size

4699 bytes

Lines

212

Domain

Driver Families

Bucket

drivers/acpi

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• 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/acpi.h
• linux/init.h
• linux/string.h
• linux/sysfs.h

Detected Declarations

• struct mrrm_mem_range_entry
• function acpi_mrrm_max_mem_region
• function get_node_num
• function for_each_online_node
• function acpi_parse_mrrm
• function add_boot_memory_ranges
• function mrrm_init
• module init mrrm_init

Annotated Snippet

device_initcall(mrrm_init);

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/init.h`, `linux/string.h`, `linux/sysfs.h`.
• Detected declarations: `struct mrrm_mem_range_entry`, `function acpi_mrrm_max_mem_region`, `function get_node_num`, `function for_each_online_node`, `function acpi_parse_mrrm`, `function add_boot_memory_ranges`, `function mrrm_init`, `module init mrrm_init`.
• Atlas domain: Driver Families / drivers/acpi.
• 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.