drm/vmwgfx: Kill unneeded legacy security features

Browse source

At one point, the GPU command verifier and user-space handle manager
couldn't properly protect GPU clients from accessing each other's data.
Instead there was an elaborate mechanism to make sure only the active
master's primary clients could render. The other clients were either
put to sleep or even killed (if the master had exited). VRAM was
evicted on master switch. With the advent of render-node functionality,
we relaxed the VRAM eviction, but the other mechanisms stayed in place.

Now that the GPU command verifier and ttm object manager properly
isolate primary clients from different master realms we can remove the
master switch related code and drop those legacy features.

Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
Reviewed-by: Deepak Rawat <drawat@vmware.com>
Acked-by: Emil Velikov <emil.velikov@collabora.com>

...

This commit is contained in:

Thomas Hellstrom 2019-05-28 08:08:55 +02:00

parent 358d76d9b5

commit 9bbfda544e

5 changed files with 3 additions and 311 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

100

drivers/gpu/drm/vmwgfx/ttm_lock.c

View file

30

drivers/gpu/drm/vmwgfx/ttm_lock.h

View file

162

drivers/gpu/drm/vmwgfx/vmwgfx_drv.c

View file

16

drivers/gpu/drm/vmwgfx/vmwgfx_drv.h

View file

6

drivers/gpu/drm/vmwgfx/vmwgfx_surface.c

View file