| commit | 6ced0bba70ff557792b781ad35366de03bcd105b | |
| author | Alex Williamson <alex.williamson@redhat.com> | |
| Thu, 26 May 2016 15:43:22 +0000 (26 09:43 -0600) | ||
| committer | Alex Williamson <alex.williamson@redhat.com> | |
| Thu, 26 May 2016 17:12:03 +0000 (26 11:12 -0600) | ||
| tree | ec36f82ca2405383597b4b4db1f1c15c7ba6d9de | treesnapshot (tar.gz zip) |
| parent | c4c45e943e519f5ac220f7af1afb2a0025d03c54 | commitdiff |
vfio/pci: Add a separate option for IGD OpRegion support
The IGD OpRegion is enabled automatically when running in legacy mode,
but it can sometimes be useful in universal passthrough mode as well.
Without an OpRegion, output spigots don't work, and even though Intel
doesn't officially support physical outputs in UPT mode, it's a
useful feature. Note that if an OpRegion is enabled but a monitor is
not connected, some graphics features will be disabled in the guest
versus a headless system without an OpRegion, where they would work.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
Tested-by: Gerd Hoffmann <kraxel@redhat.com>
The IGD OpRegion is enabled automatically when running in legacy mode,
but it can sometimes be useful in universal passthrough mode as well.
Without an OpRegion, output spigots don't work, and even though Intel
doesn't officially support physical outputs in UPT mode, it's a
useful feature. Note that if an OpRegion is enabled but a monitor is
not connected, some graphics features will be disabled in the guest
versus a headless system without an OpRegion, where they would work.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
Tested-by: Gerd Hoffmann <kraxel@redhat.com>
| hw/vfio/pci-quirks.c | diffblobblamehistory | |
| hw/vfio/pci.c | diffblobblamehistory | |
| hw/vfio/pci.h | diffblobblamehistory |