Re: [Intel-gfx] [PATCH] drm/locking: add backtrace for locking contended locks without backoff

2021-10-01 Thread Jani Nikula
On Thu, 30 Sep 2021, Daniel Vetter wrote: > On Wed, Sep 29, 2021 at 01:32:41AM +0300, Jani Nikula wrote: >> If drm_modeset_lock() returns -EDEADLK, the caller is supposed to drop >> all currently held locks using drm_modeset_backoff(). Failing to do so >> will result in warnings and backtraces on

Re: [Intel-gfx] [PATCH] drm/locking: add backtrace for locking contended locks without backoff

2021-09-30 Thread Daniel Vetter
On Wed, Sep 29, 2021 at 01:32:41AM +0300, Jani Nikula wrote: > If drm_modeset_lock() returns -EDEADLK, the caller is supposed to drop > all currently held locks using drm_modeset_backoff(). Failing to do so > will result in warnings and backtraces on the paths trying to lock a > contended lock. Add

[Intel-gfx] [PATCH] drm/locking: add backtrace for locking contended locks without backoff

2021-09-28 Thread Jani Nikula
If drm_modeset_lock() returns -EDEADLK, the caller is supposed to drop all currently held locks using drm_modeset_backoff(). Failing to do so will result in warnings and backtraces on the paths trying to lock a contended lock. Add support for optionally printing the backtrace on the path that hit t