drivers/acpi/numa/hmat.c

File Facts

System

Linux kernel

Corpus path

drivers/acpi/numa/hmat.c

Extension

.c

Size

27382 bytes

Lines

1105

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/bitops.h
• linux/device.h
• linux/init.h
• linux/list.h
• linux/mm.h
• linux/platform_device.h
• linux/list_sort.h
• linux/memregion.h
• linux/memory.h
• linux/mutex.h
• linux/node.h
• linux/sysfs.h
• linux/dax.h
• linux/memory-tiers.h

Detected Declarations

• struct target_cache
• struct memory_target
• struct memory_initiator
• struct memory_locality
• enum locality_types
• function disable_hmat
• function hmat_get_extended_linear_cache_size
• function list_for_each_entry
• function list_for_each_entry
• function acpi_get_genport_coordinates
• function alloc_memory_initiator
• function alloc_memory_target
• function alloc_genport_target
• function hmat_normalize
• function hmat_update_target_access
• function hmat_add_locality
• function hmat_update_target
• function hmat_parse_locality
• function hmat_parse_cache
• function hmat_parse_proximity_domain
• function hmat_parse_subtable
• function srat_parse_mem_affinity
• function srat_parse_genport_affinity
• function hmat_initiator_perf
• function hmat_update_best
• function initiator_cmp
• function initiators_to_nodemask
• function hmat_update_target_attrs
• function list_for_each_entry
• function __hmat_register_target_initiators
• function hmat_update_generic_target
• function hmat_register_target_initiators
• function hmat_register_target_cache
• function hmat_register_target_perf
• function hmat_register_target_devices
• function hmat_hotplug_target
• function hmat_register_target
• function hmat_register_targets
• function hmat_callback
• function hmat_set_default_dram_perf
• function for_each_node_mask
• function hmat_calculate_adistance
• function hmat_free_structures
• function list_for_each_entry_safe
• function list_for_each_entry_safe
• function list_for_each_entry_safe
• function list_for_each_entry_safe
• function hmat_init

Annotated Snippet

subsys_initcall(hmat_init);

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/bitops.h`, `linux/device.h`, `linux/init.h`, `linux/list.h`, `linux/mm.h`, `linux/platform_device.h`, `linux/list_sort.h`.
• Detected declarations: `struct target_cache`, `struct memory_target`, `struct memory_initiator`, `struct memory_locality`, `enum locality_types`, `function disable_hmat`, `function hmat_get_extended_linear_cache_size`, `function list_for_each_entry`, `function list_for_each_entry`, `function acpi_get_genport_coordinates`.
• Atlas domain: Driver Families / drivers/acpi.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.