Re: [Intel-gfx] [PATCH 1/3] drm/i915: Trim error mask to known engines

2018-03-19 Thread Chris Wilson
Quoting Michel Thierry (2018-03-19 16:31:05) > On 19/03/18 06:12, Chris Wilson wrote: > > Quoting Chris Wilson (2018-03-16 21:49:59) > >> For the convenience of userspace passing in an arbitrary reset mask, > >> remove unknown engines from the set of engines that are to be reset. > >> This means

Re: [Intel-gfx] [PATCH 1/3] drm/i915: Trim error mask to known engines

2018-03-19 Thread Chris Wilson
Quoting Michel Thierry (2018-03-19 16:31:05) > On 19/03/18 06:12, Chris Wilson wrote: > > Quoting Chris Wilson (2018-03-16 21:49:59) > >> For the convenience of userspace passing in an arbitrary reset mask, > >> remove unknown engines from the set of engines that are to be reset. > >> This means

Re: [Intel-gfx] [PATCH 1/3] drm/i915: Trim error mask to known engines

2018-03-19 Thread Michel Thierry
On 19/03/18 06:12, Chris Wilson wrote: Quoting Chris Wilson (2018-03-16 21:49:59) For the convenience of userspace passing in an arbitrary reset mask, remove unknown engines from the set of engines that are to be reset. This means that we always follow a per-engine reset with a full-device

Re: [Intel-gfx] [PATCH 1/3] drm/i915: Trim error mask to known engines

2018-03-19 Thread Chris Wilson
Quoting Chris Wilson (2018-03-16 21:49:59) > For the convenience of userspace passing in an arbitrary reset mask, > remove unknown engines from the set of engines that are to be reset. > This means that we always follow a per-engine reset with a full-device > reset when userspace writes -1 into

[Intel-gfx] [PATCH 1/3] drm/i915: Trim error mask to known engines

2018-03-16 Thread Chris Wilson
For the convenience of userspace passing in an arbitrary reset mask, remove unknown engines from the set of engines that are to be reset. This means that we always follow a per-engine reset with a full-device reset when userspace writes -1 into debugfs/i915_wedged. Reported-by: MichaƂ Winiarski