* [PATCH i-g-t] i915/gem_map_gtt: Escape from slow forked GTT access
@ 2019-09-24 12:18 Chris Wilson
2019-09-24 12:44 ` Mika Kuoppala
` (3 more replies)
0 siblings, 4 replies; 6+ messages in thread
From: Chris Wilson @ 2019-09-24 12:18 UTC (permalink / raw)
To: intel-gfx
Beware the slithy t'oves.
Forked GTT access on icl is notoriously slow, so rather than spend an
eternity checking the whole object, check for a completion event after
handling the pagefault. It's is the race of the pagefault vs reset that
we care most about, and we expect the bug to result in the pagefault
being blocked indefinitely, so checking afterwards does not reduce
coverage.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
---
tests/i915/gem_mmap_gtt.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c
index 0428a1372..91da5a37b 100644
--- a/tests/i915/gem_mmap_gtt.c
+++ b/tests/i915/gem_mmap_gtt.c
@@ -602,6 +602,9 @@ test_hang(int fd)
gtt[0][x] = patterns[next_pattern];
gtt[1][x] = patterns[next_pattern];
+
+ if (READ_ONCE(control->done))
+ break;
}
last_pattern = next_pattern;
--
2.23.0
_______________________________________________
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* Re: [PATCH i-g-t] i915/gem_map_gtt: Escape from slow forked GTT access
2019-09-24 12:18 [PATCH i-g-t] i915/gem_map_gtt: Escape from slow forked GTT access Chris Wilson
@ 2019-09-24 12:44 ` Mika Kuoppala
2019-09-24 12:48 ` Chris Wilson
2019-09-24 12:53 ` ✓ Fi.CI.BAT: success for " Patchwork
` (2 subsequent siblings)
3 siblings, 1 reply; 6+ messages in thread
From: Mika Kuoppala @ 2019-09-24 12:44 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Beware the slithy t'oves.
>
> Forked GTT access on icl is notoriously slow, so rather than spend an
> eternity checking the whole object, check for a completion event after
> handling the pagefault. It's is the race of the pagefault vs reset that
> we care most about, and we expect the bug to result in the pagefault
> being blocked indefinitely, so checking afterwards does not reduce
> coverage.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> tests/i915/gem_mmap_gtt.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c
> index 0428a1372..91da5a37b 100644
> --- a/tests/i915/gem_mmap_gtt.c
> +++ b/tests/i915/gem_mmap_gtt.c
> @@ -602,6 +602,9 @@ test_hang(int fd)
>
> gtt[0][x] = patterns[next_pattern];
> gtt[1][x] = patterns[next_pattern];
> +
> + if (READ_ONCE(control->done))
> + break;
The hang would have manifested itself on a previous loop
already.
So you could life the exit condition before the writes.
-Mika
> }
>
> last_pattern = next_pattern;
> --
> 2.23.0
_______________________________________________
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: [PATCH i-g-t] i915/gem_map_gtt: Escape from slow forked GTT access
2019-09-24 12:44 ` Mika Kuoppala
@ 2019-09-24 12:48 ` Chris Wilson
0 siblings, 0 replies; 6+ messages in thread
From: Chris Wilson @ 2019-09-24 12:48 UTC (permalink / raw)
To: Mika Kuoppala, intel-gfx
Quoting Mika Kuoppala (2019-09-24 13:44:54)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
> > Beware the slithy t'oves.
> >
> > Forked GTT access on icl is notoriously slow, so rather than spend an
> > eternity checking the whole object, check for a completion event after
> > handling the pagefault. It's is the race of the pagefault vs reset that
> > we care most about, and we expect the bug to result in the pagefault
> > being blocked indefinitely, so checking afterwards does not reduce
> > coverage.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> > ---
> > tests/i915/gem_mmap_gtt.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c
> > index 0428a1372..91da5a37b 100644
> > --- a/tests/i915/gem_mmap_gtt.c
> > +++ b/tests/i915/gem_mmap_gtt.c
> > @@ -602,6 +602,9 @@ test_hang(int fd)
> >
> > gtt[0][x] = patterns[next_pattern];
> > gtt[1][x] = patterns[next_pattern];
> > +
> > + if (READ_ONCE(control->done))
> > + break;
>
> The hang would have manifested itself on a previous loop
> already.
>
> So you could life the exit condition before the writes.
The writes may also cause a fresh fault. The idea was to simply check
more frequently than once per object -- so long as we check within 2s of
the termination request, we are good.
-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
* ✓ Fi.CI.BAT: success for i915/gem_map_gtt: Escape from slow forked GTT access
2019-09-24 12:18 [PATCH i-g-t] i915/gem_map_gtt: Escape from slow forked GTT access Chris Wilson
2019-09-24 12:44 ` Mika Kuoppala
@ 2019-09-24 12:53 ` Patchwork
2019-09-24 13:09 ` [PATCH i-g-t] " Mika Kuoppala
2019-09-25 1:03 ` ✓ Fi.CI.IGT: success for " Patchwork
3 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2019-09-24 12:53 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: i915/gem_map_gtt: Escape from slow forked GTT access
URL : https://patchwork.freedesktop.org/series/67161/
State : success
== Summary ==
CI Bug Log - changes from IGT_5201 -> IGTPW_3495
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/67161/revisions/1/mbox/
Known issues
------------
Here are the changes found in IGTPW_3495 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@i915_selftest@live_hangcheck:
- {fi-icl-dsi}: [INCOMPLETE][1] ([fdo#107713] / [fdo#108569]) -> [PASS][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/fi-icl-dsi/igt@i915_selftest@live_hangcheck.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/fi-icl-dsi/igt@i915_selftest@live_hangcheck.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
Participating hosts (52 -> 45)
------------------------------
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5201 -> IGTPW_3495
CI-20190529: 20190529
CI_DRM_6947: 567ef14d043c8fd9d9d948dac219c68216fda305 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3495: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/
IGT_5201: 3c1633abec14679300d52eeaf9fb7b63e435e51e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/
_______________________________________________
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: [PATCH i-g-t] i915/gem_map_gtt: Escape from slow forked GTT access
2019-09-24 12:18 [PATCH i-g-t] i915/gem_map_gtt: Escape from slow forked GTT access Chris Wilson
2019-09-24 12:44 ` Mika Kuoppala
2019-09-24 12:53 ` ✓ Fi.CI.BAT: success for " Patchwork
@ 2019-09-24 13:09 ` Mika Kuoppala
2019-09-25 1:03 ` ✓ Fi.CI.IGT: success for " Patchwork
3 siblings, 0 replies; 6+ messages in thread
From: Mika Kuoppala @ 2019-09-24 13:09 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Beware the slithy t'oves.
>
> Forked GTT access on icl is notoriously slow, so rather than spend an
> eternity checking the whole object, check for a completion event after
> handling the pagefault. It's is the race of the pagefault vs reset that
> we care most about, and we expect the bug to result in the pagefault
> being blocked indefinitely, so checking afterwards does not reduce
> coverage.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> tests/i915/gem_mmap_gtt.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c
> index 0428a1372..91da5a37b 100644
> --- a/tests/i915/gem_mmap_gtt.c
> +++ b/tests/i915/gem_mmap_gtt.c
> @@ -602,6 +602,9 @@ test_hang(int fd)
>
> gtt[0][x] = patterns[next_pattern];
> gtt[1][x] = patterns[next_pattern];
> +
> + if (READ_ONCE(control->done))
> + break;
> }
>
> last_pattern = next_pattern;
> --
> 2.23.0
_______________________________________________
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
* ✓ Fi.CI.IGT: success for i915/gem_map_gtt: Escape from slow forked GTT access
2019-09-24 12:18 [PATCH i-g-t] i915/gem_map_gtt: Escape from slow forked GTT access Chris Wilson
` (2 preceding siblings ...)
2019-09-24 13:09 ` [PATCH i-g-t] " Mika Kuoppala
@ 2019-09-25 1:03 ` Patchwork
3 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2019-09-25 1:03 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: i915/gem_map_gtt: Escape from slow forked GTT access
URL : https://patchwork.freedesktop.org/series/67161/
State : success
== Summary ==
CI Bug Log - changes from IGT_5201_full -> IGTPW_3495_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/67161/revisions/1/mbox/
Known issues
------------
Here are the changes found in IGTPW_3495_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_schedule@independent-bsd1:
- shard-iclb: [PASS][1] -> [SKIP][2] ([fdo#109276]) +8 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb4/igt@gem_exec_schedule@independent-bsd1.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb8/igt@gem_exec_schedule@independent-bsd1.html
* igt@gem_exec_schedule@preempt-other-chain-bsd:
- shard-iclb: [PASS][3] -> [SKIP][4] ([fdo#111325]) +3 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb5/igt@gem_exec_schedule@preempt-other-chain-bsd.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb4/igt@gem_exec_schedule@preempt-other-chain-bsd.html
* igt@gem_workarounds@suspend-resume:
- shard-apl: [PASS][5] -> [DMESG-WARN][6] ([fdo#108566]) +9 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-apl3/igt@gem_workarounds@suspend-resume.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-apl7/igt@gem_workarounds@suspend-resume.html
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy:
- shard-hsw: [PASS][7] -> [FAIL][8] ([fdo#105767])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-hsw7/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-hsw1/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-apl: [PASS][9] -> [INCOMPLETE][10] ([fdo#103927])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-apl7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-apl4/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-kbl: [PASS][11] -> [INCOMPLETE][12] ([fdo#103665]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-kbl6/igt@kms_flip@flip-vs-suspend-interruptible.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-kbl1/igt@kms_flip@flip-vs-suspend-interruptible.html
- shard-hsw: [PASS][13] -> [INCOMPLETE][14] ([fdo#103540])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-hsw8/igt@kms_flip@flip-vs-suspend-interruptible.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-hsw4/igt@kms_flip@flip-vs-suspend-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-pwrite:
- shard-glk: [PASS][15] -> [FAIL][16] ([fdo#103167])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-glk6/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-pwrite.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-glk9/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@fbc-rgb565-draw-blt:
- shard-iclb: [PASS][17] -> [INCOMPLETE][18] ([fdo#107713])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb6/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-blt.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-rgb565-draw-blt.html
* igt@kms_frontbuffer_tracking@fbc-stridechange:
- shard-iclb: [PASS][19] -> [FAIL][20] ([fdo#103167]) +4 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-stridechange.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-stridechange.html
* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-iclb: [PASS][21] -> [FAIL][22] ([fdo#103166])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb6/igt@kms_plane_lowres@pipe-a-tiling-x.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb8/igt@kms_plane_lowres@pipe-a-tiling-x.html
* igt@kms_psr@psr2_cursor_render:
- shard-iclb: [PASS][23] -> [SKIP][24] ([fdo#109441]) +2 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb2/igt@kms_psr@psr2_cursor_render.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb6/igt@kms_psr@psr2_cursor_render.html
* igt@kms_setmode@basic:
- shard-apl: [PASS][25] -> [FAIL][26] ([fdo#99912])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-apl7/igt@kms_setmode@basic.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-apl1/igt@kms_setmode@basic.html
- shard-kbl: [PASS][27] -> [FAIL][28] ([fdo#99912])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-kbl7/igt@kms_setmode@basic.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-kbl1/igt@kms_setmode@basic.html
#### Possible fixes ####
* igt@gem_ctx_shared@exec-single-timeline-bsd:
- shard-iclb: [SKIP][29] ([fdo#110841]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb2/igt@gem_ctx_shared@exec-single-timeline-bsd.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb5/igt@gem_ctx_shared@exec-single-timeline-bsd.html
* igt@gem_ctx_switch@legacy-bsd2-heavy:
- shard-iclb: [SKIP][31] ([fdo#109276]) -> [PASS][32] +13 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb5/igt@gem_ctx_switch@legacy-bsd2-heavy.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb4/igt@gem_ctx_switch@legacy-bsd2-heavy.html
* igt@gem_exec_balancer@smoke:
- shard-iclb: [SKIP][33] ([fdo#110854]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb6/igt@gem_exec_balancer@smoke.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb1/igt@gem_exec_balancer@smoke.html
* igt@gem_exec_schedule@promotion-bsd:
- shard-iclb: [SKIP][35] ([fdo#111325]) -> [PASS][36] +4 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb2/igt@gem_exec_schedule@promotion-bsd.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb7/igt@gem_exec_schedule@promotion-bsd.html
* igt@i915_pm_rps@waitboost:
- shard-apl: [FAIL][37] ([fdo#102250]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-apl6/igt@i915_pm_rps@waitboost.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-apl5/igt@i915_pm_rps@waitboost.html
* igt@i915_suspend@sysfs-reader:
- shard-apl: [DMESG-WARN][39] ([fdo#108566]) -> [PASS][40] +7 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-apl8/igt@i915_suspend@sysfs-reader.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-apl5/igt@i915_suspend@sysfs-reader.html
* igt@kms_cursor_crc@pipe-a-cursor-128x128-random:
- shard-kbl: [FAIL][41] ([fdo#103232]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-kbl6/igt@kms_cursor_crc@pipe-a-cursor-128x128-random.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-128x128-random.html
- shard-apl: [FAIL][43] ([fdo#103232]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-apl3/igt@kms_cursor_crc@pipe-a-cursor-128x128-random.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-apl1/igt@kms_cursor_crc@pipe-a-cursor-128x128-random.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-blt:
- shard-iclb: [FAIL][45] ([fdo#103167]) -> [PASS][46] +2 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-blt.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-blt.html
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][47] ([fdo#109642] / [fdo#111068]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb7/igt@kms_psr2_su@frontbuffer.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb2/igt@kms_psr2_su@frontbuffer.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [SKIP][49] ([fdo#109441]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb4/igt@kms_psr@psr2_cursor_mmap_cpu.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend:
- shard-kbl: [INCOMPLETE][51] ([fdo#103665]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-kbl2/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
#### Warnings ####
* igt@gem_ctx_isolation@vcs1-nonpriv:
- shard-iclb: [SKIP][53] ([fdo#109276]) -> [FAIL][54] ([fdo#111329])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb5/igt@gem_ctx_isolation@vcs1-nonpriv.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb1/igt@gem_ctx_isolation@vcs1-nonpriv.html
* igt@gem_mocs_settings@mocs-reset-bsd2:
- shard-iclb: [FAIL][55] ([fdo#111330]) -> [SKIP][56] ([fdo#109276])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-iclb4/igt@gem_mocs_settings@mocs-reset-bsd2.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-iclb3/igt@gem_mocs_settings@mocs-reset-bsd2.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-apl: [INCOMPLETE][57] ([fdo#103927]) -> [DMESG-WARN][58] ([fdo#108566])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5201/shard-apl3/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/shard-apl3/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[fdo#102250]: https://bugs.freedesktop.org/show_bug.cgi?id=102250
[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#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540
[fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#105767]: https://bugs.freedesktop.org/show_bug.cgi?id=105767
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841
[fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325
[fdo#111329]: https://bugs.freedesktop.org/show_bug.cgi?id=111329
[fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330
[fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
Participating hosts (7 -> 6)
------------------------------
Missing (1): shard-skl
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5201 -> IGTPW_3495
CI-20190529: 20190529
CI_DRM_6947: 567ef14d043c8fd9d9d948dac219c68216fda305 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3495: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/
IGT_5201: 3c1633abec14679300d52eeaf9fb7b63e435e51e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3495/
_______________________________________________
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:[~2019-09-25 1:03 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-09-24 12:18 [PATCH i-g-t] i915/gem_map_gtt: Escape from slow forked GTT access Chris Wilson
2019-09-24 12:44 ` Mika Kuoppala
2019-09-24 12:48 ` Chris Wilson
2019-09-24 12:53 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-09-24 13:09 ` [PATCH i-g-t] " Mika Kuoppala
2019-09-25 1:03 ` ✓ Fi.CI.IGT: success for " 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.