tests/i915/gem_exec_create: Added __for_each_physical_engine to utilize all available engines.
PATCH 1/1 tests/i915/gem_exec_create: Added __for_each_physical_engine to utilize all available engines.
From: saigowth <[email protected]>
Replaced the legacy for_each_engine* defines with the ones implemented in the gem_engine_topology library.
--- tests/i915/gem_exec_create.c | 29 ++++++++++++++++------------- 1 file changed, 16 insertions(+), 13 deletions(-)
tests/i915/gem_exec_create.c +16 -13
@@ -58,14 +58,15 @@ static double elapsed(const struct timespec *start, const struct timespec *end)static void all (int fd,unsigned flags,int timeout,int ncpus) { +const struct intel_execution_engine2 *e;const uint32_t bbe =MI_BATCH_BUFFER_END ;struct drm_i915_gem_execbuffer2 execbuf;struct drm_i915_gem_exec_object2 obj;unsigned engines[16 ], nengine; nengine =0 ; -for_each_physical_engine (e, fd) - engines[nengine++] =eb_ring (e); +__for_each_physical_engine (fd, e) + engines[nengine++] = e->flags;igt_require (nengine);memset (&obj,0 ,sizeof (obj));
@@ -86,38 +87,40 @@ static void all(int fd, unsigned flags, int timeout, int ncpus)intel_detect_and_clear_missed_interrupts (fd); igt_fork(child, ncpus) { +int i915;struct timespec start, now;unsigned long count;double time; - + i915 =gem_reopen_driver (fd); +gem_context_copy_engines (fd,0 , i915,0 ); count =0 ;clock_gettime (CLOCK_MONOTONIC , &start);do {for (int loop =0 ; loop <1024 ; loop++) {for (int n =0 ; n < nengine; n++) { - obj.handle =gem_create (fd,4096 ); -gem_write (fd, obj.handle,0 , &bbe,sizeof (bbe)); + obj.handle =gem_create (i915,4096 ); +gem_write (i915, obj.handle,0 , &bbe,sizeof (bbe)); execbuf.flags &= ~ENGINE_FLAGS ; execbuf.flags |= engines[n]; -gem_execbuf (fd, &execbuf); +gem_execbuf (i915, &execbuf);if (flags &LEAK ) -gem_madvise (fd, obj.handle,I915_MADV_DONTNEED ); +gem_madvise (i915, obj.handle,I915_MADV_DONTNEED );else -gem_close (fd, obj.handle); +gem_close (i915, obj.handle); } } count += nengine *1024 ;clock_gettime (CLOCK_MONOTONIC , &now); }while (elapsed (&start, &now) < timeout);/* Hang detection ~120s */ - obj.handle =gem_create (fd,4096 ); -gem_write (fd, obj.handle,0 , &bbe,sizeof (bbe)); + obj.handle =gem_create (i915,4096 ); +gem_write (i915, obj.handle,0 , &bbe,sizeof (bbe));for (int n =0 ; n < nengine; n++) { execbuf.flags &= ~ENGINE_FLAGS ; execbuf.flags |= engines[n]; -gem_execbuf (fd, &execbuf); +gem_execbuf (i915, &execbuf); } -gem_sync (fd, obj.handle); -gem_close (fd, obj.handle); +gem_sync (i915, obj.handle); +gem_close (i915, obj.handle);clock_gettime (CLOCK_MONOTONIC , &now); time =elapsed (&start, &now) / count;
Signature · 6 lines
2.25.0 _______________________________________________ igt-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/igt-dev
Patchwork
CI[igt-dev] ✓ Fi.CI.BAT: success for tests/i915/gem_exec_create: Added __for_each_physical_engine to utilize all available engines.
== Series Details ==
== Series Details ==
Series: tests/i915/gem_exec_create: Added __for_each_physical_engine to utilize all available engines.
URL : https://patchwork.freedesktop.org/series/73568/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7960 -> IGTPW_4177
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/index.html
Known issues
------------
Here are the changes found in IGTPW_4177 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_module_load@reload:
- fi-skl-6770hq: [PASS][1] -> [DMESG-WARN][2] ([i915#92]) +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/fi-skl-6770hq/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/fi-skl-6770hq/igt@[email protected]
* igt@kms_pipe_crc_basic@read-crc-pipe-a-frame-sequence:
- fi-skl-6770hq: [PASS][3] -> [SKIP][4] ([fdo#109271]) +4 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/fi-skl-6770hq/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/fi-skl-6770hq/igt@[email protected]
* igt@kms_pipe_crc_basic@read-crc-pipe-c:
- fi-skl-6770hq: [PASS][5] -> [DMESG-WARN][6] ([i915#106])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/fi-skl-6770hq/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/fi-skl-6770hq/igt@[email protected]
#### Possible fixes ####
* igt@gem_close_race@basic-threads:
- fi-byt-n2820: [INCOMPLETE][7] ([i915#45]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/fi-byt-n2820/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/fi-byt-n2820/igt@[email protected]
* igt@i915_selftest@live_blt:
- fi-hsw-4770r: [DMESG-FAIL][9] ([i915#553] / [i915#725]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/fi-hsw-4770r/igt@i915_selftest@live_blt.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/fi-hsw-4770r/igt@i915_selftest@live_blt.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#106]: https://gitlab.freedesktop.org/drm/intel/issues/106
[i915#1233]: https://gitlab.freedesktop.org/drm/intel/issues/1233
[i915#45]: https://gitlab.freedesktop.org/drm/intel/issues/45
[i915#553]: https://gitlab.freedesktop.org/drm/intel/issues/553
[i915#725]: https://gitlab.freedesktop.org/drm/intel/issues/725
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
Participating hosts (46 -> 47)
------------------------------
Additional (7): fi-kbl-soraka fi-hsw-peppy fi-snb-2520m fi-gdg-551 fi-cfl-8109u fi-kbl-7560u fi-bsw-nick
Missing (6): fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5447 -> IGTPW_4177
CI-20190529: 20190529
CI_DRM_7960: b86443a3c1d1b32a03f381c9198eed9243f06d18 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4177: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/index.html
IGT_5447: 8d6b2500e44d3dc78b5eac8798f0de42f2ff9014 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Patchwork
CI[igt-dev] ✓ Fi.CI.IGT: success for tests/i915/gem_exec_create: Added __for_each_physical_engine to utilize all available engines.
In reply to sai gowtham== Series Details ==
== Series Details ==
Series: tests/i915/gem_exec_create: Added __for_each_physical_engine to utilize all available engines.
URL : https://patchwork.freedesktop.org/series/73568/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7960_full -> IGTPW_4177_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_4177_full:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@gem_exec_whisper@basic-fds-forked}:
- shard-tglb: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-tglb8/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-tglb7/igt@[email protected]
Known issues
------------
Here are the changes found in IGTPW_4177_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* 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_7960/shard-iclb1/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb5/igt@[email protected]
* igt@gem_exec_parallel@vcs1-fds:
- shard-iclb: [PASS][5] -> [SKIP][6] ([fdo#112080]) +10 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb6/igt@[email protected]
* igt@gem_exec_schedule@preempt-other-bsd:
- shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#112146]) +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb8/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb1/igt@[email protected]
* igt@gem_exec_schedule@preempt-queue-bsd1:
- shard-iclb: [PASS][9] -> [SKIP][10] ([fdo#109276]) +14 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb2/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb5/igt@[email protected]
* igt@gem_mmap_gtt@fault-concurrent:
- shard-snb: [PASS][11] -> [DMESG-WARN][12] ([i915#478])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-snb4/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-snb2/igt@[email protected]
* igt@gem_softpin@noreloc-s3:
- shard-kbl: [PASS][13] -> [DMESG-WARN][14] ([i915#180]) +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-kbl4/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-kbl1/igt@[email protected]
* igt@gen7_exec_parse@basic-offset:
- shard-hsw: [PASS][15] -> [FAIL][16] ([i915#694])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-hsw8/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-hsw2/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-glk: [PASS][17] -> [INCOMPLETE][18] ([i915#58] / [k.org#198133])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-glk2/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-glk2/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [PASS][19] -> [FAIL][20] ([i915#454])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb1/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb2/igt@[email protected]
* igt@kms_big_fb@x-tiled-8bpp-rotate-180:
- shard-hsw: [PASS][21] -> [FAIL][22] ([i915#969])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-hsw7/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-hsw2/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-256x256-random:
- shard-apl: [PASS][23] -> [FAIL][24] ([i915#54])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-apl1/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-apl3/igt@[email protected]
* igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy:
- shard-glk: [PASS][25] -> [FAIL][26] ([i915#72])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-glk8/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-glk6/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank:
- shard-glk: [PASS][27] -> [FAIL][28] ([i915#79])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-glk8/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-glk1/igt@[email protected]
* igt@kms_flip@plain-flip-ts-check-interruptible:
- shard-apl: [PASS][29] -> [FAIL][30] ([i915#34])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-apl3/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-apl7/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
- shard-apl: [PASS][31] -> [DMESG-WARN][32] ([i915#180])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-apl6/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-apl3/igt@[email protected]
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [PASS][33] -> [SKIP][34] ([fdo#109441]) +2 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb5/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@perf@gen12-mi-rpc:
- shard-tglb: [PASS][35] -> [TIMEOUT][36] ([fdo#112271] / [i915#1085])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-tglb1/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-tglb5/igt@[email protected]
#### Possible fixes ####
* igt@gem_ctx_shared@exec-single-timeline-bsd:
- shard-iclb: [SKIP][37] ([fdo#110841]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb2/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb5/igt@[email protected]
* igt@gem_exec_schedule@in-order-bsd:
- shard-iclb: [SKIP][39] ([fdo#112146]) -> [PASS][40] +4 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb1/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb6/igt@[email protected]
* igt@gem_exec_schedule@pi-shared-iova-bsd:
- shard-iclb: [SKIP][41] ([i915#677]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb1/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb3/igt@[email protected]
* igt@gem_partial_pwrite_pread@writes-after-reads-snoop:
- shard-hsw: [FAIL][43] ([i915#694]) -> [PASS][44] +1 similar issue
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-hsw6/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-hsw6/igt@[email protected]
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-glk: [FAIL][45] ([i915#644]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-glk2/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-glk6/igt@[email protected]
* igt@gem_softpin@noreloc-s3:
- shard-iclb: [INCOMPLETE][47] ([fdo#109100]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb3/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb8/igt@[email protected]
* igt@i915_selftest@live_gt_heartbeat:
- shard-apl: [DMESG-FAIL][49] ([i915#541]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-apl2/igt@i915_selftest@live_gt_heartbeat.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-apl3/igt@i915_selftest@live_gt_heartbeat.html
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [DMESG-WARN][51] ([i915#180]) -> [PASS][52] +4 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-kbl7/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-kbl6/igt@[email protected]
* igt@kms_cursor_legacy@cursor-vs-flip-toggle:
- shard-hsw: [FAIL][53] ([i915#57]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-hsw8/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-hsw5/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-glk: [FAIL][55] ([i915#79]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-glk1/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-glk1/igt@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-apl: [DMESG-WARN][57] ([i915#180]) -> [PASS][58] +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-apl4/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-apl7/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite:
- shard-apl: [FAIL][59] ([i915#49]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-apl6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-apl3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite.html
- shard-kbl: [FAIL][61] ([i915#49]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-kbl6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-kbl2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-pwrite.html
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [SKIP][63] ([fdo#109441]) -> [PASS][64] +2 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb4/igt@kms_psr@psr2_primary_page_flip.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][65] ([i915#31]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-apl8/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-apl7/igt@[email protected]
* igt@perf_pmu@cpu-hotplug:
- shard-hsw: [INCOMPLETE][67] ([i915#1176] / [i915#61]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-hsw6/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-hsw1/igt@[email protected]
* igt@perf_pmu@init-busy-vcs1:
- shard-iclb: [SKIP][69] ([fdo#112080]) -> [PASS][70] +8 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb7/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb2/igt@[email protected]
* igt@prime_busy@hang-bsd2:
- shard-iclb: [SKIP][71] ([fdo#109276]) -> [PASS][72] +21 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb6/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb2/igt@[email protected]
#### Warnings ####
* igt@gem_ctx_isolation@vcs1-nonpriv:
- shard-iclb: [FAIL][73] ([IGT#28]) -> [SKIP][74] ([fdo#112080])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-iclb1/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-iclb8/igt@[email protected]
* igt@gem_ctx_shared@q-promotion-bsd:
- shard-hsw: [SKIP][75] ([fdo#109271]) -> [INCOMPLETE][76] ([i915#61])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-hsw8/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-hsw7/igt@[email protected]
* igt@gem_tiled_blits@interruptible:
- shard-hsw: [FAIL][77] ([i915#694]) -> [FAIL][78] ([i915#818])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-hsw7/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-hsw6/igt@[email protected]
* igt@gem_tiled_blits@normal:
- shard-hsw: [FAIL][79] ([i915#818]) -> [FAIL][80] ([i915#694])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7960/shard-hsw2/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/shard-hsw6/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#28]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/28
[fdo#109100]: https://bugs.freedesktop.org/show_bug.cgi?id=109100
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841
[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
[fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271
[i915#1085]: https://gitlab.freedesktop.org/drm/intel/issues/1085
[i915#1176]: https://gitlab.freedesktop.org/drm/intel/issues/1176
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#34]: https://gitlab.freedesktop.org/drm/intel/issues/34
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#478]: https://gitlab.freedesktop.org/drm/intel/issues/478
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#541]: https://gitlab.freedesktop.org/drm/intel/issues/541
[i915#57]: https://gitlab.freedesktop.org/drm/intel/issues/57
[i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
[i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61
[i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644
[i915#677]: https://gitlab.freedesktop.org/drm/intel/issues/677
[i915#694]: https://gitlab.freedesktop.org/drm/intel/issues/694
[i915#72]: https://gitlab.freedesktop.org/drm/intel/issues/72
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#818]: https://gitlab.freedesktop.org/drm/intel/issues/818
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[i915#969]: https://gitlab.freedesktop.org/drm/intel/issues/969
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (10 -> 8)
------------------------------
Missing (2): pig-skl-6260u pig-glk-j5005
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5447 -> IGTPW_4177
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_7960: b86443a3c1d1b32a03f381c9198eed9243f06d18 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_4177: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4177/index.html
IGT_5447: 8d6b2500e44d3dc78b5eac8798f0de42f2ff9014 @ 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_4177/index.html
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 35 lines · sai gowtham
From: saigowth <[email protected]>
Replaced the legacy for_each_engine* defines with the ones implemented in the
gem_engine_topologylibrary.Cc Dec Katarzyna <[email protected]>Cc Ursulin Tvrtko <[email protected]>Signed-off-by sai gowtham <[email protected]>--- tests/i915/gem_exec_create.c | 29 ++++++++++++++++------------- 1 file changed, 16 insertions(+), 13 deletions(-)tests/i915/gem_exec_create.c +3
-2@@ -58,14 +58,15 @@ static double elapsed(const struct timespec *start, const struct timespec *end)static void all (int fd,unsigned flags,int timeout,int ncpus) { +const struct intel_execution_engine2 *e;const uint32_t bbe =MI_BATCH_BUFFER_END ;struct drm_i915_gem_execbuffer2 execbuf;struct drm_i915_gem_exec_object2 obj;unsigned engines[16 ], nengine; nengine =0 ; -for_each_physical_engine (e, fd) - engines[nengine++] =eb_ring (e); +__for_each_physical_engine (fd, e) + engines[nengine++] = e->flags;igt_require (nengine);memset (&obj,0 ,sizeof (obj));
tests/i915/gem_exec_create.c static void all(int fd, unsigned flags, int timeout, int ncpus) · line 95
Quoted 10 lines
tests/i915/gem_exec_create.c +3
-1@@ -86,38 +87,40 @@ static void all(int fd, unsigned flags, int timeout, int ncpus)intel_detect_and_clear_missed_interrupts (fd); igt_fork(child, ncpus) { +int i915;struct timespec start, now;unsigned long count;double time; - + i915 =gem_reopen_driver (fd); +gem_context_copy_engines (fd,0 , i915,0 );
Why do we need to reopen device and copy it's context? What's the purpose? Kasia
Quoted 48 lines
tests/i915/gem_exec_create.c +10
-10count =0 ;clock_gettime (CLOCK_MONOTONIC , &start);do {for (int loop =0 ; loop <1024 ; loop++) {for (int n =0 ; n < nengine; n++) { - obj.handle =gem_create (fd,4096 ); -gem_write (fd, obj.handle,0 , &bbe,sizeof (bbe)); + obj.handle =gem_create (i915,4096 ); +gem_write (i915, obj.handle,0 , &bbe,sizeof (bbe)); execbuf.flags &= ~ENGINE_FLAGS ; execbuf.flags |= engines[n]; -gem_execbuf (fd, &execbuf); +gem_execbuf (i915, &execbuf);if (flags &LEAK ) -gem_madvise (fd, obj.handle,I915_MADV_DONTNEED ); +gem_madvise (i915, obj.handle,I915_MADV_DONTNEED );else -gem_close (fd, obj.handle); +gem_close (i915, obj.handle); } } count += nengine *1024 ;clock_gettime (CLOCK_MONOTONIC , &now); }while (elapsed (&start, &now) < timeout);/* Hang detection ~120s */ - obj.handle =gem_create (fd,4096 ); -gem_write (fd, obj.handle,0 , &bbe,sizeof (bbe)); + obj.handle =gem_create (i915,4096 ); +gem_write (i915, obj.handle,0 , &bbe,sizeof (bbe));for (int n =0 ; n < nengine; n++) { execbuf.flags &= ~ENGINE_FLAGS ; execbuf.flags |= engines[n]; -gem_execbuf (fd, &execbuf); +gem_execbuf (i915, &execbuf); } -gem_sync (fd, obj.handle); -gem_close (fd, obj.handle); +gem_sync (i915, obj.handle); +gem_close (i915, obj.handle);clock_gettime (CLOCK_MONOTONIC , &now); time =elapsed (&start, &now) / count;Signature · 6 lines
2.25.0 _______________________________________________ igt-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
After fork we need to transfer the engine map from parent fd default context. (gem_context_copy_engines)
Also, since we have __for_each_physical_engine in the top level igt_fixture, I think _all_ subtests run with default ctx engine map. So all which submit to one from either all_engines or ppgtt_engines need to make sure engine maps are aligned.
it was suggested by tvrtko in one of the patch: https://patchwork.freedesktop.org/patch/351622/?series=72889&rev=1
Thanks,
Gowtham
-----Original Message-----
From: Dec, Katarzyna <[email protected]>
Sent: Thursday, March 5, 2020 6:13 PM
To: Ch, Sai Gowtham <[email protected]>; [email protected]
Subject: Re: [igt-dev] [PATCH] [PATCH i-g-t]tests/i915/gem_exec_create: Added __for_each_physical_engine to utilize all available engines.
Quoted 36 lines · sai gowtham
From: saigowth <[email protected]>
Replaced the legacy for_each_engine* defines with the ones implemented in the
gem_engine_topologylibrary.Cc Dec Katarzyna <[email protected]>Cc Ursulin Tvrtko <[email protected]>Signed-off-by sai gowtham <[email protected]>--- tests/i915/gem_exec_create.c | 29 ++++++++++++++++------------- 1 file changed, 16 insertions(+), 13 deletions(-)(quoted diff) +0
-0
b/tests/i915/gem_exec_create.cindex102a161d..c70572af100644tests/i915/gem_exec_create.c +3
-2@@ -58,14 +58,15 @@ static double elapsed(const struct timespec *start, const struct timespec *end)static void all (int fd,unsigned flags,int timeout,int ncpus) { +const struct intel_execution_engine2 *e;const uint32_t bbe =MI_BATCH_BUFFER_END ;struct drm_i915_gem_execbuffer2 execbuf;struct drm_i915_gem_exec_object2 obj;unsigned engines[16 ], nengine; nengine =0 ; -for_each_physical_engine (e, fd) - engines[nengine++] =eb_ring (e); +__for_each_physical_engine (fd, e) + engines[nengine++] = e->flags;igt_require (nengine);memset (&obj,0 ,sizeof (obj));@@ -86,38 +87,40 @@ static void all(int fd, unsigned flags, int timeout, int ncpus)
tests/i915/gem_exec_create.c static void all(int fd, unsigned flags, int · line 96
Quoted 10 lines
tests/i915/gem_exec_create.c +3
-1intel_detect_and_clear_missed_interrupts (fd); igt_fork(child, ncpus) { +int i915;struct timespec start, now;unsigned long count;double time; - + i915 =gem_reopen_driver (fd); +gem_context_copy_engines (fd,0 , i915,0 );
Why do we need to reopen device and copy it's context? What's the purpose? Kasia
Quoted 44 lines
tests/i915/gem_exec_create.c +10
-10count =0 ;clock_gettime (CLOCK_MONOTONIC , &start);do {for (int loop =0 ; loop <1024 ; loop++) {for (int n =0 ; n < nengine; n++) { - obj.handle =gem_create (fd,4096 ); -gem_write (fd, obj.handle,0 , &bbe,sizeof (bbe)); + obj.handle =gem_create (i915,4096 ); +gem_write (i915, obj.handle,0 , &bbe,sizeof (bbe)); execbuf.flags &= ~ENGINE_FLAGS ; execbuf.flags |= engines[n]; -gem_execbuf (fd, &execbuf); +gem_execbuf (i915, &execbuf);if (flags &LEAK ) -gem_madvise (fd, obj.handle,I915_MADV_DONTNEED ); +gem_madvise (i915, obj.handle,I915_MADV_DONTNEED );else -gem_close (fd, obj.handle); +gem_close (i915, obj.handle); } } count += nengine *1024 ;clock_gettime (CLOCK_MONOTONIC , &now); }while (elapsed (&start, &now) < timeout);/* Hang detection ~120s */ - obj.handle =gem_create (fd,4096 ); -gem_write (fd, obj.handle,0 , &bbe,sizeof (bbe)); + obj.handle =gem_create (i915,4096 ); +gem_write (i915, obj.handle,0 , &bbe,sizeof (bbe));for (int n =0 ; n < nengine; n++) { execbuf.flags &= ~ENGINE_FLAGS ; execbuf.flags |= engines[n]; -gem_execbuf (fd, &execbuf); +gem_execbuf (i915, &execbuf); } -gem_sync (fd, obj.handle); -gem_close (fd, obj.handle); +gem_sync (i915, obj.handle); +gem_close (i915, obj.handle);clock_gettime (CLOCK_MONOTONIC , &now);time =
elapsed(&start, &now)/ count;
--
2.25.0
Quoted 4 lines
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 9 lines · Sai Gowtham
After fork we need to transfer the engine map from parent fd default context. (
gem_context_copy_engines)Also, since we have
__for_each_physical_enginein the top leveligt_fixture, I think _all_ subtests run with default ctx engine map. So all which submit to one from eitherall_enginesorppgtt_enginesneed to make sure engine maps are aligned.it was suggested by tvrtko in one of the patch: https://patchwork.freedesktop.org/patch/351622/?series=72889&rev=1
I was sadly wrong there, it is not required to reopen and copy engines after fork. So __for_each_physical_engine should do it in this case.
Regards,
Tvrtko
P.S. You could also dynamically size (allocate) the engines array while at it to be more in line with the other recent cleanups.
Hm.. actually, do we even need the array? Andi, __for_each_physical_engine will always create engine map with consecutive e->flags integers, right? There can be no holes?
Quoted 100 lines
-----Original Message-----
From: Dec, Katarzyna <[email protected]>
Sent: Thursday, March 5, 2020 6:13 PM
To: Ch, Sai Gowtham <[email protected]>; [email protected]
Subject: Re: [igt-dev] [PATCH] [PATCH i-g-t]tests/i915/gem_exec_create: Added__for_each_physical_engineto utilize all available engines.Quoted 36 lines · sai gowtham
From: saigowth <[email protected]>
Replaced the legacy for_each_engine* defines with the ones implemented in the
gem_engine_topologylibrary.Cc Dec Katarzyna <[email protected]>Cc Ursulin Tvrtko <[email protected]>Signed-off-by sai gowtham <[email protected]>--- tests/i915/gem_exec_create.c | 29 ++++++++++++++++------------- 1 file changed, 16 insertions(+), 13 deletions(-)(quoted diff) +0
-0
b/tests/i915/gem_exec_create.cindex102a161d..c70572af100644tests/i915/gem_exec_create.c +3
-2@@ -58,14 +58,15 @@ static double elapsed(const struct timespec *start, const struct timespec *end)static void all (int fd,unsigned flags,int timeout,int ncpus) { +const struct intel_execution_engine2 *e;const uint32_t bbe =MI_BATCH_BUFFER_END ;struct drm_i915_gem_execbuffer2 execbuf;struct drm_i915_gem_exec_object2 obj;unsigned engines[16 ], nengine; nengine =0 ; -for_each_physical_engine (e, fd) - engines[nengine++] =eb_ring (e); +__for_each_physical_engine (fd, e) + engines[nengine++] = e->flags;igt_require (nengine);memset (&obj,0 ,sizeof (obj));@@ -86,38 +87,40 @@ static void all(int fd, unsigned flags, int timeout, int ncpus)tests/i915/gem_exec_create.c static void all(int fd, unsigned flags, int · line 96
Quoted 10 lines
tests/i915/gem_exec_create.c +3
-1intel_detect_and_clear_missed_interrupts (fd); igt_fork(child, ncpus) { +int i915;struct timespec start, now;unsigned long count;double time; - + i915 =gem_reopen_driver (fd); +gem_context_copy_engines (fd,0 , i915,0 );Why do we need to reopen device and copy it's context? What's the purpose? Kasia
Quoted 44 lines
tests/i915/gem_exec_create.c +10
-10count =0 ;clock_gettime (CLOCK_MONOTONIC , &start);do {for (int loop =0 ; loop <1024 ; loop++) {for (int n =0 ; n < nengine; n++) { - obj.handle =gem_create (fd,4096 ); -gem_write (fd, obj.handle,0 , &bbe,sizeof (bbe)); + obj.handle =gem_create (i915,4096 ); +gem_write (i915, obj.handle,0 , &bbe,sizeof (bbe)); execbuf.flags &= ~ENGINE_FLAGS ; execbuf.flags |= engines[n]; -gem_execbuf (fd, &execbuf); +gem_execbuf (i915, &execbuf);if (flags &LEAK ) -gem_madvise (fd, obj.handle,I915_MADV_DONTNEED ); +gem_madvise (i915, obj.handle,I915_MADV_DONTNEED );else -gem_close (fd, obj.handle); +gem_close (i915, obj.handle); } } count += nengine *1024 ;clock_gettime (CLOCK_MONOTONIC , &now); }while (elapsed (&start, &now) < timeout);/* Hang detection ~120s */ - obj.handle =gem_create (fd,4096 ); -gem_write (fd, obj.handle,0 , &bbe,sizeof (bbe)); + obj.handle =gem_create (i915,4096 ); +gem_write (i915, obj.handle,0 , &bbe,sizeof (bbe));for (int n =0 ; n < nengine; n++) { execbuf.flags &= ~ENGINE_FLAGS ; execbuf.flags |= engines[n]; -gem_execbuf (fd, &execbuf); +gem_execbuf (i915, &execbuf); } -gem_sync (fd, obj.handle); -gem_close (fd, obj.handle); +gem_sync (i915, obj.handle); +gem_close (i915, obj.handle);clock_gettime (CLOCK_MONOTONIC , &now);time =
elapsed(&start, &now)/ count;
--
2.25.0
Quoted 9 lines
Quoted 4 lines
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Hi Tvrtko,
Quoted 15 lines
Quoted 9 lines
After fork we need to transfer the engine map from parent fd default context. (
gem_context_copy_engines)Also, since we have
__for_each_physical_enginein the top leveligt_fixture, I think _all_ subtests run with default ctx engine map. So all which submit to one from eitherall_enginesorppgtt_enginesneed to make sure engine maps are aligned.it was suggested by tvrtko in one of the patch: https://patchwork.freedesktop.org/patch/351622/?series=72889&rev=1
I was sadly wrong there, it is not required to reopen and copy engines after fork. So
__for_each_physical_engineshould do it in this case.Regards,
Quoted 8 lines
Tvrtko
P.S. You could also dynamically size (allocate) the engines array while at it to be more in line with the other recent cleanups.Hm.. actually, do we even need the array? Andi,
__for_each_physical_enginewill always create engine map with consecutivee->flagsintegers, right? There can be no holes?
yes, you are right, we do not need in this case the array and there shouldn't be holes, indeed.
Andi
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 22 lines · Andi Shyti
Hi Tvrtko,
Quoted 20 lines
Quoted 9 lines
After fork we need to transfer the engine map from parent fd default context. (
gem_context_copy_engines)Also, since we have
__for_each_physical_enginein the top leveligt_fixture, I think _all_ subtests run with default ctx engine map. So all which submit to one from eitherall_enginesorppgtt_enginesneed to make sure engine maps are aligned.it was suggested by tvrtko in one of the patch: https://patchwork.freedesktop.org/patch/351622/?series=72889&rev=1
I was sadly wrong there, it is not required to reopen and copy engines after fork. So
__for_each_physical_engineshould do it in this case.Regards,
Tvrtko
P.S. You could also dynamically size (allocate) the engines array while at it to be more in line with the other recent cleanups.
Quoted 6 lines
Quoted 3 lines
Hm.. actually, do we even need the array? Andi,
__for_each_physical_enginewill always create engine map with consecutivee->flagsintegers, right? There can be no holes?yes, you are right, we do not need in this case the array and there shouldn't be holes, indeed.
Then the question is whether it is a good idea to rely on this from tests or not? I can't imagine a scenario where IGT couldn't create a map with no holes but maybe my imagination is bad.
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Hi Andi,Tvrtko ,
Could you please suggest me which would be the best way ?
Thanks,
Gowtham
-----Original Message-----
From: Tvrtko Ursulin <[email protected]>
Sent: Friday, March 6, 2020 7:37 PM
To: Shyti, Andi <[email protected]>
Cc: Ch, Sai Gowtham <[email protected]>; Dec, Katarzyna <[email protected]>; [email protected]
Subject: Re: [igt-dev] [PATCH] [PATCH i-g-t]tests/i915/gem_exec_create: Added __for_each_physical_engine to utilize all available engines.
Quoted 23 lines · Andi Shyti
Hi Tvrtko,
Quoted 21 lines
Quoted 10 lines
After fork we need to transfer the engine map from parent fd default context. (
gem_context_copy_engines)Also, since we have
__for_each_physical_enginein the top leveligt_fixture, I think _all_ subtests run with default ctx engine map. So all which submit to one from eitherall_enginesorppgtt_enginesneed to make sure engine maps are aligned.it was suggested by tvrtko in one of the patch:
https://patchwork.freedesktop.org/patch/351622/?series=72889&rev=1I was sadly wrong there, it is not required to reopen and copy engines after fork. So
__for_each_physical_engineshould do it in this case.Regards,
Tvrtko
P.S. You could also dynamically size (allocate) the engines array while at it to be more in line with the other recent cleanups.
Quoted 6 lines
Quoted 3 lines
Hm.. actually, do we even need the array? Andi,
__for_each_physical_enginewill always create engine map with consecutivee->flagsintegers, right? There can be no holes?yes, you are right, we do not need in this case the array and there shouldn't be holes, indeed.
Then the question is whether it is a good idea to rely on this from tests or not? I can't imagine a scenario where IGT couldn't create a map with no holes but maybe my imagination is bad.
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Quoted 3 lines · Sai Gowtham
Hi Andi,Tvrtko ,
Could you please suggest me which would be the best way ?
No reopen after fork and no need for the engines array - just s/engines[i]/i/ in the child.
Regards,
Tvrtko
Quoted 39 lines
Thanks,
Gowtham-----Original Message-----
From: Tvrtko Ursulin <[email protected]>
Sent: Friday, March 6, 2020 7:37 PM
To: Shyti, Andi <[email protected]>
Cc: Ch, Sai Gowtham <[email protected]>; Dec, Katarzyna <[email protected]>; [email protected]
Subject: Re: [igt-dev] [PATCH] [PATCH i-g-t]tests/i915/gem_exec_create: Added__for_each_physical_engineto utilize all available engines.Quoted 27 lines · Andi Shyti
Hi Tvrtko,
Quoted 24 lines
Quoted 10 lines
After fork we need to transfer the engine map from parent fd default context. (
gem_context_copy_engines)Also, since we have
__for_each_physical_enginein the top leveligt_fixture, I think _all_ subtests run with default ctx engine map. So all which submit to one from eitherall_enginesorppgtt_enginesneed to make sure engine maps are aligned.it was suggested by tvrtko in one of the patch:
https://patchwork.freedesktop.org/patch/351622/?series=72889&rev=1I was sadly wrong there, it is not required to reopen and copy engines after fork. So
__for_each_physical_engineshould do it in this case.Regards,
Tvrtko
P.S. You could also dynamically size (allocate) the engines array while at it to be more in line with the other recent cleanups.Hm.. actually, do we even need the array? Andi,
__for_each_physical_enginewill always create engine map with consecutivee->flagsintegers, right? There can be no holes?
Quoted 10 lines
Quoted 2 lines
yes, you are right, we do not need in this case the array and there shouldn't be holes, indeed.
Then the question is whether it is a good idea to rely on this from tests or not? I can't imagine a scenario where IGT couldn't create a map with no holes but maybe my imagination is bad.
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev
Hi,
Quoted 1 line · sai gowtham
From: saigowth <[email protected]>
don't know if someone told you already, can you please use your real full name in the commit?
Thanks,
Andi
_______________________________________________
igt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/igt-dev