drm/vmwgfx: Kill unneeded legacy security features
authorThomas Hellstrom <thellstrom@vmware.com>
Tue, 28 May 2019 06:08:55 +0000 (08:08 +0200)
committerThomas Hellstrom <thellstrom@vmware.com>
Thu, 15 Aug 2019 06:39:27 +0000 (08:39 +0200)
commit9c84aeba67cce6514374f134c9ce2c5f35ac3831
treeae9c21b525e9d2ccfc8ad48c465bc8a7ede9233e
parent9bb34e9013fce81c1884d903e776ad4e18887cc3
drm/vmwgfx: Kill unneeded legacy security features

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
isolates 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: Deepak Rawat <drawat@vmware.com>
drivers/gpu/drm/vmwgfx/ttm_lock.c
drivers/gpu/drm/vmwgfx/ttm_lock.h
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c