aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/dma-buf
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2020-12-11 17:29:42 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2021-01-18 14:15:20 +0100
commit72fec10c17d95bcb99371f5b29f6947e67d7493b (patch)
treeb8d5668ae2e0c6d2046f5aa7b0650c59104e7b21 /drivers/dma-buf
parentdrm/vmwgfx: Always evict vram _before_ disabling it (diff)
downloadlinux-dev-72fec10c17d95bcb99371f5b29f6947e67d7493b.tar.xz
linux-dev-72fec10c17d95bcb99371f5b29f6947e67d7493b.zip
drm/ttm: WARN_ON non-empty lru when disabling a resource manager
ttm_resource_manager->use_type is only used for runtime changes by vmwgfx. I think ideally we'd push this functionality into drivers - ttm itself does not provide any locking to guarantee this is safe, so the only way this can work at runtime is if the driver does provide additional guarantees. vwmgfx does that through the vmw_private->reservation_sem. Therefore supporting this feature in shared code feels a bit misplaced. As a first step add a WARN_ON to make sure the resource manager is empty. This is just to make sure I actually understand correctly what vmwgfx is doing, and to make sure an eventual subsequent refactor doesn't break anything. This check should also be useful for other drivers, to make sure they haven't leaked anything. Reviewed-by: Roland Scheidegger <sroland@vmware.com> Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Cc: Christian Koenig <christian.koenig@amd.com> Cc: Huang Rui <ray.huang@amd.com> Link: https://patchwork.freedesktop.org/patch/msgid/20201211162942.3399050-3-daniel.vetter@ffwll.ch
Diffstat (limited to 'drivers/dma-buf')
0 files changed, 0 insertions, 0 deletions