pci/controller/pci-hyperv.c

96  * Size of requestor for VMbus; the value is based on the observation
709 	 * always fails since the vmbus channel has been closed:  in hv_arch_irq_unmask()
2039 	 * remove the ID from the VMbus requestor if the identifier is still  in hv_compose_msi_msg()
2716 			 "PCI VMBus BUS_RELATIONS: ignored\n");  in hv_pci_start_relations_work()
2901 		dev_info(&hdev->device, "PCI VMBus EJECT: ignored\n");  in hv_pci_eject_device()
3087  * @hdev:		VMBus's tracking struct for this root PCI bus.
3096  * asynchronous messaging via VMBus.  Windows 10 increases the
3150 				"PCI VMBus probing: Using version %#x\n",  in hv_pci_protocol_negotiation()
3209  * node (in this case, VMBus) or change it such that it
3210  * understands VMBus.  The pnp layer, however, has been declared
3213  * The workaround, implemented here, is to ask VMBus to allocate
3214  * MMIO space for this bus.  VMBus itself knows which ranges are
3323  * @hdev:	VMBus's tracking struct for this root PCI bus
3413  * @hdev:	VMBus's tracking struct for this root PCI bus
3460  * @hdev:	VMBus's tracking struct for this root PCI bus
3548  * @hdev:	VMBus's tracking struct for this root PCI bus
3627  * hv_pci_probe() - New VMBus channel probe, for a root PCI bus
3628  * @hdev:	VMBus's tracking struct for this root PCI bus
3689 	 * Set the PCI bus parent to be the corresponding VMbus  in hv_pci_probe()
3690 	 * device. Then the VMbus device will be assigned as the  in hv_pci_probe()
3877 		 * 'return'; remove the ID from the VMbus requestor if the  in hv_pci_bus_exit()
3891  * hv_pci_remove() - Remove routine for this VMBus channel
3892  * @hdev:	VMBus's tracking struct for this root PCI bus
3948 	 * vmbus channel, which can be being closed by hv_pci_suspend(), e.g.  in hv_pci_suspend()
3950 	 * new_pcichild_device() writes to the vmbus channel.  in hv_pci_suspend()
3956 	 * hbus->wq and safely closes the vmbus channel.  in hv_pci_suspend()
4076 MODULE_DEVICE_TABLE(vmbus, hv_pci_id_table);