drm/radeon: rework locking ring emission mutex in fence deadlock detection v2
Some callers illegal called fence_wait_next/empty while holding the ring emission mutex. So don't relock the mutex in that cases, and move the actual locking into the fence code. v2: Don't try to unlock the mutex if it isn't locked. Signed-off-by:Christian König <deathsimple@vodafone.de> Signed-off-by:
Dave Airlie <airlied@redhat.com>
Showing
- drivers/gpu/drm/radeon/radeon.h 2 additions, 2 deletionsdrivers/gpu/drm/radeon/radeon.h
- drivers/gpu/drm/radeon/radeon_device.c 4 additions, 1 deletiondrivers/gpu/drm/radeon/radeon_device.c
- drivers/gpu/drm/radeon/radeon_fence.c 29 additions, 14 deletionsdrivers/gpu/drm/radeon/radeon_fence.c
- drivers/gpu/drm/radeon/radeon_pm.c 1 addition, 7 deletionsdrivers/gpu/drm/radeon/radeon_pm.c
- drivers/gpu/drm/radeon/radeon_ring.c 1 addition, 5 deletionsdrivers/gpu/drm/radeon/radeon_ring.c
Loading
Please register or sign in to comment