drivers/pci/controller/pci-hyperv.c

File Facts

System

Linux kernel

Corpus path

drivers/pci/controller/pci-hyperv.c

Extension

.c

Size

118847 bytes

Lines

4195

Domain

Representative Device Path

Bucket

PCIe NVMe Storage Path

Inferred role

Representative Device Path: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.

• Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/kernel.h
• linux/module.h
• linux/pci.h
• linux/pci-ecam.h
• linux/delay.h
• linux/semaphore.h
• linux/irq.h
• linux/irqchip/irq-msi-lib.h
• linux/msi.h
• linux/hyperv.h
• linux/refcount.h
• linux/irqdomain.h
• linux/acpi.h
• linux/sizes.h
• linux/of_irq.h
• asm/mshyperv.h

Detected Declarations

• struct pci_function_description
• struct pci_function_description2
• struct hv_msi_desc
• struct hv_msi_desc2
• struct hv_msi_desc3
• struct tran_int_desc
• struct pci_message
• struct pci_child_message
• struct pci_incoming_message
• struct pci_response
• struct pci_packet
• struct pci_version_request
• struct pci_bus_d0_entry
• struct pci_bus_relations
• struct pci_bus_relations2
• struct pci_q_res_req_response
• struct pci_set_power
• struct pci_set_power_response
• struct pci_resources_assigned
• struct pci_resources_assigned2
• struct pci_create_interrupt
• struct pci_create_int_response
• struct pci_create_interrupt2
• struct pci_create_interrupt3
• struct pci_delete_interrupt
• struct pci_read_block
• struct pci_read_block_response
• struct pci_write_block
• struct pci_dev_inval_block
• struct pci_dev_incoming
• struct pci_eject_response
• struct hv_pcibus_device
• struct hv_dr_work
• struct hv_pcidev_description
• struct hv_dr_state
• struct hv_pci_dev
• struct hv_pci_compl
• struct hv_pci_chip_data
• struct hv_read_config_compl
• struct compose_comp_ctxt
• struct q_res_req_compl
• enum pci_protocol_version_t
• enum pci_message_type
• enum pci_device_description_flags
• enum hv_pcibus_state
• function hv_pci_irqchip_init
• function hv_msi_get_int_vector
• function hv_irq_retarget_interrupt

Annotated Snippet

module_init(init_hv_pci_drv);
module_exit(exit_hv_pci_drv);

MODULE_DESCRIPTION("Hyper-V PCI");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `linux/pci-ecam.h`, `linux/delay.h`, `linux/semaphore.h`, `linux/irq.h`, `linux/irqchip/irq-msi-lib.h`.
• Detected declarations: `struct pci_function_description`, `struct pci_function_description2`, `struct hv_msi_desc`, `struct hv_msi_desc2`, `struct hv_msi_desc3`, `struct tran_int_desc`, `struct pci_message`, `struct pci_child_message`, `struct pci_incoming_message`, `struct pci_response`.
• Atlas domain: Representative Device Path / PCIe NVMe Storage Path.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.