]> git.baikalelectronics.ru Git - kernel.git/commit
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>
Tue, 18 Jun 2019 13:22:48 +0000 (15:22 +0200)
commite069efd0d461e33c816954436a3f0ef190f00b95
treebe01fecb1e0e96c2729a7a19e38b9b9dce1c7b94
parent936d047e7d7ba8ddb7bf64147d80efb105e44f35
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
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>
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