* [Intel-gfx] [PATCH i-g-t] i915/gem_exec_balancer: Force timeslicing of the virtual request
@ 2020-05-14 11:29 ` Chris Wilson
0 siblings, 0 replies; 5+ messages in thread
From: Chris Wilson @ 2020-05-14 11:29 UTC (permalink / raw)
To: intel-gfx; +Cc: igt-dev, Chris Wilson
Investigate the impact of timeslicing on the virtal request, both with
independent and dependent workloads.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
tests/i915/gem_exec_balancer.c | 101 +++++++++++++++++++++++++++++++++
1 file changed, 101 insertions(+)
diff --git a/tests/i915/gem_exec_balancer.c b/tests/i915/gem_exec_balancer.c
index d4944e3f1..607f1dc38 100644
--- a/tests/i915/gem_exec_balancer.c
+++ b/tests/i915/gem_exec_balancer.c
@@ -1531,6 +1531,104 @@ static void full(int i915, unsigned int flags)
gem_quiescent_gpu(i915);
}
+static void sliced(int i915)
+{
+ /*
+ * Let's investigate what happens when the virtual request is
+ * timesliced away.
+ *
+ * If the engine is busy with independent work, we want the virtual
+ * request to hop over to an idle engine (within its balancing set).
+ * However, if the work is dependent upon the virtual request,
+ * we most certainly do not want to reschedule that work ahead of
+ * the virtual request. [If we did, we should still have the saving
+ * grace of being able to move the virual request to another engine
+ * and so run both in parallel.] If we do neither, and get stuck
+ * on the dependent work and never run the virtual request, we hang.
+ */
+
+ igt_require(gem_scheduler_has_preemption(i915));
+ igt_require(gem_scheduler_has_semaphores(i915));
+
+ for (int class = 0; class < 32; class++) {
+ struct i915_engine_class_instance *ci;
+ int64_t timeout = NSEC_PER_SEC;
+ igt_spin_t *virtual, **load;
+ unsigned int count;
+ uint32_t ctx;
+
+ ci = list_engines(i915, 1u << class, &count);
+ if (!ci)
+ continue;
+
+ if (count < 2) {
+ free(ci);
+ continue;
+ }
+
+ load = calloc(count, sizeof(*load));
+ igt_assert(load);
+
+ ctx = load_balancer_create(i915, ci, count);
+
+ /* Independent load */
+ virtual = igt_spin_new(i915, ctx,
+ .flags = IGT_SPIN_POLL_RUN);
+ igt_spin_busywait_until_started(virtual);
+ for (int i = 0; i < count; i++) {
+ load[i] = igt_spin_new(i915, ctx,
+ .engine = i + 1,
+ .flags = IGT_SPIN_POLL_RUN);
+ igt_spin_busywait_until_started(load[i]);
+ }
+ /*
+ * As we waited until all requests started, and we
+ * oversubscribed the engines, we know that we must have
+ * forced the virtual request to be timesliced away.
+ *
+ * We then expect for it to receive a timeslice on congested
+ * engines, so that the spinned completes quickly.
+ */
+ igt_spin_end(virtual);
+ igt_assert_eq(gem_wait(i915, virtual->handle, &timeout), 0);
+
+ for (int i = 0; i < count; i++)
+ igt_spin_free(i915, load[i]);
+ igt_spin_free(i915, virtual);
+
+ /* Dependent load */
+ virtual = igt_spin_new(i915, ctx, .engine = 0,
+ .flags = (IGT_SPIN_FENCE_OUT |
+ IGT_SPIN_POLL_RUN));
+ for (int i = 0; i < count; i++) {
+ load[i] = igt_spin_new(i915, ctx,
+ .engine = i + 1,
+ .fence = virtual->out_fence,
+ .flags = IGT_SPIN_FENCE_IN);
+ /*
+ * We could wait until load[i] starts, but we do not
+ * want to mandate that the scheduler must evict
+ * the virtual request, as load[i] depends on
+ * the virtual request.
+ */
+ }
+
+ /* Wait long enough for the virtual timeslice [ms] to expire */
+ igt_spin_busywait_until_started(virtual);
+ usleep(250 * 1000); /* 250ms */
+
+ igt_spin_end(virtual);
+ igt_assert_eq(sync_fence_wait(virtual->out_fence, 1000), 0);
+ igt_assert_eq(sync_fence_status(virtual->out_fence), 1);
+
+ gem_context_destroy(i915, ctx);
+ free(load);
+ free(ci);
+ }
+
+ gem_quiescent_gpu(i915);
+}
+
static void nop(int i915)
{
struct drm_i915_gem_exec_object2 batch = {
@@ -2014,6 +2112,9 @@ igt_main
igt_subtest("semaphore")
semaphore(i915);
+ igt_subtest("sliced")
+ sliced(i915);
+
igt_subtest("smoke")
smoketest(i915, 20);
--
2.26.2
_______________________________________________
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
* [igt-dev] [PATCH i-g-t] i915/gem_exec_balancer: Force timeslicing of the virtual request
@ 2020-05-14 11:29 ` Chris Wilson
0 siblings, 0 replies; 5+ messages in thread
From: Chris Wilson @ 2020-05-14 11:29 UTC (permalink / raw)
To: intel-gfx; +Cc: igt-dev, Tvrtko Ursulin, Chris Wilson
Investigate the impact of timeslicing on the virtal request, both with
independent and dependent workloads.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
tests/i915/gem_exec_balancer.c | 101 +++++++++++++++++++++++++++++++++
1 file changed, 101 insertions(+)
diff --git a/tests/i915/gem_exec_balancer.c b/tests/i915/gem_exec_balancer.c
index d4944e3f1..607f1dc38 100644
--- a/tests/i915/gem_exec_balancer.c
+++ b/tests/i915/gem_exec_balancer.c
@@ -1531,6 +1531,104 @@ static void full(int i915, unsigned int flags)
gem_quiescent_gpu(i915);
}
+static void sliced(int i915)
+{
+ /*
+ * Let's investigate what happens when the virtual request is
+ * timesliced away.
+ *
+ * If the engine is busy with independent work, we want the virtual
+ * request to hop over to an idle engine (within its balancing set).
+ * However, if the work is dependent upon the virtual request,
+ * we most certainly do not want to reschedule that work ahead of
+ * the virtual request. [If we did, we should still have the saving
+ * grace of being able to move the virual request to another engine
+ * and so run both in parallel.] If we do neither, and get stuck
+ * on the dependent work and never run the virtual request, we hang.
+ */
+
+ igt_require(gem_scheduler_has_preemption(i915));
+ igt_require(gem_scheduler_has_semaphores(i915));
+
+ for (int class = 0; class < 32; class++) {
+ struct i915_engine_class_instance *ci;
+ int64_t timeout = NSEC_PER_SEC;
+ igt_spin_t *virtual, **load;
+ unsigned int count;
+ uint32_t ctx;
+
+ ci = list_engines(i915, 1u << class, &count);
+ if (!ci)
+ continue;
+
+ if (count < 2) {
+ free(ci);
+ continue;
+ }
+
+ load = calloc(count, sizeof(*load));
+ igt_assert(load);
+
+ ctx = load_balancer_create(i915, ci, count);
+
+ /* Independent load */
+ virtual = igt_spin_new(i915, ctx,
+ .flags = IGT_SPIN_POLL_RUN);
+ igt_spin_busywait_until_started(virtual);
+ for (int i = 0; i < count; i++) {
+ load[i] = igt_spin_new(i915, ctx,
+ .engine = i + 1,
+ .flags = IGT_SPIN_POLL_RUN);
+ igt_spin_busywait_until_started(load[i]);
+ }
+ /*
+ * As we waited until all requests started, and we
+ * oversubscribed the engines, we know that we must have
+ * forced the virtual request to be timesliced away.
+ *
+ * We then expect for it to receive a timeslice on congested
+ * engines, so that the spinned completes quickly.
+ */
+ igt_spin_end(virtual);
+ igt_assert_eq(gem_wait(i915, virtual->handle, &timeout), 0);
+
+ for (int i = 0; i < count; i++)
+ igt_spin_free(i915, load[i]);
+ igt_spin_free(i915, virtual);
+
+ /* Dependent load */
+ virtual = igt_spin_new(i915, ctx, .engine = 0,
+ .flags = (IGT_SPIN_FENCE_OUT |
+ IGT_SPIN_POLL_RUN));
+ for (int i = 0; i < count; i++) {
+ load[i] = igt_spin_new(i915, ctx,
+ .engine = i + 1,
+ .fence = virtual->out_fence,
+ .flags = IGT_SPIN_FENCE_IN);
+ /*
+ * We could wait until load[i] starts, but we do not
+ * want to mandate that the scheduler must evict
+ * the virtual request, as load[i] depends on
+ * the virtual request.
+ */
+ }
+
+ /* Wait long enough for the virtual timeslice [ms] to expire */
+ igt_spin_busywait_until_started(virtual);
+ usleep(250 * 1000); /* 250ms */
+
+ igt_spin_end(virtual);
+ igt_assert_eq(sync_fence_wait(virtual->out_fence, 1000), 0);
+ igt_assert_eq(sync_fence_status(virtual->out_fence), 1);
+
+ gem_context_destroy(i915, ctx);
+ free(load);
+ free(ci);
+ }
+
+ gem_quiescent_gpu(i915);
+}
+
static void nop(int i915)
{
struct drm_i915_gem_exec_object2 batch = {
@@ -2014,6 +2112,9 @@ igt_main
igt_subtest("semaphore")
semaphore(i915);
+ igt_subtest("sliced")
+ sliced(i915);
+
igt_subtest("smoke")
smoketest(i915, 20);
--
2.26.2
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 5+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_exec_balancer: Force timeslicing of the virtual request
2020-05-14 11:29 ` [igt-dev] " Chris Wilson
(?)
@ 2020-05-14 12:47 ` Patchwork
-1 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2020-05-14 12:47 UTC (permalink / raw)
To: Chris Wilson; +Cc: igt-dev
== Series Details ==
Series: i915/gem_exec_balancer: Force timeslicing of the virtual request
URL : https://patchwork.freedesktop.org/series/77261/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8485 -> IGTPW_4569
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/index.html
Known issues
------------
Here are the changes found in IGTPW_4569 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- {fi-tgl-dsi}: [INCOMPLETE][1] ([i915#1803]) -> [PASS][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/fi-tgl-dsi/igt@i915_selftest@live@execlists.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/fi-tgl-dsi/igt@i915_selftest@live@execlists.html
#### Warnings ####
* igt@i915_pm_rpm@module-reload:
- fi-kbl-x1275: [FAIL][3] ([i915#62] / [i915#95]) -> [SKIP][4] ([fdo#109271])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/fi-kbl-x1275/igt@i915_pm_rpm@module-reload.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/fi-kbl-x1275/igt@i915_pm_rpm@module-reload.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1803]: https://gitlab.freedesktop.org/drm/intel/issues/1803
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (50 -> 44)
------------------------------
Additional (1): fi-kbl-7560u
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-hsw-4770 fi-byt-clapper
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5654 -> IGTPW_4569
CI-20190529: 20190529
CI_DRM_8485: 0c6c45b4587580b4b7b2247d201a3b0f7af4b7f6 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4569: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/index.html
IGT_5654: 5637a466a0b09535517751608f5525a8b468a76b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Testlist changes ==
+igt@gem_exec_balancer@sliced
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 5+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for i915/gem_exec_balancer: Force timeslicing of the virtual request
2020-05-14 11:29 ` [igt-dev] " Chris Wilson
(?)
(?)
@ 2020-05-14 17:06 ` Patchwork
-1 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2020-05-14 17:06 UTC (permalink / raw)
To: Chris Wilson; +Cc: igt-dev
== Series Details ==
Series: i915/gem_exec_balancer: Force timeslicing of the virtual request
URL : https://patchwork.freedesktop.org/series/77261/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8485_full -> IGTPW_4569_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_4569_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_4569_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_4569_full:
### IGT changes ###
#### Possible regressions ####
* {igt@gem_exec_balancer@sliced} (NEW):
- shard-kbl: NOTRUN -> [FAIL][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl3/igt@gem_exec_balancer@sliced.html
- shard-tglb: NOTRUN -> [FAIL][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-tglb7/igt@gem_exec_balancer@sliced.html
* igt@i915_pm_dc@dc5-psr:
- shard-iclb: [PASS][3] -> [FAIL][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-iclb8/igt@i915_pm_dc@dc5-psr.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-iclb2/igt@i915_pm_dc@dc5-psr.html
- shard-tglb: [PASS][5] -> [FAIL][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-tglb8/igt@i915_pm_dc@dc5-psr.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-tglb6/igt@i915_pm_dc@dc5-psr.html
New tests
---------
New tests have been introduced between CI_DRM_8485_full and IGTPW_4569_full:
### New IGT tests (1) ###
* igt@gem_exec_balancer@sliced:
- Statuses : 2 fail(s) 3 pass(s) 1 skip(s)
- Exec time: [0.0, 3.27] s
Known issues
------------
Here are the changes found in IGTPW_4569_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@processes:
- shard-iclb: [PASS][7] -> [FAIL][8] ([i915#1528])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-iclb7/igt@gem_ctx_persistence@processes.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-iclb4/igt@gem_ctx_persistence@processes.html
* igt@i915_suspend@debugfs-reader:
- shard-kbl: [PASS][9] -> [DMESG-WARN][10] ([i915#180]) +2 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl2/igt@i915_suspend@debugfs-reader.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl1/igt@i915_suspend@debugfs-reader.html
* igt@kms_cursor_crc@pipe-a-cursor-256x256-random:
- shard-kbl: [PASS][11] -> [FAIL][12] ([i915#54] / [i915#93] / [i915#95]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl3/igt@kms_cursor_crc@pipe-a-cursor-256x256-random.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl3/igt@kms_cursor_crc@pipe-a-cursor-256x256-random.html
* igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy:
- shard-glk: [PASS][13] -> [FAIL][14] ([i915#72])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-glk7/igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-glk1/igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy.html
* igt@kms_draw_crc@fill-fb:
- shard-apl: [PASS][15] -> [FAIL][16] ([i915#95])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-apl7/igt@kms_draw_crc@fill-fb.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-apl2/igt@kms_draw_crc@fill-fb.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [PASS][17] -> [DMESG-WARN][18] ([i915#180] / [i915#93] / [i915#95])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl2/igt@kms_frontbuffer_tracking@fbc-suspend.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_plane_cursor@pipe-a-viewport-size-128:
- shard-apl: [PASS][19] -> [FAIL][20] ([i915#1559] / [i915#95])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-apl2/igt@kms_plane_cursor@pipe-a-viewport-size-128.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-apl3/igt@kms_plane_cursor@pipe-a-viewport-size-128.html
- shard-kbl: [PASS][21] -> [FAIL][22] ([i915#1559] / [i915#93] / [i915#95])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl4/igt@kms_plane_cursor@pipe-a-viewport-size-128.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl2/igt@kms_plane_cursor@pipe-a-viewport-size-128.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [PASS][23] -> [SKIP][24] ([fdo#109441]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-iclb5/igt@kms_psr@psr2_primary_mmap_cpu.html
#### Possible fixes ####
* {igt@gem_ctx_isolation@preservation-s3@rcs0}:
- shard-kbl: [DMESG-WARN][25] ([i915#180]) -> [PASS][26] +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl2/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl7/igt@gem_ctx_isolation@preservation-s3@rcs0.html
* igt@gem_exec_suspend@basic-s0:
- shard-tglb: [INCOMPLETE][27] ([i915#1602] / [i915#456]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-tglb3/igt@gem_exec_suspend@basic-s0.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-tglb8/igt@gem_exec_suspend@basic-s0.html
* igt@gen9_exec_parse@allowed-all:
- shard-glk: [DMESG-WARN][29] ([i915#1436] / [i915#716]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-glk5/igt@gen9_exec_parse@allowed-all.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-glk8/igt@gen9_exec_parse@allowed-all.html
* igt@i915_suspend@forcewake:
- shard-kbl: [DMESG-WARN][31] ([i915#165]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl3/igt@i915_suspend@forcewake.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl7/igt@i915_suspend@forcewake.html
* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-apl: [FAIL][33] ([i915#1119] / [i915#95]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-apl7/igt@kms_big_fb@linear-32bpp-rotate-180.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-apl3/igt@kms_big_fb@linear-32bpp-rotate-180.html
- shard-kbl: [FAIL][35] ([i915#1119] / [i915#93] / [i915#95]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl3/igt@kms_big_fb@linear-32bpp-rotate-180.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl3/igt@kms_big_fb@linear-32bpp-rotate-180.html
* igt@kms_cursor_crc@pipe-a-cursor-128x128-onscreen:
- shard-kbl: [FAIL][37] ([i915#54] / [i915#93] / [i915#95]) -> [PASS][38] +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-128x128-onscreen.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl4/igt@kms_cursor_crc@pipe-a-cursor-128x128-onscreen.html
* igt@kms_cursor_legacy@pipe-b-torture-bo:
- shard-iclb: [DMESG-WARN][39] ([i915#128]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-iclb5/igt@kms_cursor_legacy@pipe-b-torture-bo.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-iclb4/igt@kms_cursor_legacy@pipe-b-torture-bo.html
* igt@kms_draw_crc@draw-method-xrgb8888-pwrite-untiled:
- shard-apl: [FAIL][41] ([i915#52] / [i915#54] / [i915#95]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-apl1/igt@kms_draw_crc@draw-method-xrgb8888-pwrite-untiled.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-apl3/igt@kms_draw_crc@draw-method-xrgb8888-pwrite-untiled.html
* {igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@bc-hdmi-a1-hdmi-a2}:
- shard-glk: [FAIL][43] ([i915#79]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-glk8/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@bc-hdmi-a1-hdmi-a2.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-glk8/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@bc-hdmi-a1-hdmi-a2.html
* igt@kms_hdmi_inject@inject-audio:
- shard-tglb: [SKIP][45] ([i915#433]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-tglb8/igt@kms_hdmi_inject@inject-audio.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-tglb3/igt@kms_hdmi_inject@inject-audio.html
* igt@kms_psr@psr2_cursor_render:
- shard-iclb: [SKIP][47] ([fdo#109441]) -> [PASS][48] +1 similar issue
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-iclb6/igt@kms_psr@psr2_cursor_render.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-iclb2/igt@kms_psr@psr2_cursor_render.html
* igt@kms_vblank@pipe-b-ts-continuation-suspend:
- shard-apl: [DMESG-WARN][49] ([i915#180]) -> [PASS][50] +2 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-apl6/igt@kms_vblank@pipe-b-ts-continuation-suspend.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-apl1/igt@kms_vblank@pipe-b-ts-continuation-suspend.html
#### Warnings ####
* igt@i915_pm_dc@dc6-dpms:
- shard-kbl: [FAIL][51] ([i915#454]) -> [FAIL][52] ([i915#454] / [i915#93] / [i915#95])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl2/igt@i915_pm_dc@dc6-dpms.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl4/igt@i915_pm_dc@dc6-dpms.html
* igt@i915_pm_rpm@modeset-pc8-residency-stress:
- shard-snb: [SKIP][53] ([fdo#109271]) -> [INCOMPLETE][54] ([i915#82])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-snb6/igt@i915_pm_rpm@modeset-pc8-residency-stress.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-snb4/igt@i915_pm_rpm@modeset-pc8-residency-stress.html
* igt@kms_content_protection@atomic:
- shard-apl: [TIMEOUT][55] ([i915#1319]) -> [FAIL][56] ([fdo#110321] / [fdo#110336]) +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-apl2/igt@kms_content_protection@atomic.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-apl1/igt@kms_content_protection@atomic.html
* igt@kms_content_protection@uevent:
- shard-kbl: [FAIL][57] ([i915#357] / [i915#93] / [i915#95]) -> [FAIL][58] ([i915#357])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl6/igt@kms_content_protection@uevent.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl3/igt@kms_content_protection@uevent.html
- shard-apl: [FAIL][59] ([i915#357] / [i915#95]) -> [FAIL][60] ([i915#357])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-apl6/igt@kms_content_protection@uevent.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-apl3/igt@kms_content_protection@uevent.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-apl: [FAIL][61] ([i915#1121] / [i915#95]) -> [FAIL][62] ([i915#1525])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-apl3/igt@kms_fbcon_fbt@fbc-suspend.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-apl8/igt@kms_fbcon_fbt@fbc-suspend.html
- shard-kbl: [FAIL][63] ([i915#1121] / [i915#93] / [i915#95]) -> [FAIL][64] ([i915#64])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8485/shard-kbl6/igt@kms_fbcon_fbt@fbc-suspend.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/shard-kbl2/igt@kms_fbcon_fbt@fbc-suspend.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#1121]: https://gitlab.freedesktop.org/drm/intel/issues/1121
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1525]: https://gitlab.freedesktop.org/drm/intel/issues/1525
[i915#1528]: https://gitlab.freedesktop.org/drm/intel/issues/1528
[i915#1559]: https://gitlab.freedesktop.org/drm/intel/issues/1559
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#1755]: https://gitlab.freedesktop.org/drm/intel/issues/1755
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#357]: https://gitlab.freedesktop.org/drm/intel/issues/357
[i915#433]: https://gitlab.freedesktop.org/drm/intel/issues/433
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456
[i915#52]: https://gitlab.freedesktop.org/drm/intel/issues/52
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#64]: https://gitlab.freedesktop.org/drm/intel/issues/64
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#72]: https://gitlab.freedesktop.org/drm/intel/issues/72
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 8)
------------------------------
Missing (3): pig-skl-6260u pig-glk-j5005 pig-icl-1065g7
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5654 -> IGTPW_4569
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_8485: 0c6c45b4587580b4b7b2247d201a3b0f7af4b7f6 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4569: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/index.html
IGT_5654: 5637a466a0b09535517751608f5525a8b468a76b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4569/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 5+ messages in thread
* [igt-dev] ✗ GitLab.Pipeline: failure for i915/gem_exec_balancer: Force timeslicing of the virtual request
2020-05-14 11:29 ` [igt-dev] " Chris Wilson
` (2 preceding siblings ...)
(?)
@ 2020-05-15 11:44 ` Patchwork
-1 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2020-05-15 11:44 UTC (permalink / raw)
To: Chris Wilson; +Cc: igt-dev
== Series Details ==
Series: i915/gem_exec_balancer: Force timeslicing of the virtual request
URL : https://patchwork.freedesktop.org/series/77261/
State : failure
== Summary ==
ERROR! This series introduces new undocumented tests:
gem_exec_balancer@sliced
Can you document them as per the requirement in the [CONTRIBUTING.md]?
[Documentation] has more details on how to do this.
Here are few examples:
https://gitlab.freedesktop.org/drm/igt-gpu-tools/commit/0316695d03aa46108296b27f3982ec93200c7a6e
https://gitlab.freedesktop.org/drm/igt-gpu-tools/commit/443cc658e1e6b492ee17bf4f4d891029eb7a205d
Thanks in advance!
[CONTRIBUTING.md]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/blob/master/CONTRIBUTING.md#L19
[Documentation]: https://drm.pages.freedesktop.org/igt-gpu-tools/igt-gpu-tools-Core.html#igt-describe
Other than that, pipeline status: SUCCESS.
see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/146721 for the overview.
== Logs ==
For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/146721
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-05-15 11:44 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-14 11:29 [Intel-gfx] [PATCH i-g-t] i915/gem_exec_balancer: Force timeslicing of the virtual request Chris Wilson
2020-05-14 11:29 ` [igt-dev] " Chris Wilson
2020-05-14 12:47 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-05-14 17:06 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-05-15 11:44 ` [igt-dev] ✗ GitLab.Pipeline: " 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.