* [PATCH 1/2] drm/i915/tgl: the BCS engine supports relative MMIO @ 2019-10-09 23:04 Daniele Ceraolo Spurio 2019-10-09 23:04 ` [PATCH 2/2] drm/i915/tgl: simplify the lrc register list for !RCS Daniele Ceraolo Spurio ` (3 more replies) 0 siblings, 4 replies; 7+ messages in thread From: Daniele Ceraolo Spurio @ 2019-10-09 23:04 UTC (permalink / raw) To: intel-gfx The specs don't mention any specific HW limitation on the blitter and manual inspection shows that the HW does set the relative MMIO bit in the LRI of the blitter context image, so we can remove our limitations. Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: John Harrison <John.C.Harrison@Intel.com> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> --- drivers/gpu/drm/i915/gt/intel_lrc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c index 6db762c509b8..78a136c12385 100644 --- a/drivers/gpu/drm/i915/gt/intel_lrc.c +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c @@ -3448,7 +3448,7 @@ void intel_execlists_set_default_submission(struct intel_engine_cs *engine) engine->flags |= I915_ENGINE_HAS_PREEMPTION; } - if (engine->class != COPY_ENGINE_CLASS && INTEL_GEN(engine->i915) >= 12) + if (INTEL_GEN(engine->i915) >= 12) engine->flags |= I915_ENGINE_HAS_RELATIVE_MMIO; } -- 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] 7+ messages in thread
* [PATCH 2/2] drm/i915/tgl: simplify the lrc register list for !RCS 2019-10-09 23:04 [PATCH 1/2] drm/i915/tgl: the BCS engine supports relative MMIO Daniele Ceraolo Spurio @ 2019-10-09 23:04 ` Daniele Ceraolo Spurio 2019-10-10 9:03 ` Chris Wilson 2019-10-10 2:08 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/tgl: the BCS engine supports relative MMIO Patchwork ` (2 subsequent siblings) 3 siblings, 1 reply; 7+ messages in thread From: Daniele Ceraolo Spurio @ 2019-10-09 23:04 UTC (permalink / raw) To: intel-gfx There are small differences between the blitter and the video engines in the xcs context image (e.g. registers 0x200 and 0x204 only exist on the blitter). Since we never explicitly set a value for those register and given that we don't need to update the offsets in the lrc image when we change engine within the class for virtual engine because the HW can handle that, instead of having a separate define for the BCS we can just restrict the programming to the part we're interested in, which is common across the engines. Bspec: 45584 Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Cc: Stuart Summers <stuart.summers@intel.com> --- drivers/gpu/drm/i915/gt/intel_lrc.c | 66 ++++------------------------- 1 file changed, 8 insertions(+), 58 deletions(-) diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c index 78a136c12385..488a19ab908d 100644 --- a/drivers/gpu/drm/i915/gt/intel_lrc.c +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c @@ -669,64 +669,6 @@ static const u8 gen12_xcs_offsets[] = { REG16(0x274), REG16(0x270), - NOP(13), - LRI(2, POSTED), - REG16(0x200), - REG16(0x204), - - NOP(11), - LRI(50, POSTED), - REG16(0x588), - REG16(0x588), - REG16(0x588), - REG16(0x588), - REG16(0x588), - REG16(0x588), - REG(0x028), - REG(0x09c), - REG(0x0c0), - REG(0x178), - REG(0x17c), - REG16(0x358), - REG(0x170), - REG(0x150), - REG(0x154), - REG(0x158), - REG16(0x41c), - REG16(0x600), - REG16(0x604), - REG16(0x608), - REG16(0x60c), - REG16(0x610), - REG16(0x614), - REG16(0x618), - REG16(0x61c), - REG16(0x620), - REG16(0x624), - REG16(0x628), - REG16(0x62c), - REG16(0x630), - REG16(0x634), - REG16(0x638), - REG16(0x63c), - REG16(0x640), - REG16(0x644), - REG16(0x648), - REG16(0x64c), - REG16(0x650), - REG16(0x654), - REG16(0x658), - REG16(0x65c), - REG16(0x660), - REG16(0x664), - REG16(0x668), - REG16(0x66c), - REG16(0x670), - REG16(0x674), - REG16(0x678), - REG16(0x67c), - REG(0x068), - END(), }; @@ -857,6 +799,14 @@ static const u8 gen12_rcs_offsets[] = { static const u8 *reg_offsets(const struct intel_engine_cs *engine) { + /* + * the gen12+ lists only have the register we program in the default + * state because we don't need to update the offsets when using a + * virtual engine. + */ + GEM_BUG_ON(INTEL_GEN(engine->i915) >= 12 && + !intel_engine_has_relative_mmio(engine)); + if (engine->class == RENDER_CLASS) { if (INTEL_GEN(engine->i915) >= 12) return gen12_rcs_offsets; -- 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] 7+ messages in thread
* Re: [PATCH 2/2] drm/i915/tgl: simplify the lrc register list for !RCS 2019-10-09 23:04 ` [PATCH 2/2] drm/i915/tgl: simplify the lrc register list for !RCS Daniele Ceraolo Spurio @ 2019-10-10 9:03 ` Chris Wilson 0 siblings, 0 replies; 7+ messages in thread From: Chris Wilson @ 2019-10-10 9:03 UTC (permalink / raw) To: Daniele Ceraolo Spurio, intel-gfx Quoting Daniele Ceraolo Spurio (2019-10-10 00:04:24) > There are small differences between the blitter and the video engines in > the xcs context image (e.g. registers 0x200 and 0x204 only exist on the > blitter). Since we never explicitly set a value for those register and > given that we don't need to update the offsets in the lrc image when we > change engine within the class for virtual engine because the HW can > handle that, instead of having a separate define for the BCS we can > just restrict the programming to the part we're interested in, which is > common across the engines. Yeah, my thinking was to be as complete as possible so that if we needed to apply register updates, we could. It was also a fascinating insight into what was stored, I was planning on using it for doing isolation testing (albeit that's a bit chicken-and-egg). > Bspec: 45584 > Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> > Cc: Chris Wilson <chris@chris-wilson.co.uk> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> > Cc: Stuart Summers <stuart.summers@intel.com> No qualms about restricting ourselves to the bare essentials on the basis that the context image is meant to be relative-addressed. It did not improve stability of tgl-gem however. Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
* ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/tgl: the BCS engine supports relative MMIO 2019-10-09 23:04 [PATCH 1/2] drm/i915/tgl: the BCS engine supports relative MMIO Daniele Ceraolo Spurio 2019-10-09 23:04 ` [PATCH 2/2] drm/i915/tgl: simplify the lrc register list for !RCS Daniele Ceraolo Spurio @ 2019-10-10 2:08 ` Patchwork 2019-10-10 9:17 ` Chris Wilson 2019-10-10 8:49 ` [PATCH 1/2] " Chris Wilson 2019-10-10 12:04 ` ✓ Fi.CI.IGT: success for series starting with [1/2] " Patchwork 3 siblings, 1 reply; 7+ messages in thread From: Patchwork @ 2019-10-10 2:08 UTC (permalink / raw) To: Daniele Ceraolo Spurio; +Cc: intel-gfx == Series Details == Series: series starting with [1/2] drm/i915/tgl: the BCS engine supports relative MMIO URL : https://patchwork.freedesktop.org/series/67809/ State : success == Summary == CI Bug Log - changes from CI_DRM_7046 -> Patchwork_14739 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/index.html Known issues ------------ Here are the changes found in Patchwork_14739 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_flink_basic@bad-flink: - fi-icl-u3: [PASS][1] -> [DMESG-WARN][2] ([fdo#107724]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/fi-icl-u3/igt@gem_flink_basic@bad-flink.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/fi-icl-u3/igt@gem_flink_basic@bad-flink.html * igt@i915_selftest@live_hangcheck: - fi-icl-u2: [PASS][3] -> [INCOMPLETE][4] ([fdo#107713] / [fdo#108569]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/fi-icl-u2/igt@i915_selftest@live_hangcheck.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/fi-icl-u2/igt@i915_selftest@live_hangcheck.html #### Possible fixes #### * igt@gem_exec_suspend@basic: - {fi-tgl-u2}: [INCOMPLETE][5] ([fdo#111850]) -> [PASS][6] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/fi-tgl-u2/igt@gem_exec_suspend@basic.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/fi-tgl-u2/igt@gem_exec_suspend@basic.html * igt@gem_mmap_gtt@basic-read-write: - fi-icl-u3: [DMESG-WARN][7] ([fdo#107724]) -> [PASS][8] +1 similar issue [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/fi-icl-u3/igt@gem_mmap_gtt@basic-read-write.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/fi-icl-u3/igt@gem_mmap_gtt@basic-read-write.html * igt@i915_pm_rpm@module-reload: - {fi-icl-guc}: [INCOMPLETE][9] ([fdo#107713] / [fdo#108840]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/fi-icl-guc/igt@i915_pm_rpm@module-reload.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/fi-icl-guc/igt@i915_pm_rpm@module-reload.html * igt@i915_selftest@live_hugepages: - fi-elk-e7500: [INCOMPLETE][11] ([fdo#103989]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/fi-elk-e7500/igt@i915_selftest@live_hugepages.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/fi-elk-e7500/igt@i915_selftest@live_hugepages.html * igt@kms_chamelium@hdmi-hpd-fast: - fi-kbl-7500u: [FAIL][13] ([fdo#111045] / [fdo#111096]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a: - fi-kbl-r: [INCOMPLETE][15] -> [PASS][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/fi-kbl-r/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/fi-kbl-r/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#103989]: https://bugs.freedesktop.org/show_bug.cgi?id=103989 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569 [fdo#108840]: https://bugs.freedesktop.org/show_bug.cgi?id=108840 [fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045 [fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096 [fdo#111381]: https://bugs.freedesktop.org/show_bug.cgi?id=111381 [fdo#111850]: https://bugs.freedesktop.org/show_bug.cgi?id=111850 Participating hosts (53 -> 47) ------------------------------ Additional (1): fi-pnv-d510 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 * Linux: CI_DRM_7046 -> Patchwork_14739 CI-20190529: 20190529 CI_DRM_7046: 136f98967ad06da28fd795aa83be314c7b641c49 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5220: 1e38e32d721210a780198c8293a6b8c8e881df68 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_14739: 8c65f9a90680ed75a3a32a7d74b2118d22d06148 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 8c65f9a90680 drm/i915/tgl: simplify the lrc register list for !RCS f473ce3ccdf9 drm/i915/tgl: the BCS engine supports relative MMIO == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/tgl: the BCS engine supports relative MMIO 2019-10-10 2:08 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/tgl: the BCS engine supports relative MMIO Patchwork @ 2019-10-10 9:17 ` Chris Wilson 0 siblings, 0 replies; 7+ messages in thread From: Chris Wilson @ 2019-10-10 9:17 UTC (permalink / raw) To: Daniele Ceraolo Spurio, Patchwork; +Cc: intel-gfx Quoting Patchwork (2019-10-10 03:08:10) > == Series Details == > > Series: series starting with [1/2] drm/i915/tgl: the BCS engine supports relative MMIO > URL : https://patchwork.freedesktop.org/series/67809/ > State : success > > == Summary == > > CI Bug Log - changes from CI_DRM_7046 -> Patchwork_14739 > ==================================================== > > Summary > ------- > > **SUCCESS** > > No regressions found. > > External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/index.html That's enough (boots and live_lrc found no inconsistencies) convincing, pushed. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH 1/2] drm/i915/tgl: the BCS engine supports relative MMIO 2019-10-09 23:04 [PATCH 1/2] drm/i915/tgl: the BCS engine supports relative MMIO Daniele Ceraolo Spurio 2019-10-09 23:04 ` [PATCH 2/2] drm/i915/tgl: simplify the lrc register list for !RCS Daniele Ceraolo Spurio 2019-10-10 2:08 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/tgl: the BCS engine supports relative MMIO Patchwork @ 2019-10-10 8:49 ` Chris Wilson 2019-10-10 12:04 ` ✓ Fi.CI.IGT: success for series starting with [1/2] " Patchwork 3 siblings, 0 replies; 7+ messages in thread From: Chris Wilson @ 2019-10-10 8:49 UTC (permalink / raw) To: Daniele Ceraolo Spurio, intel-gfx Quoting Daniele Ceraolo Spurio (2019-10-10 00:04:23) > The specs don't mention any specific HW limitation on the blitter and > manual inspection shows that the HW does set the relative MMIO bit in > the LRI of the blitter context image, so we can remove our limitations. I concur, the HW itself sets the bit, so it can't be too harmful... > Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> > Cc: Chris Wilson <chris@chris-wilson.co.uk> > Cc: John Harrison <John.C.Harrison@Intel.com> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
* ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/tgl: the BCS engine supports relative MMIO 2019-10-09 23:04 [PATCH 1/2] drm/i915/tgl: the BCS engine supports relative MMIO Daniele Ceraolo Spurio ` (2 preceding siblings ...) 2019-10-10 8:49 ` [PATCH 1/2] " Chris Wilson @ 2019-10-10 12:04 ` Patchwork 3 siblings, 0 replies; 7+ messages in thread From: Patchwork @ 2019-10-10 12:04 UTC (permalink / raw) To: Daniele Ceraolo Spurio; +Cc: intel-gfx == Series Details == Series: series starting with [1/2] drm/i915/tgl: the BCS engine supports relative MMIO URL : https://patchwork.freedesktop.org/series/67809/ State : success == Summary == CI Bug Log - changes from CI_DRM_7046_full -> Patchwork_14739_full ==================================================== Summary ------- **SUCCESS** No regressions found. Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_14739_full: ### IGT changes ### #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * igt@kms_flip@blocking-wf_vblank: - {shard-tglb}: NOTRUN -> [INCOMPLETE][1] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-tglb5/igt@kms_flip@blocking-wf_vblank.html Known issues ------------ Here are the changes found in Patchwork_14739_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_ctx_switch@legacy-bsd1: - shard-iclb: [PASS][2] -> [INCOMPLETE][3] ([fdo#107713]) [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb8/igt@gem_ctx_switch@legacy-bsd1.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb1/igt@gem_ctx_switch@legacy-bsd1.html * igt@gem_exec_schedule@deep-render: - shard-apl: [PASS][4] -> [INCOMPLETE][5] ([fdo#103927]) +1 similar issue [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-apl1/igt@gem_exec_schedule@deep-render.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-apl7/igt@gem_exec_schedule@deep-render.html * igt@gem_exec_schedule@promotion-bsd1: - shard-iclb: [PASS][6] -> [SKIP][7] ([fdo#109276]) +13 similar issues [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb2/igt@gem_exec_schedule@promotion-bsd1.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb6/igt@gem_exec_schedule@promotion-bsd1.html * igt@gem_exec_schedule@reorder-wide-bsd: - shard-iclb: [PASS][8] -> [SKIP][9] ([fdo#111325]) +3 similar issues [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb7/igt@gem_exec_schedule@reorder-wide-bsd.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb4/igt@gem_exec_schedule@reorder-wide-bsd.html * igt@gem_softpin@noreloc-s3: - shard-skl: [PASS][10] -> [INCOMPLETE][11] ([fdo#104108]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-skl4/igt@gem_softpin@noreloc-s3.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-skl8/igt@gem_softpin@noreloc-s3.html * igt@gem_tiled_swapping@non-threaded: - shard-hsw: [PASS][12] -> [DMESG-FAIL][13] ([fdo#108686]) [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-hsw2/igt@gem_tiled_swapping@non-threaded.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-hsw1/igt@gem_tiled_swapping@non-threaded.html * igt@gem_userptr_blits@sync-unmap-cycles: - shard-snb: [PASS][14] -> [DMESG-WARN][15] ([fdo#111870]) +1 similar issue [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-snb6/igt@gem_userptr_blits@sync-unmap-cycles.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-snb6/igt@gem_userptr_blits@sync-unmap-cycles.html * igt@i915_suspend@sysfs-reader: - shard-apl: [PASS][16] -> [DMESG-WARN][17] ([fdo#108566]) +3 similar issues [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-apl1/igt@i915_suspend@sysfs-reader.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-apl4/igt@i915_suspend@sysfs-reader.html * igt@kms_flip@flip-vs-expired-vblank: - shard-glk: [PASS][18] -> [FAIL][19] ([fdo#105363]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-glk6/igt@kms_flip@flip-vs-expired-vblank.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-glk5/igt@kms_flip@flip-vs-expired-vblank.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-pwrite: - shard-iclb: [PASS][20] -> [FAIL][21] ([fdo#103167]) +2 similar issues [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb6/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-pwrite.html [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-pwrite.html * igt@kms_psr@psr2_dpms: - shard-iclb: [PASS][22] -> [SKIP][23] ([fdo#109441]) [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb2/igt@kms_psr@psr2_dpms.html [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb1/igt@kms_psr@psr2_dpms.html #### Possible fixes #### * igt@gem_eio@in-flight-contexts-immediate: - shard-snb: [FAIL][24] ([fdo#111925]) -> [PASS][25] [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-snb1/igt@gem_eio@in-flight-contexts-immediate.html [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-snb2/igt@gem_eio@in-flight-contexts-immediate.html * igt@gem_exec_schedule@in-order-bsd2: - shard-iclb: [SKIP][26] ([fdo#109276]) -> [PASS][27] +13 similar issues [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb6/igt@gem_exec_schedule@in-order-bsd2.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb2/igt@gem_exec_schedule@in-order-bsd2.html * igt@gem_exec_schedule@wide-bsd: - shard-iclb: [SKIP][28] ([fdo#111325]) -> [PASS][29] +2 similar issues [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb4/igt@gem_exec_schedule@wide-bsd.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb8/igt@gem_exec_schedule@wide-bsd.html * igt@gem_userptr_blits@dmabuf-unsync: - shard-hsw: [DMESG-WARN][30] ([fdo#111870]) -> [PASS][31] [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-hsw4/igt@gem_userptr_blits@dmabuf-unsync.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-hsw2/igt@gem_userptr_blits@dmabuf-unsync.html * {igt@i915_pm_dc@dc6-psr}: - shard-iclb: [FAIL][32] ([fdo#110548]) -> [PASS][33] [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb4/igt@i915_pm_dc@dc6-psr.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb8/igt@i915_pm_dc@dc6-psr.html * igt@kms_flip@2x-flip-vs-expired-vblank-interruptible: - shard-glk: [FAIL][34] ([fdo#105363]) -> [PASS][35] [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-glk2/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-glk1/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible.html * igt@kms_flip@flip-vs-suspend-interruptible: - shard-kbl: [INCOMPLETE][36] ([fdo#103665]) -> [PASS][37] [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-kbl1/igt@kms_flip@flip-vs-suspend-interruptible.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-kbl4/igt@kms_flip@flip-vs-suspend-interruptible.html - shard-hsw: [INCOMPLETE][38] ([fdo#103540]) -> [PASS][39] [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-hsw6/igt@kms_flip@flip-vs-suspend-interruptible.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-hsw1/igt@kms_flip@flip-vs-suspend-interruptible.html * igt@kms_frontbuffer_tracking@basic: - shard-iclb: [FAIL][40] ([fdo#103167]) -> [PASS][41] +3 similar issues [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb7/igt@kms_frontbuffer_tracking@basic.html [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb4/igt@kms_frontbuffer_tracking@basic.html * igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-mmap-wc: - shard-skl: [DMESG-WARN][42] ([fdo#106107]) -> [PASS][43] [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-skl3/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-mmap-wc.html [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-skl9/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-mmap-wc.html * igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-indfb-draw-mmap-cpu: - shard-iclb: [INCOMPLETE][44] ([fdo#106978] / [fdo#107713]) -> [PASS][45] [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb1/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-indfb-draw-mmap-cpu.html [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb8/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-indfb-draw-mmap-cpu.html * igt@kms_plane_lowres@pipe-a-tiling-y: - shard-iclb: [FAIL][46] ([fdo#103166]) -> [PASS][47] [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb6/igt@kms_plane_lowres@pipe-a-tiling-y.html [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb2/igt@kms_plane_lowres@pipe-a-tiling-y.html * igt@kms_psr@psr2_cursor_render: - shard-iclb: [SKIP][48] ([fdo#109441]) -> [PASS][49] +1 similar issue [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb6/igt@kms_psr@psr2_cursor_render.html [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb2/igt@kms_psr@psr2_cursor_render.html * igt@kms_vblank@pipe-a-ts-continuation-suspend: - shard-apl: [DMESG-WARN][50] ([fdo#108566]) -> [PASS][51] +6 similar issues [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-apl3/igt@kms_vblank@pipe-a-ts-continuation-suspend.html [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-apl3/igt@kms_vblank@pipe-a-ts-continuation-suspend.html * igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend: - {shard-tglb}: [INCOMPLETE][52] ([fdo#111832] / [fdo#111850]) -> [PASS][53] [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-tglb1/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-tglb5/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html * igt@perf_pmu@cpu-hotplug: - shard-apl: [TIMEOUT][54] ([fdo#111546] / [fdo#111800]) -> [PASS][55] [54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-apl6/igt@perf_pmu@cpu-hotplug.html [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-apl6/igt@perf_pmu@cpu-hotplug.html #### Warnings #### * igt@gem_mocs_settings@mocs-reset-bsd2: - shard-iclb: [FAIL][56] ([fdo#111330]) -> [SKIP][57] ([fdo#109276]) +2 similar issues [56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-iclb4/igt@gem_mocs_settings@mocs-reset-bsd2.html [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-iclb8/igt@gem_mocs_settings@mocs-reset-bsd2.html * igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-onoff: - shard-apl: [INCOMPLETE][58] ([fdo#103927]) -> [SKIP][59] ([fdo#109271]) [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7046/shard-apl6/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-onoff.html [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/shard-apl6/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-onoff.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166 [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 [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#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108 [fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363 [fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107 [fdo#106978]: https://bugs.freedesktop.org/show_bug.cgi?id=106978 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566 [fdo#108686]: https://bugs.freedesktop.org/show_bug.cgi?id=108686 [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#110548]: https://bugs.freedesktop.org/show_bug.cgi?id=110548 [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#111546]: https://bugs.freedesktop.org/show_bug.cgi?id=111546 [fdo#111800]: https://bugs.freedesktop.org/show_bug.cgi?id=111800 [fdo#111832]: https://bugs.freedesktop.org/show_bug.cgi?id=111832 [fdo#111850]: https://bugs.freedesktop.org/show_bug.cgi?id=111850 [fdo#111867]: https://bugs.freedesktop.org/show_bug.cgi?id=111867 [fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870 [fdo#111925]: https://bugs.freedesktop.org/show_bug.cgi?id=111925 Participating hosts (11 -> 11) ------------------------------ No changes in participating hosts Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_7046 -> Patchwork_14739 CI-20190529: 20190529 CI_DRM_7046: 136f98967ad06da28fd795aa83be314c7b641c49 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5220: 1e38e32d721210a780198c8293a6b8c8e881df68 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_14739: 8c65f9a90680ed75a3a32a7d74b2118d22d06148 @ git://anongit.freedesktop.org/gfx-ci/linux piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14739/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-10-10 12:04 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-10-09 23:04 [PATCH 1/2] drm/i915/tgl: the BCS engine supports relative MMIO Daniele Ceraolo Spurio 2019-10-09 23:04 ` [PATCH 2/2] drm/i915/tgl: simplify the lrc register list for !RCS Daniele Ceraolo Spurio 2019-10-10 9:03 ` Chris Wilson 2019-10-10 2:08 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/tgl: the BCS engine supports relative MMIO Patchwork 2019-10-10 9:17 ` Chris Wilson 2019-10-10 8:49 ` [PATCH 1/2] " Chris Wilson 2019-10-10 12:04 ` ✓ Fi.CI.IGT: success for series starting with [1/2] " 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.