Re: [PATCH] mutex: Report recursive ww_mutex locking early

2016-05-30 Thread Maarten Lankhorst
Op 30-05-16 om 12:45 schreef Chris Wilson: > On Mon, May 30, 2016 at 12:27:46PM +0200, Peter Zijlstra wrote: >> On Mon, May 30, 2016 at 11:43:31AM +0200, Maarten Lankhorst wrote: >>> Patch not applied, SCHED_RR: >> ww_mutex isn't RT aware at all; its one of the things I still have on a >> todo list

Re: [PATCH] mutex: Report recursive ww_mutex locking early

2016-05-30 Thread Chris Wilson
On Mon, May 30, 2016 at 12:27:46PM +0200, Peter Zijlstra wrote: > On Mon, May 30, 2016 at 11:43:31AM +0200, Maarten Lankhorst wrote: > > Patch not applied, SCHED_RR: > > ww_mutex isn't RT aware at all; its one of the things I still have on a > todo list. Should I look harder at finding time for th

Re: [PATCH] mutex: Report recursive ww_mutex locking early

2016-05-30 Thread Peter Zijlstra
On Mon, May 30, 2016 at 11:43:31AM +0200, Maarten Lankhorst wrote: > Patch not applied, SCHED_RR: ww_mutex isn't RT aware at all; its one of the things I still have on a todo list. Should I look harder at finding time for this?

Re: [PATCH] mutex: Report recursive ww_mutex locking early

2016-05-30 Thread Maarten Lankhorst
Op 30-05-16 om 11:11 schreef Peter Zijlstra: > On Mon, May 30, 2016 at 09:43:53AM +0200, Maarten Lankhorst wrote: >> Op 26-05-16 om 22:08 schreef Chris Wilson: >>> Recursive locking for ww_mutexes was originally conceived as an >>> exception. However, it is heavily used by the DRM atomic modesettin

Re: [PATCH] mutex: Report recursive ww_mutex locking early

2016-05-30 Thread Peter Zijlstra
On Mon, May 30, 2016 at 09:43:53AM +0200, Maarten Lankhorst wrote: > Op 26-05-16 om 22:08 schreef Chris Wilson: > > Recursive locking for ww_mutexes was originally conceived as an > > exception. However, it is heavily used by the DRM atomic modesetting > > code. Currently, the recursive deadlock is

Re: [PATCH] mutex: Report recursive ww_mutex locking early

2016-05-30 Thread Maarten Lankhorst
Op 26-05-16 om 22:08 schreef Chris Wilson: > Recursive locking for ww_mutexes was originally conceived as an > exception. However, it is heavily used by the DRM atomic modesetting > code. Currently, the recursive deadlock is checked after we have queued > up for a busy-spin and as we never release

[PATCH] mutex: Report recursive ww_mutex locking early

2016-05-26 Thread Chris Wilson
Recursive locking for ww_mutexes was originally conceived as an exception. However, it is heavily used by the DRM atomic modesetting code. Currently, the recursive deadlock is checked after we have queued up for a busy-spin and as we never release the lock, we spin until kicked, whereupon the deadl