diff options
author | Thomas Hellstrom <thellstrom@vmware.com> | 2019-05-28 08:08:55 +0200 |
---|---|---|
committer | Thomas Hellstrom <thellstrom@vmware.com> | 2019-06-18 15:22:48 +0200 |
commit | 9bbfda544ed79e8e9abde27bfe2c85428d582e7b (patch) | |
tree | be01fecb1e0e96c2729a7a19e38b9b9dce1c7b94 /include | |
parent | 358d76d9b577aefba973aea9a50dbfcbaac25d6e (diff) | |
download | linux-9bbfda544ed79e8e9abde27bfe2c85428d582e7b.tar.bz2 |
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>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions