* [PATCH] drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR
@ 2019-01-02 16:35 Chris Wilson
2019-01-02 17:10 ` ✓ Fi.CI.BAT: success for " Patchwork
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Chris Wilson @ 2019-01-02 16:35 UTC (permalink / raw)
To: intel-gfx
On Baytail, notably, we can still detect missed interrupt syndrome
(where we never spot a completed request). In this case, it can be
alleviated by always keeping the interrupt unmasked, implying that the
interrupt is being lost in the window after modifying the IMR. (This is
the reason we still have the posting reads on enable_irq, if we remove
them we miss interrupts!) Having narrowed the issue down to the IMR,
rather than keeping it always enabled, applying the usual posting
read/flush of the RING_IMR before unmasking the GT IMR also seems to
prevent the missed interrupt. So be it.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
drivers/gpu/drm/i915/intel_ringbuffer.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
index 8967dcb5f58f..3d5d6b908148 100644
--- a/drivers/gpu/drm/i915/intel_ringbuffer.c
+++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
@@ -974,6 +974,10 @@ gen6_irq_enable(struct intel_engine_cs *engine)
I915_WRITE_IMR(engine,
~(engine->irq_enable_mask |
engine->irq_keep_mask));
+
+ /* Flush/delay to ensure the RING_IMR is active before the GT IMR */
+ POSTING_READ_FW(RING_IMR(engine->mmio_base));
+
gen5_enable_gt_irq(dev_priv, engine->irq_enable_mask);
}
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 5+ messages in thread* ✓ Fi.CI.BAT: success for drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR
2019-01-02 16:35 [PATCH] drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR Chris Wilson
@ 2019-01-02 17:10 ` Patchwork
2019-01-02 18:24 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-03 10:25 ` [PATCH] " Mika Kuoppala
2 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2019-01-02 17:10 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR
URL : https://patchwork.freedesktop.org/series/54655/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5358 -> Patchwork_11176
====================================================
Summary
-------
**WARNING**
Minor unknown changes coming with Patchwork_11176 need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_11176, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://patchwork.freedesktop.org/api/1.0/series/54655/revisions/1/mbox/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_11176:
### IGT changes ###
#### Warnings ####
* igt@kms_flip@basic-flip-vs-dpms:
- fi-skl-6770hq: SKIP -> PASS +36
Known issues
------------
Here are the changes found in Patchwork_11176 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_pipe_crc_basic@read-crc-pipe-a:
- fi-byt-clapper: PASS -> FAIL [fdo#107362]
#### Possible fixes ####
* igt@i915_selftest@live_evict:
- fi-bsw-kefka: DMESG-WARN [fdo#107709] -> PASS
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence:
- fi-byt-clapper: FAIL [fdo#103191] / [fdo#107362] -> PASS
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-blb-e6850: INCOMPLETE [fdo#107718] -> PASS
[fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
[fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
[fdo#107709]: https://bugs.freedesktop.org/show_bug.cgi?id=107709
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
Participating hosts (50 -> 44)
------------------------------
Additional (2): fi-gdg-551 fi-snb-2600
Missing (8): fi-kbl-soraka fi-hsw-4770r fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-icl-y
Build changes
-------------
* Linux: CI_DRM_5358 -> Patchwork_11176
CI_DRM_5358: c6a0276a5007c01c64a8a80552b78c115e8a0dae @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4755: 0ba18cf75cafb51d1e72557528de4a1be640a85c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_11176: b6858ef7ab8fda7cd93db420e139507d4ca16a46 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
b6858ef7ab8f drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_11176/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread* ✓ Fi.CI.IGT: success for drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR
2019-01-02 16:35 [PATCH] drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR Chris Wilson
2019-01-02 17:10 ` ✓ Fi.CI.BAT: success for " Patchwork
@ 2019-01-02 18:24 ` Patchwork
2019-01-03 10:25 ` [PATCH] " Mika Kuoppala
2 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2019-01-02 18:24 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR
URL : https://patchwork.freedesktop.org/series/54655/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5358_full -> Patchwork_11176_full
====================================================
Summary
-------
**WARNING**
Minor unknown changes coming with Patchwork_11176_full need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_11176_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_11176_full:
### IGT changes ###
#### Warnings ####
* igt@pm_rc6_residency@rc6-accuracy:
- shard-kbl: SKIP -> PASS
* igt@tools_test@tools_test:
- shard-glk: SKIP -> PASS
Known issues
------------
Here are the changes found in Patchwork_11176_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_busy@extended-modeset-hang-newfb-render-c:
- shard-hsw: PASS -> DMESG-WARN [fdo#107956]
* igt@kms_cursor_crc@cursor-128x128-onscreen:
- shard-apl: PASS -> FAIL [fdo#103232] +1
* igt@kms_cursor_crc@cursor-256x85-offscreen:
- shard-glk: PASS -> INCOMPLETE [fdo#103359] / [k.org#198133]
* igt@kms_draw_crc@draw-method-rgb565-render-untiled:
- shard-iclb: PASS -> WARN [fdo#108336] +2
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render:
- shard-iclb: PASS -> DMESG-FAIL [fdo#107720] / [fdo#107724] +1
* igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-gtt:
- shard-iclb: PASS -> DMESG-FAIL [fdo#107724] +14
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-gtt:
- shard-iclb: PASS -> FAIL [fdo#103167] +2
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen:
- shard-iclb: PASS -> DMESG-WARN [fdo#107724] / [fdo#108336] +23
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-iclb: PASS -> INCOMPLETE [fdo#107713]
* igt@kms_plane@pixel-format-pipe-a-planes:
- shard-skl: NOTRUN -> DMESG-WARN [fdo#106885]
* igt@kms_plane@plane-position-covered-pipe-b-planes:
- shard-iclb: PASS -> FAIL [fdo#103166] +1
* igt@kms_plane@plane-position-covered-pipe-c-planes:
- shard-apl: PASS -> FAIL [fdo#103166]
- shard-glk: PASS -> FAIL [fdo#103166]
* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- shard-glk: PASS -> FAIL [fdo#108145]
* igt@kms_plane_alpha_blend@pipe-a-alpha-transparant-fb:
- shard-skl: NOTRUN -> FAIL [fdo#108145] +1
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: PASS -> FAIL [fdo#107815]
* igt@kms_sysfs_edid_timing:
- shard-iclb: PASS -> FAIL [fdo#100047]
* igt@kms_vblank@pipe-a-ts-continuation-idle:
- shard-iclb: PASS -> DMESG-WARN [fdo#107724] +36
* igt@pm_rpm@basic-rte:
- shard-skl: PASS -> INCOMPLETE [fdo#107807]
#### Possible fixes ####
* igt@gem_ctx_isolation@rcs0-s3:
- shard-skl: INCOMPLETE [fdo#104108] / [fdo#107773] -> PASS
* igt@gem_ppgtt@blt-vs-render-ctxn:
- shard-skl: TIMEOUT [fdo#108039] -> PASS
* igt@kms_busy@extended-modeset-hang-newfb-render-a:
- shard-hsw: DMESG-WARN [fdo#107956] -> PASS
* igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-c:
- shard-kbl: DMESG-WARN [fdo#107956] -> PASS
* igt@kms_cursor_crc@cursor-256x256-onscreen:
- shard-apl: FAIL [fdo#103232] -> PASS
* igt@kms_cursor_legacy@flip-vs-cursor-atomic:
- shard-skl: FAIL [fdo#102670] -> PASS
* igt@kms_draw_crc@draw-method-xrgb8888-render-xtiled:
- shard-skl: FAIL [fdo#107791] -> PASS
* igt@kms_draw_crc@draw-method-xrgb8888-render-ytiled:
- shard-skl: FAIL [fdo#103232] -> PASS
* igt@kms_flip_tiling@flip-x-tiled:
- shard-skl: FAIL [fdo#108145] -> PASS
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move:
- shard-apl: FAIL [fdo#103167] -> PASS
* igt@kms_frontbuffer_tracking@fbcpsr-indfb-scaledprimary:
- shard-skl: FAIL [fdo#105682] -> PASS
* igt@kms_frontbuffer_tracking@fbcpsr-stridechange:
- shard-iclb: FAIL [fdo#105683] -> PASS
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-mmap-cpu:
- shard-skl: FAIL [fdo#103167] -> PASS
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-blt:
- shard-iclb: FAIL [fdo#103167] -> PASS +9
* igt@kms_frontbuffer_tracking@psr-suspend:
- shard-iclb: INCOMPLETE [fdo#106978] / [fdo#107713] -> PASS
* igt@kms_plane@plane-position-covered-pipe-b-planes:
- shard-glk: FAIL [fdo#103166] -> PASS
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max:
- shard-glk: FAIL [fdo#108145] -> PASS
* igt@kms_plane_multiple@atomic-pipe-a-tiling-x:
- shard-iclb: FAIL [fdo#103166] -> PASS
* igt@kms_rotation_crc@multiplane-rotation-cropping-top:
- shard-glk: DMESG-FAIL [fdo#105763] / [fdo#106538] -> PASS
* igt@kms_rotation_crc@primary-rotation-90:
- shard-skl: FAIL [fdo#103925] / [fdo#107815] -> PASS
* igt@kms_vblank@pipe-a-query-forked-busy-hang:
- shard-apl: DMESG-WARN [fdo#103558] / [fdo#105602] -> PASS +31
* igt@pm_rpm@modeset-non-lpsp-stress-no-wait:
- shard-skl: INCOMPLETE [fdo#107807] -> SKIP
#### Warnings ####
* igt@kms_color@pipe-b-legacy-gamma:
- shard-apl: DMESG-WARN [fdo#103558] / [fdo#105602] -> FAIL [fdo#104782]
* igt@kms_cursor_crc@cursor-64x64-random:
- shard-iclb: FAIL [fdo#103232] -> DMESG-WARN [fdo#107724] / [fdo#108336] +1
- shard-apl: DMESG-WARN [fdo#103558] / [fdo#105602] -> FAIL [fdo#103232]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render:
- shard-snb: DMESG-FAIL [fdo#107469] -> INCOMPLETE [fdo#105411] / [fdo#107469]
* igt@kms_hdmi_inject@inject-audio:
- shard-iclb: FAIL [fdo#102370] -> DMESG-FAIL [fdo#107724]
* igt@kms_plane_alpha_blend@pipe-c-alpha-opaque-fb:
- shard-apl: DMESG-FAIL [fdo#103558] / [fdo#105602] / [fdo#108145] -> FAIL [fdo#108145] +1
[fdo#100047]: https://bugs.freedesktop.org/show_bug.cgi?id=100047
[fdo#102370]: https://bugs.freedesktop.org/show_bug.cgi?id=102370
[fdo#102670]: https://bugs.freedesktop.org/show_bug.cgi?id=102670
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232
[fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359
[fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558
[fdo#103925]: https://bugs.freedesktop.org/show_bug.cgi?id=103925
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#104782]: https://bugs.freedesktop.org/show_bug.cgi?id=104782
[fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
[fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
[fdo#105682]: https://bugs.freedesktop.org/show_bug.cgi?id=105682
[fdo#105683]: https://bugs.freedesktop.org/show_bug.cgi?id=105683
[fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763
[fdo#106538]: https://bugs.freedesktop.org/show_bug.cgi?id=106538
[fdo#106885]: https://bugs.freedesktop.org/show_bug.cgi?id=106885
[fdo#106978]: https://bugs.freedesktop.org/show_bug.cgi?id=106978
[fdo#107469]: https://bugs.freedesktop.org/show_bug.cgi?id=107469
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107720]: https://bugs.freedesktop.org/show_bug.cgi?id=107720
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#107773]: https://bugs.freedesktop.org/show_bug.cgi?id=107773
[fdo#107791]: https://bugs.freedesktop.org/show_bug.cgi?id=107791
[fdo#107807]: https://bugs.freedesktop.org/show_bug.cgi?id=107807
[fdo#107815]: https://bugs.freedesktop.org/show_bug.cgi?id=107815
[fdo#107956]: https://bugs.freedesktop.org/show_bug.cgi?id=107956
[fdo#108039]: https://bugs.freedesktop.org/show_bug.cgi?id=108039
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108336]: https://bugs.freedesktop.org/show_bug.cgi?id=108336
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (7 -> 7)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_5358 -> Patchwork_11176
CI_DRM_5358: c6a0276a5007c01c64a8a80552b78c115e8a0dae @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4755: 0ba18cf75cafb51d1e72557528de4a1be640a85c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_11176: b6858ef7ab8fda7cd93db420e139507d4ca16a46 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_11176/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH] drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR
2019-01-02 16:35 [PATCH] drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR Chris Wilson
2019-01-02 17:10 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-01-02 18:24 ` ✓ Fi.CI.IGT: " Patchwork
@ 2019-01-03 10:25 ` Mika Kuoppala
2019-01-03 10:39 ` Chris Wilson
2 siblings, 1 reply; 5+ messages in thread
From: Mika Kuoppala @ 2019-01-03 10:25 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
Chris Wilson <chris@chris-wilson.co.uk> writes:
> On Baytail, notably, we can still detect missed interrupt syndrome
> (where we never spot a completed request). In this case, it can be
> alleviated by always keeping the interrupt unmasked, implying that the
> interrupt is being lost in the window after modifying the IMR. (This is
> the reason we still have the posting reads on enable_irq, if we remove
> them we miss interrupts!) Having narrowed the issue down to the IMR,
> rather than keeping it always enabled, applying the usual posting
> read/flush of the RING_IMR before unmasking the GT IMR also seems to
> prevent the missed interrupt. So be it.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/intel_ringbuffer.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> index 8967dcb5f58f..3d5d6b908148 100644
> --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> @@ -974,6 +974,10 @@ gen6_irq_enable(struct intel_engine_cs *engine)
> I915_WRITE_IMR(engine,
> ~(engine->irq_enable_mask |
> engine->irq_keep_mask));
> +
> + /* Flush/delay to ensure the RING_IMR is active before the GT IMR */
> + POSTING_READ_FW(RING_IMR(engine->mmio_base));
> +
I guess lifting this to be part of I915_WRITE_IMR would have caused
unwanted latencies on platforms that demonstratedly are free
of this sort of weirdness. I mean, the write should go in order
so the gpu view of events is consistent. Perhaps there
is some asyncness we can't grasp...or it is the delay like
the comment explains.
Acked-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> gen5_enable_gt_irq(dev_priv, engine->irq_enable_mask);
> }
>
> --
> 2.20.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR
2019-01-03 10:25 ` [PATCH] " Mika Kuoppala
@ 2019-01-03 10:39 ` Chris Wilson
0 siblings, 0 replies; 5+ messages in thread
From: Chris Wilson @ 2019-01-03 10:39 UTC (permalink / raw)
To: Mika Kuoppala, intel-gfx
Quoting Mika Kuoppala (2019-01-03 10:25:37)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
> > On Baytail, notably, we can still detect missed interrupt syndrome
> > (where we never spot a completed request). In this case, it can be
> > alleviated by always keeping the interrupt unmasked, implying that the
> > interrupt is being lost in the window after modifying the IMR. (This is
> > the reason we still have the posting reads on enable_irq, if we remove
> > them we miss interrupts!) Having narrowed the issue down to the IMR,
> > rather than keeping it always enabled, applying the usual posting
> > read/flush of the RING_IMR before unmasking the GT IMR also seems to
> > prevent the missed interrupt. So be it.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > ---
> > drivers/gpu/drm/i915/intel_ringbuffer.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > index 8967dcb5f58f..3d5d6b908148 100644
> > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > @@ -974,6 +974,10 @@ gen6_irq_enable(struct intel_engine_cs *engine)
> > I915_WRITE_IMR(engine,
> > ~(engine->irq_enable_mask |
> > engine->irq_keep_mask));
> > +
> > + /* Flush/delay to ensure the RING_IMR is active before the GT IMR */
> > + POSTING_READ_FW(RING_IMR(engine->mmio_base));
> > +
>
> I guess lifting this to be part of I915_WRITE_IMR would have caused
> unwanted latencies on platforms that demonstratedly are free
> of this sort of weirdness. I mean, the write should go in order
> so the gpu view of events is consistent. Perhaps there
> is some asyncness we can't grasp...or it is the delay like
> the comment explains.
The only plausible explanation I can give as to why this might actually
be a HW device and not just a delay is some latching, but even then I
would expect it to be tied to the IIR (if the ring had any!) rather than
the IMR.
Also better if we don't bury away magic too deeply if it's only required
for a single reason.
Fwiw, I tried removing the POSTING_READ(RING_IMR) elsewhere, and
bsw/bxt/glk all failed gem_sync (in CI no less, so \o/ for BAT sometimes
doing its job).
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-01-03 10:40 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-01-02 16:35 [PATCH] drm/i915/gen6: Flush RING_IMR changes before changing the global GT IMR Chris Wilson
2019-01-02 17:10 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-01-02 18:24 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-03 10:25 ` [PATCH] " Mika Kuoppala
2019-01-03 10:39 ` Chris Wilson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.