drivers/ras/amd/atl/core.c

File Facts

System

Linux kernel

Corpus path

drivers/ras/amd/atl/core.c

Extension

.c

Size

5267 bytes

Lines

233

Domain

Driver Families

Bucket

drivers/ras

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• asm/cpu_device_id.h
• internal.h

Detected Declarations

• function addr_over_limit
• function legacy_hole_en
• function add_legacy_hole
• function remove_legacy_hole
• function get_base_addr
• function add_base_and_hole
• function remove_base_and_hole
• function late_hole_remove
• function norm_to_sys_addr
• function check_for_legacy_df_access
• function amd_atl_init
• function amd_atl_exit
• module init amd_atl_init

Annotated Snippet

module_init(amd_atl_init);
module_exit(amd_atl_exit);

MODULE_DESCRIPTION("AMD Address Translation Library");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `asm/cpu_device_id.h`, `internal.h`.
• Detected declarations: `function addr_over_limit`, `function legacy_hole_en`, `function add_legacy_hole`, `function remove_legacy_hole`, `function get_base_addr`, `function add_base_and_hole`, `function remove_base_and_hole`, `function late_hole_remove`, `function norm_to_sys_addr`, `function check_for_legacy_df_access`.
• Atlas domain: Driver Families / drivers/ras.
• 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.