drivers/cxl/core/region_dax.c

File Facts

System

Linux kernel

Corpus path

drivers/cxl/core/region_dax.c

Extension

.c

Size

2520 bytes

Lines

107

Domain

Driver Families

Bucket

drivers/cxl

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/device.h
• linux/slab.h
• cxlmem.h
• cxl.h
• core.h

Detected Declarations

• function Copyright
• function is_cxl_dax_region
• function cxlr_dax_unregister
• function devm_cxl_add_dax_region

Annotated Snippet

rc = device_add(dev);
	if (rc)
		return rc;

	dev_dbg(&cxlr->dev, "%s: register %s\n", dev_name(dev->parent),
		dev_name(dev));

	return devm_add_action_or_reset(&cxlr->dev, cxlr_dax_unregister,
					no_free_ptr(cxlr_dax));
}

Annotation

• Immediate include surface: `linux/device.h`, `linux/slab.h`, `cxlmem.h`, `cxl.h`, `core.h`.
• Detected declarations: `function Copyright`, `function is_cxl_dax_region`, `function cxlr_dax_unregister`, `function devm_cxl_add_dax_region`.
• Atlas domain: Driver Families / drivers/cxl.
• 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.