Re: [Intel-gfx] [PATCH] drm: Don't block the kworker waiting for mode_config.lock in output_poll()

2016-12-06 Thread Daniel Vetter
On Tue, Dec 06, 2016 at 11:55:14AM +, Eric Engestrom wrote: > On Tuesday, 2016-12-06 11:37:15 +, Chris Wilson wrote: > > If we cannot acquire the mode_config.lock immediately, just back off and > > s/mode_config.lock/mode_config.mutex lock/ ? Fixed > > > queue a new attempt after the

Re: [Intel-gfx] [PATCH] drm: Don't block the kworker waiting for mode_config.lock in output_poll()

2016-12-06 Thread Eric Engestrom
On Tuesday, 2016-12-06 11:37:15 +, Chris Wilson wrote: > If we cannot acquire the mode_config.lock immediately, just back off and s/mode_config.lock/mode_config.mutex lock/ ? > queue a new attempt after the poll interval. This is mostly to stop the > hung task spam when the system is

[Intel-gfx] [PATCH] drm: Don't block the kworker waiting for mode_config.lock in output_poll()

2016-12-06 Thread Chris Wilson
If we cannot acquire the mode_config.lock immediately, just back off and queue a new attempt after the poll interval. This is mostly to stop the hung task spam when the system is deadlocked, but it will also lessen the load (in such extreme cases). Signed-off-by: Chris Wilson