summaryrefslogtreecommitdiffstats
path: root/drivers/block/ataflop.c
diff options
context:
space:
mode:
authorThomas Hellstrom <thellstrom@vmware.com>2019-05-28 08:08:55 +0200
committerThomas Hellstrom <thellstrom@vmware.com>2019-08-15 08:39:27 +0200
commit9c84aeba67cce6514374f134c9ce2c5f35ac3831 (patch)
treeae9c21b525e9d2ccfc8ad48c465bc8a7ede9233e /drivers/block/ataflop.c
parentdrm/vmwgfx: Use VMW_DEBUG_KMS for vmwgfx mode-setting user errors (diff)
downloadlinux-9c84aeba67cce6514374f134c9ce2c5f35ac3831.tar.xz
linux-9c84aeba67cce6514374f134c9ce2c5f35ac3831.zip
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>
Diffstat (limited to 'drivers/block/ataflop.c')
0 files changed, 0 insertions, 0 deletions