* [Intel-gfx] [CI] drm/i915/execlists: Workaround switching back to a complete context
@ 2020-03-27 20:14 Chris Wilson
2020-03-27 20:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
` (3 more replies)
0 siblings, 4 replies; 6+ messages in thread
From: Chris Wilson @ 2020-03-27 20:14 UTC (permalink / raw)
To: intel-gfx
In what seems remarkably similar to the w/a required to not reload an
idle context with HEAD==TAIL, it appears we must prevent the HW from
switching to an idle context in ELSP[1], while simultaneously trying to
preempt the HW to run another context and a continuation of the idle
context (which is no longer idle).
We can achieve this by preventing the context from completing while we
reload a new ELSP (by applying ring_set_paused(1) across the whole of
dequeue), except this eventually fails due to a lite-restore into a
waiting semaphore does not generate an ACK. Instead, we try to avoid
making the GPU do anything too challenging and not submit a new ELSP
while the interrupts + CSB events appear to have fallen behind the
completed contexts. We expect it to catch up shortly so we queue another
tasklet execution and hope for the best.
Closes: https://gitlab.freedesktop.org/drm/intel/issues/1501
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
---
drivers/gpu/drm/i915/gt/intel_lrc.c | 26 +++++++++++++++++++++++---
1 file changed, 23 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
index b12355048501..5f17ece07858 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc.c
+++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
@@ -1915,11 +1915,26 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
* of trouble.
*/
active = READ_ONCE(execlists->active);
- while ((last = *active) && i915_request_completed(last))
- active++;
- if (last) {
+ /*
+ * In theory we can skip over completed contexts that have not
+ * yet been processed by events (as those events are in flight):
+ *
+ * while ((last = *active) && i915_request_completed(last))
+ * active++;
+ *
+ * However, the GPU is cannot handle this as it will ultimately
+ * find itself trying to jump back into a context it has just
+ * completed and barf.
+ */
+
+ if ((last = *active)) {
if (need_preempt(engine, last, rb)) {
+ if (i915_request_completed(last)) {
+ tasklet_hi_schedule(&execlists->tasklet);
+ return;
+ }
+
ENGINE_TRACE(engine,
"preempting last=%llx:%lld, prio=%d, hint=%d\n",
last->fence.context,
@@ -1947,6 +1962,11 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
last = NULL;
} else if (need_timeslice(engine, last) &&
timer_expired(&engine->execlists.timer)) {
+ if (i915_request_completed(last)) {
+ tasklet_hi_schedule(&execlists->tasklet);
+ return;
+ }
+
ENGINE_TRACE(engine,
"expired last=%llx:%lld, prio=%d, hint=%d\n",
last->fence.context,
--
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] 6+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/execlists: Workaround switching back to a complete context
2020-03-27 20:14 [Intel-gfx] [CI] drm/i915/execlists: Workaround switching back to a complete context Chris Wilson
@ 2020-03-27 20:27 ` Patchwork
2020-03-27 20:33 ` [Intel-gfx] [CI] " Mika Kuoppala
` (2 subsequent siblings)
3 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2020-03-27 20:27 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/execlists: Workaround switching back to a complete context
URL : https://patchwork.freedesktop.org/series/75181/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
b7cd77b4f576 drm/i915/execlists: Workaround switching back to a complete context
-:51: ERROR:ASSIGN_IN_IF: do not use assignment in if condition
#51: FILE: drivers/gpu/drm/i915/gt/intel_lrc.c:1931:
+ if ((last = *active)) {
total: 1 errors, 0 warnings, 0 checks, 40 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Intel-gfx] [CI] drm/i915/execlists: Workaround switching back to a complete context
2020-03-27 20:14 [Intel-gfx] [CI] drm/i915/execlists: Workaround switching back to a complete context Chris Wilson
2020-03-27 20:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
@ 2020-03-27 20:33 ` Mika Kuoppala
2020-03-27 20:42 ` Chris Wilson
2020-03-27 20:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-03-28 16:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
3 siblings, 1 reply; 6+ messages in thread
From: Mika Kuoppala @ 2020-03-27 20:33 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
Chris Wilson <chris@chris-wilson.co.uk> writes:
> In what seems remarkably similar to the w/a required to not reload an
> idle context with HEAD==TAIL, it appears we must prevent the HW from
> switching to an idle context in ELSP[1], while simultaneously trying to
> preempt the HW to run another context and a continuation of the idle
> context (which is no longer idle).
>
> We can achieve this by preventing the context from completing while we
> reload a new ELSP (by applying ring_set_paused(1) across the whole of
> dequeue), except this eventually fails due to a lite-restore into a
> waiting semaphore does not generate an ACK. Instead, we try to avoid
> making the GPU do anything too challenging and not submit a new ELSP
> while the interrupts + CSB events appear to have fallen behind the
> completed contexts. We expect it to catch up shortly so we queue another
> tasklet execution and hope for the best.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/issues/1501
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_lrc.c | 26 +++++++++++++++++++++++---
> 1 file changed, 23 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index b12355048501..5f17ece07858 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -1915,11 +1915,26 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
> * of trouble.
> */
> active = READ_ONCE(execlists->active);
> - while ((last = *active) && i915_request_completed(last))
> - active++;
>
> - if (last) {
> + /*
> + * In theory we can skip over completed contexts that have not
> + * yet been processed by events (as those events are in flight):
> + *
> + * while ((last = *active) && i915_request_completed(last))
> + * active++;
> + *
> + * However, the GPU is cannot handle this as it will ultimately
s/is//
I applaud the straightforward nature of this compared to the pausing.
Albeit this seems to have a cost.
But this should be quite rare event comparatively?
> + * find itself trying to jump back into a context it has just
> + * completed and barf.
> + */
> +
> + if ((last = *active)) {
> if (need_preempt(engine, last, rb)) {
> + if (i915_request_completed(last)) {
> + tasklet_hi_schedule(&execlists->tasklet);
> + return;
> + }
> +
I was pondering of the lost tracing and if you can
work it backwards to this condition.
But I really hope this nails it,
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ENGINE_TRACE(engine,
> "preempting last=%llx:%lld, prio=%d, hint=%d\n",
> last->fence.context,
> @@ -1947,6 +1962,11 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
> last = NULL;
> } else if (need_timeslice(engine, last) &&
> timer_expired(&engine->execlists.timer)) {
> + if (i915_request_completed(last)) {
> + tasklet_hi_schedule(&execlists->tasklet);
> + return;
> + }
> +
> ENGINE_TRACE(engine,
> "expired last=%llx:%lld, prio=%d, hint=%d\n",
> last->fence.context,
> --
> 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] 6+ messages in thread
* Re: [Intel-gfx] [CI] drm/i915/execlists: Workaround switching back to a complete context
2020-03-27 20:33 ` [Intel-gfx] [CI] " Mika Kuoppala
@ 2020-03-27 20:42 ` Chris Wilson
0 siblings, 0 replies; 6+ messages in thread
From: Chris Wilson @ 2020-03-27 20:42 UTC (permalink / raw)
To: Mika Kuoppala, intel-gfx
Quoting Mika Kuoppala (2020-03-27 20:33:29)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
> > In what seems remarkably similar to the w/a required to not reload an
> > idle context with HEAD==TAIL, it appears we must prevent the HW from
> > switching to an idle context in ELSP[1], while simultaneously trying to
> > preempt the HW to run another context and a continuation of the idle
> > context (which is no longer idle).
> >
> > We can achieve this by preventing the context from completing while we
> > reload a new ELSP (by applying ring_set_paused(1) across the whole of
> > dequeue), except this eventually fails due to a lite-restore into a
> > waiting semaphore does not generate an ACK. Instead, we try to avoid
> > making the GPU do anything too challenging and not submit a new ELSP
> > while the interrupts + CSB events appear to have fallen behind the
> > completed contexts. We expect it to catch up shortly so we queue another
> > tasklet execution and hope for the best.
> >
> > Closes: https://gitlab.freedesktop.org/drm/intel/issues/1501
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/gt/intel_lrc.c | 26 +++++++++++++++++++++++---
> > 1 file changed, 23 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> > index b12355048501..5f17ece07858 100644
> > --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> > +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> > @@ -1915,11 +1915,26 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
> > * of trouble.
> > */
> > active = READ_ONCE(execlists->active);
> > - while ((last = *active) && i915_request_completed(last))
> > - active++;
> >
> > - if (last) {
> > + /*
> > + * In theory we can skip over completed contexts that have not
> > + * yet been processed by events (as those events are in flight):
> > + *
> > + * while ((last = *active) && i915_request_completed(last))
> > + * active++;
> > + *
> > + * However, the GPU is cannot handle this as it will ultimately
>
> s/is//
>
> I applaud the straightforward nature of this compared to the pausing.
> Albeit this seems to have a cost.
>
> But this should be quite rare event comparatively?
In the grand scheme of things, yes, it should only be short-circuiting
the interrupt delivery prior to direct submission or a preemption bump.
But since the request is complete, there should be nothing to stop the
context from completing, triggering the CSB event and sending the
interrupt. So it should be, one hopes, about 100ns at most behind.
> > + * find itself trying to jump back into a context it has just
> > + * completed and barf.
> > + */
> > +
> > + if ((last = *active)) {
> > if (need_preempt(engine, last, rb)) {
> > + if (i915_request_completed(last)) {
> > + tasklet_hi_schedule(&execlists->tasklet);
> > + return;
> > + }
> > +
>
> I was pondering of the lost tracing and if you can
> work it backwards to this condition.
We back out, but we will back again and will likely need to preempt
after we handle the next CSB event. So it's just "gpu is not ready yet,
no decision made" noise.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/execlists: Workaround switching back to a complete context
2020-03-27 20:14 [Intel-gfx] [CI] drm/i915/execlists: Workaround switching back to a complete context Chris Wilson
2020-03-27 20:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-03-27 20:33 ` [Intel-gfx] [CI] " Mika Kuoppala
@ 2020-03-27 20:59 ` Patchwork
2020-03-28 16:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
3 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2020-03-27 20:59 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/execlists: Workaround switching back to a complete context
URL : https://patchwork.freedesktop.org/series/75181/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8205 -> Patchwork_17119
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/index.html
Known issues
------------
Here are the changes found in Patchwork_17119 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-cml-u2: [PASS][1] -> [DMESG-WARN][2] ([IGT#4])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/fi-cml-u2/igt@kms_chamelium@common-hpd-after-suspend.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/fi-cml-u2/igt@kms_chamelium@common-hpd-after-suspend.html
[IGT#4]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/4
Participating hosts (42 -> 39)
------------------------------
Additional (4): fi-hsw-peppy fi-gdg-551 fi-bsw-kefka fi-snb-2600
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-glk-dsi fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8205 -> Patchwork_17119
CI-20190529: 20190529
CI_DRM_8205: ab978953f30ee06195d7f77952bd9fc17cb317f7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5543: 779d43cda49c230afd32c37730ad853f02e9d749 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17119: b7cd77b4f576b736131012a656b225084f8c5dff @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
b7cd77b4f576 drm/i915/execlists: Workaround switching back to a complete context
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/execlists: Workaround switching back to a complete context
2020-03-27 20:14 [Intel-gfx] [CI] drm/i915/execlists: Workaround switching back to a complete context Chris Wilson
` (2 preceding siblings ...)
2020-03-27 20:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
@ 2020-03-28 16:53 ` Patchwork
3 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2020-03-28 16:53 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/execlists: Workaround switching back to a complete context
URL : https://patchwork.freedesktop.org/series/75181/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8205_full -> Patchwork_17119_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_17119_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_busy@busy-vcs1:
- shard-iclb: [PASS][1] -> [SKIP][2] ([fdo#112080]) +10 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb4/igt@gem_busy@busy-vcs1.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb3/igt@gem_busy@busy-vcs1.html
* igt@gem_exec_balancer@smoke:
- shard-iclb: [PASS][3] -> [SKIP][4] ([fdo#110854])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb1/igt@gem_exec_balancer@smoke.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb8/igt@gem_exec_balancer@smoke.html
* igt@gem_exec_schedule@implicit-both-bsd:
- shard-iclb: [PASS][5] -> [SKIP][6] ([i915#677]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb6/igt@gem_exec_schedule@implicit-both-bsd.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb1/igt@gem_exec_schedule@implicit-both-bsd.html
* igt@gem_exec_schedule@implicit-read-write-bsd1:
- shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#109276] / [i915#677])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb2/igt@gem_exec_schedule@implicit-read-write-bsd1.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb6/igt@gem_exec_schedule@implicit-read-write-bsd1.html
* igt@gem_exec_schedule@preempt-other-chain-bsd:
- shard-iclb: [PASS][9] -> [SKIP][10] ([fdo#112146]) +7 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb5/igt@gem_exec_schedule@preempt-other-chain-bsd.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb4/igt@gem_exec_schedule@preempt-other-chain-bsd.html
* igt@gem_exec_schedule@promotion-bsd1:
- shard-iclb: [PASS][11] -> [SKIP][12] ([fdo#109276]) +18 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb4/igt@gem_exec_schedule@promotion-bsd1.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb3/igt@gem_exec_schedule@promotion-bsd1.html
* igt@gem_exec_suspend@basic-s3:
- shard-kbl: [PASS][13] -> [DMESG-WARN][14] ([i915#180]) +4 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-kbl2/igt@gem_exec_suspend@basic-s3.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-kbl6/igt@gem_exec_suspend@basic-s3.html
* igt@gem_reg_read@timestamp-monotonic:
- shard-hsw: [PASS][15] -> [INCOMPLETE][16] ([i915#61])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-hsw8/igt@gem_reg_read@timestamp-monotonic.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-hsw8/igt@gem_reg_read@timestamp-monotonic.html
* igt@gem_softpin@noreloc-s3:
- shard-skl: [PASS][17] -> [INCOMPLETE][18] ([i915#69])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-skl7/igt@gem_softpin@noreloc-s3.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-skl6/igt@gem_softpin@noreloc-s3.html
* igt@gen9_exec_parse@allowed-all:
- shard-apl: [PASS][19] -> [DMESG-WARN][20] ([i915#716])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-apl1/igt@gen9_exec_parse@allowed-all.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-apl4/igt@gen9_exec_parse@allowed-all.html
- shard-glk: [PASS][21] -> [DMESG-WARN][22] ([i915#716])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-glk3/igt@gen9_exec_parse@allowed-all.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-glk9/igt@gen9_exec_parse@allowed-all.html
* igt@i915_selftest@live@requests:
- shard-tglb: [PASS][23] -> [INCOMPLETE][24] ([i915#1531])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-tglb7/igt@i915_selftest@live@requests.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-tglb1/igt@i915_selftest@live@requests.html
* igt@kms_color@pipe-a-ctm-0-5:
- shard-skl: [PASS][25] -> [FAIL][26] ([i915#182])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-skl3/igt@kms_color@pipe-a-ctm-0-5.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-skl7/igt@kms_color@pipe-a-ctm-0-5.html
* igt@kms_draw_crc@draw-method-rgb565-render-untiled:
- shard-skl: [PASS][27] -> [FAIL][28] ([i915#52] / [i915#54]) +1 similar issue
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-skl3/igt@kms_draw_crc@draw-method-rgb565-render-untiled.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-skl7/igt@kms_draw_crc@draw-method-rgb565-render-untiled.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-skl: [PASS][29] -> [FAIL][30] ([i915#79])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-skl7/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-skl6/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][31] -> [FAIL][32] ([i915#1188])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-skl6/igt@kms_hdr@bpc-switch-dpms.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-skl1/igt@kms_hdr@bpc-switch-dpms.html
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: [PASS][33] -> [FAIL][34] ([fdo#108145]) +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-skl6/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-skl10/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-glk: [PASS][35] -> [FAIL][36] ([i915#899])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-glk2/igt@kms_plane_lowres@pipe-a-tiling-x.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-glk1/igt@kms_plane_lowres@pipe-a-tiling-x.html
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [PASS][37] -> [SKIP][38] ([fdo#109441]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb6/igt@kms_psr@psr2_no_drrs.html
* igt@kms_setmode@basic:
- shard-apl: [PASS][39] -> [FAIL][40] ([i915#31])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-apl3/igt@kms_setmode@basic.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-apl6/igt@kms_setmode@basic.html
#### Possible fixes ####
* igt@gem_exec_parallel@vcs1-fds:
- shard-iclb: [SKIP][41] ([fdo#112080]) -> [PASS][42] +9 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb7/igt@gem_exec_parallel@vcs1-fds.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb4/igt@gem_exec_parallel@vcs1-fds.html
* igt@gem_exec_schedule@implicit-write-read-bsd1:
- shard-iclb: [SKIP][43] ([fdo#109276] / [i915#677]) -> [PASS][44] +1 similar issue
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb6/igt@gem_exec_schedule@implicit-write-read-bsd1.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb1/igt@gem_exec_schedule@implicit-write-read-bsd1.html
* igt@gem_exec_schedule@pi-distinct-iova-bsd:
- shard-iclb: [SKIP][45] ([i915#677]) -> [PASS][46] +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb4/igt@gem_exec_schedule@pi-distinct-iova-bsd.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb7/igt@gem_exec_schedule@pi-distinct-iova-bsd.html
* igt@gem_exec_schedule@preempt-queue-bsd:
- shard-iclb: [SKIP][47] ([fdo#112146]) -> [PASS][48] +4 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb2/igt@gem_exec_schedule@preempt-queue-bsd.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb7/igt@gem_exec_schedule@preempt-queue-bsd.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-snb: [TIMEOUT][49] ([i915#1526]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-snb1/igt@i915_pm_rc6_residency@rc6-idle.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-snb5/igt@i915_pm_rc6_residency@rc6-idle.html
- shard-glk: [FAIL][51] ([i915#1527]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-glk3/igt@i915_pm_rc6_residency@rc6-idle.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-glk8/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@i915_selftest@live@hangcheck:
- shard-apl: [INCOMPLETE][53] -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-apl6/igt@i915_selftest@live@hangcheck.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-apl7/igt@i915_selftest@live@hangcheck.html
* igt@kms_cursor_crc@pipe-a-cursor-256x85-sliding:
- shard-kbl: [FAIL][55] ([i915#54] / [i915#93] / [i915#95]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-kbl7/igt@kms_cursor_crc@pipe-a-cursor-256x85-sliding.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-kbl3/igt@kms_cursor_crc@pipe-a-cursor-256x85-sliding.html
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [DMESG-WARN][57] ([i915#180]) -> [PASS][58] +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-kbl2/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-kbl2/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
* igt@kms_flip@flip-vs-expired-vblank:
- shard-skl: [FAIL][59] ([i915#79]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-skl3/igt@kms_flip@flip-vs-expired-vblank.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-skl7/igt@kms_flip@flip-vs-expired-vblank.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][61] ([i915#180] / [i915#93] / [i915#95]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-suspend.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-kbl2/igt@kms_frontbuffer_tracking@fbc-suspend.html
- shard-apl: [DMESG-WARN][63] ([i915#180] / [i915#95]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-apl4/igt@kms_frontbuffer_tracking@fbc-suspend.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-apl3/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_hdr@bpc-switch-suspend:
- shard-apl: [DMESG-WARN][65] ([i915#180]) -> [PASS][66] +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-apl3/igt@kms_hdr@bpc-switch-suspend.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-apl6/igt@kms_hdr@bpc-switch-suspend.html
- shard-skl: [FAIL][67] ([i915#1188]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-skl5/igt@kms_hdr@bpc-switch-suspend.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-skl9/igt@kms_hdr@bpc-switch-suspend.html
* igt@kms_psr@no_drrs:
- shard-iclb: [FAIL][69] ([i915#173]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb1/igt@kms_psr@no_drrs.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb3/igt@kms_psr@no_drrs.html
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [SKIP][71] ([fdo#109441]) -> [PASS][72] +1 similar issue
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb3/igt@kms_psr@psr2_primary_page_flip.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
* {igt@perf@blocking-parameterized}:
- shard-hsw: [FAIL][73] -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-hsw5/igt@perf@blocking-parameterized.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-hsw6/igt@perf@blocking-parameterized.html
* igt@prime_vgem@fence-wait-bsd2:
- shard-iclb: [SKIP][75] ([fdo#109276]) -> [PASS][76] +22 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-iclb6/igt@prime_vgem@fence-wait-bsd2.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-iclb1/igt@prime_vgem@fence-wait-bsd2.html
#### Warnings ####
* igt@runner@aborted:
- shard-apl: [FAIL][77] ([i915#1423]) -> ([FAIL][78], [FAIL][79], [FAIL][80]) ([i915#1423] / [i915#529] / [i915#716])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8205/shard-apl8/igt@runner@aborted.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-apl8/igt@runner@aborted.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-apl4/igt@runner@aborted.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17119/shard-apl7/igt@runner@aborted.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#1423]: https://gitlab.freedesktop.org/drm/intel/issues/1423
[i915#1526]: https://gitlab.freedesktop.org/drm/intel/issues/1526
[i915#1527]: https://gitlab.freedesktop.org/drm/intel/issues/1527
[i915#1531]: https://gitlab.freedesktop.org/drm/intel/issues/1531
[i915#173]: https://gitlab.freedesktop.org/drm/intel/issues/173
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#182]: https://gitlab.freedesktop.org/drm/intel/issues/182
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#52]: https://gitlab.freedesktop.org/drm/intel/issues/52
[i915#529]: https://gitlab.freedesktop.org/drm/intel/issues/529
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61
[i915#677]: https://gitlab.freedesktop.org/drm/intel/issues/677
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#899]: https://gitlab.freedesktop.org/drm/intel/issues/899
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8205 -> Patchwork_17119
CI-20190529: 20190529
CI_DRM_8205: ab978953f30ee06195d7f77952bd9fc17cb317f7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5543: 779d43cda49c230afd32c37730ad853f02e9d749 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17119: b7cd77b4f576b736131012a656b225084f8c5dff @ 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_17119/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-03-28 16:53 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-27 20:14 [Intel-gfx] [CI] drm/i915/execlists: Workaround switching back to a complete context Chris Wilson
2020-03-27 20:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-03-27 20:33 ` [Intel-gfx] [CI] " Mika Kuoppala
2020-03-27 20:42 ` Chris Wilson
2020-03-27 20:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-03-28 16:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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.