[Intel-gfx] ✓ Fi.CI.IGT: success for igt/gem_ctx_thrash: Order writes between contexts

2018-05-12 Thread Patchwork
== Series Details == Series: igt/gem_ctx_thrash: Order writes between contexts URL : https://patchwork.freedesktop.org/series/43090/ State : success == Summary == = CI Bug Log - changes from IGT_4475_full -> IGTPW_1350_full = == Summary - WARNING == Minor unknown changes coming with

[Intel-gfx] ✓ Fi.CI.BAT: success for igt/gem_ctx_thrash: Order writes between contexts

2018-05-12 Thread Patchwork
== Series Details == Series: igt/gem_ctx_thrash: Order writes between contexts URL : https://patchwork.freedesktop.org/series/43090/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4171 -> IGTPW_1350 = == Summary - WARNING == Minor unknown changes coming with IGTPW_1350

[Intel-gfx] [PATCH i-g-t] igt/gem_ctx_thrash: Order writes between contexts

2018-05-12 Thread Chris Wilson
The test wrote to the same dwords from multiple contexts, assuming that the writes would be ordered by its submission. However, as it was using multiple contexts without a write hazard, those timelines are not coupled and the requests may be emitted to hw in any order. So emit a write hazard for

Re: [Intel-gfx] [PATCH] dim: replace pipe commands with single sed

2018-05-12 Thread Daniel Vetter
On Wed, May 09, 2018 at 04:32:53PM -0700, Lucas De Marchi wrote: > Now CC the right mailing list. The way dim sets up the repository you > can't have individual git configs, e.g. to set a different > sendemail.to for dim-tools :( > > Lucas De Marchi > > On Wed, May 9, 2018 at 2:28 PM, Lucas De

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Mark up nested spinlocks

2018-05-12 Thread Patchwork
== Series Details == Series: drm/i915: Mark up nested spinlocks URL : https://patchwork.freedesktop.org/series/43082/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4171_full -> Patchwork_8986_full = == Summary - WARNING == Minor unknown changes coming with

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Mark up nested spinlocks

2018-05-12 Thread Patchwork
== Series Details == Series: drm/i915: Mark up nested spinlocks URL : https://patchwork.freedesktop.org/series/43082/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4171 -> Patchwork_8986 = == Summary - WARNING == Minor unknown changes coming with Patchwork_8986 need to

[Intel-gfx] [PATCH i-g-t] igt/gem_eio: Exercise banning

2018-05-12 Thread Chris Wilson
If we trigger "too many" resets, the context and even the file, will be banend and subsequent execbufs should fail with -EIO. Signed-off-by: Chris Wilson --- tests/gem_eio.c | 49 + 1 file changed, 49 insertions(+) diff

[Intel-gfx] [PATCH] drm/i915: Mark up nested spinlocks

2018-05-12 Thread Chris Wilson
When we process the outstanding requests upon banning a context, we need to acquire both the engine and the client's timeline, nesting the locks. This requires explicit markup as the two timelines are now of the same class, since commit a89d1f921c15 ("drm/i915: Split i915_gem_timeline into