Lines Matching full:vmbus
98 * Size of requestor for VMbus; the value is based on the observation
699 * always fails since the vmbus channel has been closed: in hv_irq_retarget_interrupt()
971 WARN_ONCE(1, "Invalid firmware configuration for VMBus interrupts\n"); in hv_pci_irqchip_init()
2094 * remove the ID from the VMbus requestor if the identifier is still in hv_compose_msi_msg()
2830 "PCI VMBus BUS_RELATIONS: ignored\n"); in hv_pci_start_relations_work()
3013 dev_info(&hdev->device, "PCI VMBus EJECT: ignored\n"); in hv_pci_eject_device()
3199 * @hdev: VMBus's tracking struct for this root PCI bus.
3208 * asynchronous messaging via VMBus. Windows 10 increases the
3262 "PCI VMBus probing: Using version %#x\n", in hv_pci_protocol_negotiation()
3321 * node (in this case, VMBus) or change it such that it
3322 * understands VMBus. The pnp layer, however, has been declared
3325 * The workaround, implemented here, is to ask VMBus to allocate
3326 * MMIO space for this bus. VMBus itself knows which ranges are
3435 * @hdev: VMBus's tracking struct for this root PCI bus
3525 * @hdev: VMBus's tracking struct for this root PCI bus
3572 * @hdev: VMBus's tracking struct for this root PCI bus
3660 * @hdev: VMBus's tracking struct for this root PCI bus
3697 * hv_pci_probe() - New VMBus channel probe, for a root PCI bus
3698 * @hdev: VMBus's tracking struct for this root PCI bus
3762 * Set the PCI bus parent to be the corresponding VMbus in hv_pci_probe()
3763 * device. Then the VMbus device will be assigned as the in hv_pci_probe()
3951 * 'return'; remove the ID from the VMbus requestor if the in hv_pci_bus_exit()
3965 * hv_pci_remove() - Remove routine for this VMBus channel
3966 * @hdev: VMBus's tracking struct for this root PCI bus
4020 * vmbus channel, which can be being closed by hv_pci_suspend(), e.g. in hv_pci_suspend()
4022 * new_pcichild_device() writes to the vmbus channel. in hv_pci_suspend()
4028 * hbus->wq and safely closes the vmbus channel. in hv_pci_suspend()
4142 MODULE_DEVICE_TABLE(vmbus, hv_pci_id_table);