summaryrefslogtreecommitdiff
path: root/drivers/virtio/virtio_pci_common.c
diff options
context:
space:
mode:
authorJake Oshins <jakeo@microsoft.com>2015-08-05 07:52:36 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2015-08-05 18:41:30 (GMT)
commit7f163a6fd957a85f7f66a129db1ad243a44399ee (patch)
tree5c72e580e6ff9d18a39005a09e906121783d4317 /drivers/virtio/virtio_pci_common.c
parentf368ed6088ae9c1fbe1c897bb5f215ce5e63fa1e (diff)
downloadlinux-7f163a6fd957a85f7f66a129db1ad243a44399ee.tar.xz
drivers:hv: Modify hv_vmbus to search for all MMIO ranges available.
This patch changes the logic in hv_vmbus to record all of the ranges in the VM's firmware (BIOS or UEFI) that offer regions of memory-mapped I/O space for use by paravirtual front-end drivers. The old logic just found one range above 4GB and called it good. This logic will find any ranges above 1MB. It would have been possible with this patch to just use existing resource allocation functions, rather than keep track of the entire set of Hyper-V related MMIO regions in VMBus. This strategy, however, is not sufficient when the resource allocator needs to be aware of the constraints of a Hyper-V virtual machine, which is what happens in the next patch in the series. So this first patch exists to show the first steps in reworking the MMIO allocation paths for Hyper-V front-end drivers. Signed-off-by: Jake Oshins <jakeo@microsoft.com> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/virtio/virtio_pci_common.c')
0 files changed, 0 insertions, 0 deletions