diff options
| author |   Vitaly Kuznetsov <vkuznets@redhat.com> | 2022-08-27 15:03:44 +0200 |
|---|---|---|
| committer |   Wei Liu <wei.liu@kernel.org> | 2022-09-05 17:02:15 +0000 |
| commit | 2a8a8afba0c3053d0ea8686182f6b2104293037e (patch) | |
| tree | ac9ebdf010e5695bf87197264517b268e0f17fc9 /tools | |
| parent | PCI: Move PCI_VENDOR_ID_MICROSOFT/PCI_DEVICE_ID_HYPERV_VIDEO definitions to pci_ids.h (diff) | |
| download | linux-dev-2a8a8afba0c3053d0ea8686182f6b2104293037e.tar.xz linux-dev-2a8a8afba0c3053d0ea8686182f6b2104293037e.zip | |
Drivers: hv: Always reserve framebuffer region for Gen1 VMs
vmbus_reserve_fb() tries reserving framebuffer region iff
'screen_info.lfb_base' is set. Gen2 VMs seem to have it set by EFI
and/or by the kernel EFI FB driver (or, in some edge cases like kexec,
the address where the buffer was moved, see
https://lore.kernel.org/all/20201014092429.1415040-1-kasong@redhat.com/)
but on Gen1 VM it depends on bootloader behavior. With grub, it depends
on 'gfxpayload=' setting but in some cases it is observed to be zero.
That being said, relying on 'screen_info.lfb_base' to reserve
framebuffer region is risky. For Gen1 VMs, it should always be
possible to get the address from the dedicated PCI device instead.
Check for legacy PCI video device presence and reserve the whole
region for framebuffer on Gen1 VMs.
Reviewed-by: Michael Kelley <mikelley@microsoft.com>
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Link: https://lore.kernel.org/r/20220827130345.1320254-3-vkuznets@redhat.com
Signed-off-by: Wei Liu <wei.liu@kernel.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions