diff options
| author | Sinclair Yeh <syeh@vmware.com> | 2017-11-01 10:47:05 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-11-15 17:13:13 +0100 |
| commit | ba4828af60e227fffb6ccca2e17c64938e7a5d0d (patch) | |
| tree | fac98e7074742bc38391adaa8ba246b929e70f61 /drivers/block | |
| parent | 05b690ccb077eccb6a1aeb610456dbd5ea7f04a1 (diff) | |
| download | linux-stable-ba4828af60e227fffb6ccca2e17c64938e7a5d0d.tar.gz linux-stable-ba4828af60e227fffb6ccca2e17c64938e7a5d0d.tar.bz2 linux-stable-ba4828af60e227fffb6ccca2e17c64938e7a5d0d.zip | |
drm/vmwgfx: Fix Ubuntu 17.10 Wayland black screen issue
commit cef75036c40408ba3bc308bcb00a3d440da713fc upstream.
This is an extension of Commit 7c20d213dd3c ("drm/vmwgfx: Work
around mode set failure in 2D VMs")
With Wayland desktop and atomic mode set, during the mode setting
process there is a moment when two framebuffer sized surfaces
are being pinned. This was not an issue with Xorg.
Since this only happens during a mode change, there should be no
performance impact by increasing allowable mem_size.
Signed-off-by: Sinclair Yeh <syeh@vmware.com>
Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/block')
0 files changed, 0 insertions, 0 deletions