drivers/dax/pmem.c

File Facts

System

Linux kernel

Corpus path

drivers/dax/pmem.c

Extension

.c

Size

2615 bytes

Lines

100

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/memremap.h
• linux/module.h
• ../nvdimm/pfn.h
• ../nvdimm/nd.h
• bus.h

Detected Declarations

• function dev_name
• function dax_pmem_probe
• function dax_pmem_init
• function dax_pmem_exit
• module init dax_pmem_init

Annotated Snippet

module_init(dax_pmem_init);

static void __exit dax_pmem_exit(void)
{
	driver_unregister(&dax_pmem_driver.drv);
}
module_exit(dax_pmem_exit);

MODULE_DESCRIPTION("PMEM DAX: direct access to persistent memory");
MODULE_LICENSE("GPL v2");
MODULE_AUTHOR("Intel Corporation");
MODULE_ALIAS_ND_DEVICE(ND_DEVICE_DAX_PMEM);

Annotation

• Immediate include surface: `linux/memremap.h`, `linux/module.h`, `../nvdimm/pfn.h`, `../nvdimm/nd.h`, `bus.h`.
• Detected declarations: `function dev_name`, `function dax_pmem_probe`, `function dax_pmem_init`, `function dax_pmem_exit`, `module init dax_pmem_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.