drm/vmwgfx: Don't cache framebuffer maps

Browse source

commit 98648ae6ef upstream.

Buffer objects need to be either pinned or reserved while a map is active,
that's not the case here, so avoid caching the framebuffer map.
This will cause increasing mapping activity mainly when we don't do
page flipping.

This fixes occasional garbage filled screens when the framebuffer has been
evicted after the map.

Since in-kernel mapping of whole buffer objects is error-prone on 32-bit
architectures and also quite inefficient, we will revisit this later.

Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Sinclair Yeh <syeh@vmware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

...

This commit is contained in:

Thomas Hellstrom 2018-01-09 15:33:42 +01:00 • committed by Greg Kroah-Hartman

parent 02453a0f8f

commit 2f6ff75e48

3 changed files with 13 additions and 36 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

6

drivers/gpu/drm/vmwgfx/vmwgfx_kms.c

View file

2

drivers/gpu/drm/vmwgfx/vmwgfx_kms.h

View file

41

drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c

View file