[PATCH 3/3] drm/vmwgfx: Delay pinning fbdev framebuffer until after mode set

2016-07-05 Thread Sinclair Yeh
Argh, you're right. I'll send out a patch. Thanks for catching this! Sinclair On Mon, Jul 04, 2016 at 04:51:52PM +0100, Emil Velikov wrote: > Hi Sinclair, > > On 1 July 2016 at 19:24, wrote: > > From: Sinclair Yeh > > > > For the Screen Object display unit, we need to reserve a > > guest-in

[PATCH 3/3] drm/vmwgfx: Delay pinning fbdev framebuffer until after mode set

2016-07-04 Thread Emil Velikov
Hi Sinclair, On 1 July 2016 at 19:24, wrote: > From: Sinclair Yeh > > For the Screen Object display unit, we need to reserve a > guest-invisible region equal to the size of the framebuffer for > the host. This region can only be reserved in VRAM, whereas > the guest-visible framebuffer can be

[PATCH 3/3] drm/vmwgfx: Delay pinning fbdev framebuffer until after mode set

2016-07-01 Thread s...@vmware.com
From: Sinclair Yeh For the Screen Object display unit, we need to reserve a guest-invisible region equal to the size of the framebuffer for the host. This region can only be reserved in VRAM, whereas the guest-visible framebuffer can be reserved in either VRAM or GMR. As such priority should be