hyperv vmbus_pcib: Use pci_domain_*_bus for PCI_RES_BUS resources

[jhb]

Summary

Specifically for bus_activate/adjust/deactivate_bus methods.

[schakrabarti_microsoft.com]

sys/dev/hyperv/pcib/vmbus_pcib.c

2011–2012

Please check the indentation here.

[jhb]

sys/dev/hyperv/pcib/vmbus_pcib.c

2011–2012

The raw version looks fine. I think the previous version was not fully consistent. Here is the patched method table:

	/* Bus interface */
	DEVMETHOD(bus_read_ivar,		vmbus_pcib_read_ivar),
	DEVMETHOD(bus_write_ivar,		vmbus_pcib_write_ivar),
	DEVMETHOD(bus_alloc_resource,		vmbus_pcib_alloc_resource),
	DEVMETHOD(bus_adjust_resource,		vmbus_pcib_adjust_resource),
	DEVMETHOD(bus_release_resource,		vmbus_pcib_release_resource),
	DEVMETHOD(bus_activate_resource,   	vmbus_pcib_activate_resource),
	DEVMETHOD(bus_deactivate_resource, 	vmbus_pcib_deactivate_resource),
	DEVMETHOD(bus_setup_intr,	   bus_generic_setup_intr),
	DEVMETHOD(bus_teardown_intr,	   bus_generic_teardown_intr),
	DEVMETHOD(bus_get_cpus,			vmbus_pcib_get_cpus),

[schakrabarti_microsoft.com]

Code looks fine to me, but has the new functions been tested on Azure ? As in local Hyper-V we mostly dont use pci passthrough.

[jhb]

In D43431#993619, @schakrabarti_microsoft.com wrote:

Code looks fine to me, but has the new functions been tested on Azure ? As in local Hyper-V we mostly dont use pci passthrough.

I do not have a means to test it, no. It is part of a larger API sweep/cleanup series.