drivers/xen/platform-pci.c

File Facts

System

Linux kernel

Corpus path

drivers/xen/platform-pci.c

Extension

.c

Size

4369 bytes

Lines

196

Domain

Driver Families

Bucket

drivers/xen

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/interrupt.h
• linux/io.h
• linux/init.h
• linux/pci.h
• xen/platform_pci.h
• xen/grant_table.h
• xen/xenbus.h
• xen/events.h
• xen/hvm.h
• xen/xen-ops.h

Detected Declarations

• function alloc_xen_mmio
• function get_callback_via
• function do_hvm_evtchn_intr
• function xen_allocate_irq
• function platform_pci_resume
• function platform_pci_probe

Annotated Snippet

static struct pci_driver platform_driver = {
	.name =           DRV_NAME,
	.probe =          platform_pci_probe,
	.id_table =       platform_pci_tbl,
	.driver = {
		.pm =     &platform_pm_ops,
	},
};

builtin_pci_driver(platform_driver);

Annotation

• Immediate include surface: `linux/interrupt.h`, `linux/io.h`, `linux/init.h`, `linux/pci.h`, `xen/platform_pci.h`, `xen/grant_table.h`, `xen/xenbus.h`, `xen/events.h`.
• Detected declarations: `function alloc_xen_mmio`, `function get_callback_via`, `function do_hvm_evtchn_intr`, `function xen_allocate_irq`, `function platform_pci_resume`, `function platform_pci_probe`.
• Atlas domain: Driver Families / drivers/xen.
• Implementation status: pattern implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.