* [PATCH] drm/i915/execlists: Flush the post-sync breadcrumb write harder
@ 2019-08-27 12:06 Chris Wilson
2019-08-27 13:38 ` ✓ Fi.CI.BAT: success for " Patchwork
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Chris Wilson @ 2019-08-27 12:06 UTC (permalink / raw)
To: intel-gfx
Quite rarely we see that the CS completion event fires before the
breadcrumb is coherent, which presumably is a result of the CS_STALL not
waiting for the post-sync operation. Try following in a DC_FLUSH into
the following pipecontrol to see if that makes any difference.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
---
drivers/gpu/drm/i915/gt/intel_lrc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
index 80a3f1dbb456..48046d445733 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc.c
+++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
@@ -2971,6 +2971,7 @@ static u32 *gen8_emit_fini_breadcrumb_rcs(struct i915_request *request, u32 *cs)
/* XXX flush+write+CS_STALL all in one upsets gem_concurrent_blt:kbl */
cs = gen8_emit_pipe_control(cs,
PIPE_CONTROL_FLUSH_ENABLE |
+ PIPE_CONTROL_DC_FLUSH_ENABLE |
PIPE_CONTROL_CS_STALL,
0);
--
2.23.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 6+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915/execlists: Flush the post-sync breadcrumb write harder
2019-08-27 12:06 [PATCH] drm/i915/execlists: Flush the post-sync breadcrumb write harder Chris Wilson
@ 2019-08-27 13:38 ` Patchwork
2019-08-28 12:12 ` ✓ Fi.CI.IGT: " Patchwork
2019-08-28 12:49 ` [PATCH] " Mika Kuoppala
2 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2019-08-27 13:38 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/execlists: Flush the post-sync breadcrumb write harder
URL : https://patchwork.freedesktop.org/series/65871/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6792 -> Patchwork_14200
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/
Known issues
------------
Here are the changes found in Patchwork_14200 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s3:
- fi-blb-e6850: [PASS][1] -> [INCOMPLETE][2] ([fdo#107718])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html
* igt@kms_chamelium@dp-crc-fast:
- fi-cml-u2: [PASS][3] -> [FAIL][4] ([fdo#110627])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html
* igt@kms_frontbuffer_tracking@basic:
- fi-hsw-peppy: [PASS][5] -> [DMESG-WARN][6] ([fdo#102614])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
#### Possible fixes ####
* igt@i915_selftest@live_execlists:
- fi-skl-gvtdvm: [DMESG-FAIL][7] ([fdo#111108]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/fi-skl-gvtdvm/igt@i915_selftest@live_execlists.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/fi-skl-gvtdvm/igt@i915_selftest@live_execlists.html
* igt@kms_frontbuffer_tracking@basic:
- fi-icl-u2: [FAIL][9] ([fdo#103167]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
#### Warnings ####
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-icl-u2: [FAIL][11] ([fdo#111407]) -> [FAIL][12] ([fdo#109483])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html
[fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#109483]: https://bugs.freedesktop.org/show_bug.cgi?id=109483
[fdo#110627]: https://bugs.freedesktop.org/show_bug.cgi?id=110627
[fdo#111108]: https://bugs.freedesktop.org/show_bug.cgi?id=111108
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
Participating hosts (52 -> 43)
------------------------------
Missing (9): fi-kbl-soraka fi-hsw-4770r 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_6792 -> Patchwork_14200
CI-20190529: 20190529
CI_DRM_6792: 87f7792bc3891de3fab4fb64d66a85a66729e3d4 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5150: a4e8217bcdfef9bb523f26a9084bbf615a6e8abb @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14200: c4d5dbd2cff36d506ce5f84da812b77434e94cfb @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
c4d5dbd2cff3 drm/i915/execlists: Flush the post-sync breadcrumb write harder
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* ✓ Fi.CI.IGT: success for drm/i915/execlists: Flush the post-sync breadcrumb write harder
2019-08-27 12:06 [PATCH] drm/i915/execlists: Flush the post-sync breadcrumb write harder Chris Wilson
2019-08-27 13:38 ` ✓ Fi.CI.BAT: success for " Patchwork
@ 2019-08-28 12:12 ` Patchwork
2019-08-28 12:49 ` [PATCH] " Mika Kuoppala
2 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2019-08-28 12:12 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/execlists: Flush the post-sync breadcrumb write harder
URL : https://patchwork.freedesktop.org/series/65871/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6792_full -> Patchwork_14200_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_14200_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_parallel@bcs0-contexts:
- shard-hsw: [PASS][1] -> [FAIL][2] ([fdo#111469])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-hsw7/igt@gem_exec_parallel@bcs0-contexts.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-hsw6/igt@gem_exec_parallel@bcs0-contexts.html
* igt@gem_exec_schedule@reorder-wide-bsd:
- shard-iclb: [PASS][3] -> [SKIP][4] ([fdo#111325]) +6 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb3/igt@gem_exec_schedule@reorder-wide-bsd.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb1/igt@gem_exec_schedule@reorder-wide-bsd.html
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-skl: [PASS][5] -> [INCOMPLETE][6] ([fdo#110741])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-skl2/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-skl10/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
* igt@kms_flip@flip-vs-expired-vblank:
- shard-glk: [PASS][7] -> [FAIL][8] ([fdo#105363])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-glk3/igt@kms_flip@flip-vs-expired-vblank.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-glk3/igt@kms_flip@flip-vs-expired-vblank.html
* igt@kms_flip@flip-vs-modeset-vs-hang:
- shard-apl: [PASS][9] -> [INCOMPLETE][10] ([fdo#103927]) +5 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-apl6/igt@kms_flip@flip-vs-modeset-vs-hang.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-apl5/igt@kms_flip@flip-vs-modeset-vs-hang.html
* igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw:
- shard-iclb: [PASS][11] -> [FAIL][12] ([fdo#103167]) +4 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb3/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-apl: [PASS][13] -> [DMESG-WARN][14] ([fdo#108566]) +4 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-apl2/igt@kms_frontbuffer_tracking@fbc-suspend.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-apl4/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-gtt:
- shard-iclb: [PASS][15] -> [INCOMPLETE][16] ([fdo#106978] / [fdo#107713])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb3/igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-gtt.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb7/igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-gtt.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-gtt:
- shard-skl: [PASS][17] -> [FAIL][18] ([fdo#103167])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-skl3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-gtt.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-skl8/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-gtt.html
* igt@kms_psr@suspend:
- shard-skl: [PASS][19] -> [INCOMPLETE][20] ([fdo#108972])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-skl2/igt@kms_psr@suspend.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-skl3/igt@kms_psr@suspend.html
* igt@prime_busy@hang-bsd2:
- shard-iclb: [PASS][21] -> [SKIP][22] ([fdo#109276]) +21 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb1/igt@prime_busy@hang-bsd2.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb7/igt@prime_busy@hang-bsd2.html
* igt@tools_test@sysfs_l3_parity:
- shard-hsw: [PASS][23] -> [SKIP][24] ([fdo#109271])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-hsw2/igt@tools_test@sysfs_l3_parity.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-hsw1/igt@tools_test@sysfs_l3_parity.html
#### Possible fixes ####
* igt@gem_ctx_shared@exec-single-timeline-bsd:
- shard-iclb: [SKIP][25] ([fdo#110841]) -> [PASS][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb1/igt@gem_ctx_shared@exec-single-timeline-bsd.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb6/igt@gem_ctx_shared@exec-single-timeline-bsd.html
* igt@gem_exec_schedule@fifo-bsd1:
- shard-iclb: [SKIP][27] ([fdo#109276]) -> [PASS][28] +17 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb5/igt@gem_exec_schedule@fifo-bsd1.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb1/igt@gem_exec_schedule@fifo-bsd1.html
* igt@gem_exec_schedule@wide-bsd:
- shard-iclb: [SKIP][29] ([fdo#111325]) -> [PASS][30] +8 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb4/igt@gem_exec_schedule@wide-bsd.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb7/igt@gem_exec_schedule@wide-bsd.html
* igt@gem_wait@write-wait-vecs0:
- shard-skl: [DMESG-WARN][31] ([fdo#106107]) -> [PASS][32] +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-skl7/igt@gem_wait@write-wait-vecs0.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-skl5/igt@gem_wait@write-wait-vecs0.html
* igt@kms_cursor_edge_walk@pipe-b-128x128-top-edge:
- shard-apl: [INCOMPLETE][33] ([fdo#103927]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-apl8/igt@kms_cursor_edge_walk@pipe-b-128x128-top-edge.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-apl6/igt@kms_cursor_edge_walk@pipe-b-128x128-top-edge.html
* igt@kms_flip@flip-vs-expired-vblank:
- shard-skl: [FAIL][35] ([fdo#105363]) -> [PASS][36] +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-skl5/igt@kms_flip@flip-vs-expired-vblank.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-skl4/igt@kms_flip@flip-vs-expired-vblank.html
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-skl: [INCOMPLETE][37] ([fdo#109507]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-skl8/igt@kms_flip@flip-vs-suspend-interruptible.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-skl2/igt@kms_flip@flip-vs-suspend-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render:
- shard-iclb: [FAIL][39] ([fdo#103167]) -> [PASS][40] +5 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb6/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb3/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-wc:
- shard-skl: [FAIL][41] ([fdo#103167]) -> [PASS][42] +2 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-skl4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-wc.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-skl5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-wc.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
- shard-apl: [DMESG-WARN][43] ([fdo#108566]) -> [PASS][44] +3 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-apl7/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-apl6/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [FAIL][45] ([fdo#108145] / [fdo#110403]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-skl10/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-skl9/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-iclb: [FAIL][47] ([fdo#103166]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb7/igt@kms_plane_lowres@pipe-a-tiling-x.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb3/igt@kms_plane_lowres@pipe-a-tiling-x.html
* igt@perf_pmu@enable-race-rcs0:
- shard-iclb: [INCOMPLETE][49] ([fdo#107713]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb7/igt@perf_pmu@enable-race-rcs0.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb1/igt@perf_pmu@enable-race-rcs0.html
#### Warnings ####
* igt@gem_ctx_isolation@vcs1-nonpriv:
- shard-iclb: [FAIL][51] ([fdo#111329]) -> [SKIP][52] ([fdo#109276])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb4/igt@gem_ctx_isolation@vcs1-nonpriv.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb8/igt@gem_ctx_isolation@vcs1-nonpriv.html
* igt@gem_mocs_settings@mocs-reset-bsd2:
- shard-iclb: [SKIP][53] ([fdo#109276]) -> [FAIL][54] ([fdo#111330]) +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-iclb5/igt@gem_mocs_settings@mocs-reset-bsd2.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-iclb4/igt@gem_mocs_settings@mocs-reset-bsd2.html
* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][55] ([fdo#110321] / [fdo#110336]) -> [INCOMPLETE][56] ([fdo#103927])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6792/shard-apl4/igt@kms_content_protection@atomic.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14200/shard-apl4/igt@kms_content_protection@atomic.html
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[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#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#108972]: https://bugs.freedesktop.org/show_bug.cgi?id=108972
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109507]: https://bugs.freedesktop.org/show_bug.cgi?id=109507
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#110403]: https://bugs.freedesktop.org/show_bug.cgi?id=110403
[fdo#110741]: https://bugs.freedesktop.org/show_bug.cgi?id=110741
[fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841
[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#111469]: https://bugs.freedesktop.org/show_bug.cgi?id=111469
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6792 -> Patchwork_14200
CI-20190529: 20190529
CI_DRM_6792: 87f7792bc3891de3fab4fb64d66a85a66729e3d4 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5150: a4e8217bcdfef9bb523f26a9084bbf615a6e8abb @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14200: c4d5dbd2cff36d506ce5f84da812b77434e94cfb @ 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_14200/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] drm/i915/execlists: Flush the post-sync breadcrumb write harder
2019-08-27 12:06 [PATCH] drm/i915/execlists: Flush the post-sync breadcrumb write harder Chris Wilson
2019-08-27 13:38 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-08-28 12:12 ` ✓ Fi.CI.IGT: " Patchwork
@ 2019-08-28 12:49 ` Mika Kuoppala
2019-08-28 13:09 ` Chris Wilson
2 siblings, 1 reply; 6+ messages in thread
From: Mika Kuoppala @ 2019-08-28 12:49 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quite rarely we see that the CS completion event fires before the
> breadcrumb is coherent, which presumably is a result of the CS_STALL not
> waiting for the post-sync operation. Try following in a DC_FLUSH into
> the following pipecontrol to see if that makes any difference.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Acked-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_lrc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index 80a3f1dbb456..48046d445733 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -2971,6 +2971,7 @@ static u32 *gen8_emit_fini_breadcrumb_rcs(struct i915_request *request, u32 *cs)
> /* XXX flush+write+CS_STALL all in one upsets gem_concurrent_blt:kbl */
> cs = gen8_emit_pipe_control(cs,
> PIPE_CONTROL_FLUSH_ENABLE |
> + PIPE_CONTROL_DC_FLUSH_ENABLE |
> PIPE_CONTROL_CS_STALL,
> 0);
>
> --
> 2.23.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] drm/i915/execlists: Flush the post-sync breadcrumb write harder
2019-08-28 12:49 ` [PATCH] " Mika Kuoppala
@ 2019-08-28 13:09 ` Chris Wilson
2019-08-28 18:09 ` Chris Wilson
0 siblings, 1 reply; 6+ messages in thread
From: Chris Wilson @ 2019-08-28 13:09 UTC (permalink / raw)
To: Mika Kuoppala, intel-gfx
Quoting Mika Kuoppala (2019-08-28 13:49:55)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
> > Quite rarely we see that the CS completion event fires before the
> > breadcrumb is coherent, which presumably is a result of the CS_STALL not
> > waiting for the post-sync operation. Try following in a DC_FLUSH into
> > the following pipecontrol to see if that makes any difference.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>
> Acked-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Yup, there's only way to find out if this helps... Ta,
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] drm/i915/execlists: Flush the post-sync breadcrumb write harder
2019-08-28 13:09 ` Chris Wilson
@ 2019-08-28 18:09 ` Chris Wilson
0 siblings, 0 replies; 6+ messages in thread
From: Chris Wilson @ 2019-08-28 18:09 UTC (permalink / raw)
To: Mika Kuoppala, intel-gfx
Quoting Chris Wilson (2019-08-28 14:09:23)
> Quoting Mika Kuoppala (2019-08-28 13:49:55)
> > Chris Wilson <chris@chris-wilson.co.uk> writes:
> >
> > > Quite rarely we see that the CS completion event fires before the
> > > breadcrumb is coherent, which presumably is a result of the CS_STALL not
> > > waiting for the post-sync operation. Try following in a DC_FLUSH into
> > > the following pipecontrol to see if that makes any difference.
> > >
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> >
> > Acked-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>
> Yup, there's only way to find out if this helps... Ta,
And the answer came back straight away. Nope.
Sigh,
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-08-28 18:09 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-08-27 12:06 [PATCH] drm/i915/execlists: Flush the post-sync breadcrumb write harder Chris Wilson
2019-08-27 13:38 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-08-28 12:12 ` ✓ Fi.CI.IGT: " Patchwork
2019-08-28 12:49 ` [PATCH] " Mika Kuoppala
2019-08-28 13:09 ` Chris Wilson
2019-08-28 18:09 ` Chris Wilson
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.