drivers/vfio/platform/vfio_platform_private.h

File Facts

System

Linux kernel

Corpus path

drivers/vfio/platform/vfio_platform_private.h

Extension

.h

Size

3938 bytes

Lines

133

Domain

Driver Families

Bucket

drivers/vfio

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/types.h
• linux/interrupt.h
• linux/vfio.h

Detected Declarations

• struct vfio_platform_irq
• struct vfio_platform_region
• struct vfio_platform_device
• struct vfio_platform_reset_node

Annotated Snippet

module_init(reset ## _module_init);				\
module_exit(reset ## _module_exit)

#endif /* VFIO_PLATFORM_PRIVATE_H */

Annotation

• Immediate include surface: `linux/types.h`, `linux/interrupt.h`, `linux/vfio.h`.
• Detected declarations: `struct vfio_platform_irq`, `struct vfio_platform_region`, `struct vfio_platform_device`, `struct vfio_platform_reset_node`.
• Atlas domain: Driver Families / drivers/vfio.
• 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.