drivers/dax/cxl.c

File Facts

System

Linux kernel

Corpus path

drivers/dax/cxl.c

Extension

.c

Size

1982 bytes

Lines

76

Domain

Driver Families

Bucket

drivers/dax

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
• linux/dax.h
• ../cxl/cxl.h
• bus.h

Detected Declarations

• function cxl_dax_region_probe
• function cxl_dax_region_driver_register
• function cxl_dax_region_init
• function cxl_dax_region_exit
• module init cxl_dax_region_init

Annotated Snippet

module_init(cxl_dax_region_init);

static void __exit cxl_dax_region_exit(void)
{
	flush_work(&cxl_dax_region_driver_work);
	cxl_driver_unregister(&cxl_dax_region_driver);
}
module_exit(cxl_dax_region_exit);

MODULE_ALIAS_CXL(CXL_DEVICE_DAX_REGION);
MODULE_DESCRIPTION("CXL DAX: direct access to CXL regions");
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Intel Corporation");
MODULE_IMPORT_NS("CXL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/dax.h`, `../cxl/cxl.h`, `bus.h`.
• Detected declarations: `function cxl_dax_region_probe`, `function cxl_dax_region_driver_register`, `function cxl_dax_region_init`, `function cxl_dax_region_exit`, `module init cxl_dax_region_init`.
• Atlas domain: Driver Families / drivers/dax.
• 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.