[Intel-gfx] ✗ Fi.CI.IGT: failure for x86/mm: Fix PAT bit missing from page protection modify mask (rev3)
== Series Details ==
Series: x86/mm: Fix PAT bit missing from page protection modify mask (rev3)
URL : https://patchwork.freedesktop.org/series/116883/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13256_full -> Patchwork_116883v3_full
Summary
---
**FAILURE**
Serious unknown changes coming with Patchwork_116883v3_full absolutely need
to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_116883v3_full, please notify your bug team to allow
them
to document this new failure mode, which will reduce false positives in CI.
Participating hosts (7 -> 7)
--
No changes in participating hosts
Possible new issues
---
Here are the unknown changes that may have been introduced in
Patchwork_116883v3_full:
### IGT changes ###
Possible regressions
* igt@gem_exec_parallel@contexts:
- shard-glk: NOTRUN -> [TIMEOUT][1] +1 similar issue
[1]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-glk4/igt@gem_exec_paral...@contexts.html
* igt@gem_exec_reloc@basic-write-wc:
- shard-glk: [PASS][2] -> [TIMEOUT][3] +2 similar issues
[2]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-glk1/igt@gem_exec_re...@basic-write-wc.html
[3]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-glk4/igt@gem_exec_re...@basic-write-wc.html
Known issues
Here are the changes found in Patchwork_116883v3_full that come from known
issues:
### IGT changes ###
Issues hit
* igt@gem_ctx_persistence@processes:
- shard-snb: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#1099]) +1
similar issue
[4]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-snb4/igt@gem_ctx_persiste...@processes.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-glk: NOTRUN -> [FAIL][5] ([i915#2842])
[5]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-glk9/igt@gem_exec_fair@basic-pace-s...@rcs0.html
* igt@i915_module_load@load:
- shard-glk: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#6227])
[6]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-glk9/igt@i915_module_l...@load.html
* igt@i915_pm_rpm@system-suspend-devices:
- shard-snb: NOTRUN -> [SKIP][7] ([fdo#109271]) +80 similar issues
[7]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-snb4/igt@i915_pm_...@system-suspend-devices.html
* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#3886])
[8]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-glk9/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html
* igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes:
- shard-apl: [PASS][9] -> [ABORT][10] ([i915#180])
[9]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-apl1/igt@kms_plane@plane-panning-bottom-right-susp...@pipe-a-planes.html
[10]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-apl3/igt@kms_plane@plane-panning-bottom-right-susp...@pipe-a-planes.html
* igt@kms_plane_scaling@plane-upscale-with-rotation-20x20@pipe-c-hdmi-a-1:
- shard-glk: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4579]) +2
similar issues
[11]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-glk9/igt@kms_plane_scaling@plane-upscale-with-rotation-20...@pipe-c-hdmi-a-1.html
*
igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-b-hdmi-a-1:
- shard-snb: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#4579]) +14
similar issues
[12]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-snb1/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0...@pipe-b-hdmi-a-1.html
* igt@kms_vblank@pipe-d-wait-busy-hang:
- shard-glk: NOTRUN -> [SKIP][13] ([fdo#109271]) +37 similar issues
[13]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-glk9/igt@kms_vbl...@pipe-d-wait-busy-hang.html
* igt@perf@enable-disable@0-rcs0:
- shard-glk: [PASS][14] -> [TIMEOUT][15] ([i915#8170])
[14]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-glk1/igt@perf@enable-disa...@0-rcs0.html
[15]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116883v3/shard-glk4/igt@perf@enable-disa...@0-rcs0.html
Possible fixes
* igt@drm_fdinfo@most-busy-idle-check-all@rcs0:
- {shard-rkl}:[FAIL][16] ([i915#7742]) -> [PASS][17]
[16]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-rkl-4/igt@drm_fdinfo@most-busy-idle-check-...@rcs0.html
[17]:
[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/mtl: Cleanup usage of phy lane reset
== Series Details ==
Series: drm/i915/mtl: Cleanup usage of phy lane reset
URL : https://patchwork.freedesktop.org/series/119138/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13256_full -> Patchwork_119138v1_full
Summary
---
**SUCCESS**
No regressions found.
Participating hosts (7 -> 7)
--
No changes in participating hosts
Known issues
Here are the changes found in Patchwork_119138v1_full that come from known
issues:
### IGT changes ###
Issues hit
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [PASS][1] -> [FAIL][2] ([i915#2842])
[1]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-glk4/igt@gem_exec_fair@basic-pace-sh...@rcs0.html
[2]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-glk6/igt@gem_exec_fair@basic-pace-sh...@rcs0.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-glk: NOTRUN -> [FAIL][3] ([i915#2842])
[3]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-glk5/igt@gem_exec_fair@basic-pace-s...@rcs0.html
* igt@i915_module_load@load:
- shard-glk: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#6227])
[4]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-glk5/igt@i915_module_l...@load.html
* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#3886])
[5]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-glk5/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html
* igt@kms_flip@2x-flip-vs-dpms:
- shard-snb: NOTRUN -> [SKIP][6] ([fdo#109271]) +9 similar issues
[6]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-snb2/igt@kms_f...@2x-flip-vs-dpms.html
* igt@kms_plane_scaling@plane-upscale-with-rotation-20x20@pipe-c-hdmi-a-1:
- shard-glk: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#4579]) +2
similar issues
[7]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-glk5/igt@kms_plane_scaling@plane-upscale-with-rotation-20...@pipe-c-hdmi-a-1.html
*
igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-b-hdmi-a-1:
- shard-snb: NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#4579]) +6
similar issues
[8]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-snb1/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0...@pipe-b-hdmi-a-1.html
* igt@kms_vblank@pipe-d-wait-busy-hang:
- shard-glk: NOTRUN -> [SKIP][9] ([fdo#109271]) +37 similar issues
[9]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-glk5/igt@kms_vbl...@pipe-d-wait-busy-hang.html
Possible fixes
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl: [FAIL][10] ([i915#2842]) -> [PASS][11]
[10]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-apl1/igt@gem_exec_fair@basic-none-s...@rcs0.html
[11]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-apl6/igt@gem_exec_fair@basic-none-s...@rcs0.html
* igt@gem_exec_fair@basic-none@vecs0:
- {shard-rkl}:[FAIL][12] ([i915#2842]) -> [PASS][13] +2 similar
issues
[12]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-rkl-2/igt@gem_exec_fair@basic-n...@vecs0.html
[13]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-rkl-2/igt@gem_exec_fair@basic-n...@vecs0.html
* igt@gen9_exec_parse@allowed-single:
- shard-glk: [ABORT][14] ([i915#5566]) -> [PASS][15]
[14]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-glk5/igt@gen9_exec_pa...@allowed-single.html
[15]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-glk5/igt@gen9_exec_pa...@allowed-single.html
* igt@i915_suspend@basic-s2idle-without-i915:
- {shard-tglu}: [ABORT][16] ([i915#8213]) -> [PASS][17]
[16]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-tglu-2/igt@i915_susp...@basic-s2idle-without-i915.html
[17]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-tglu-6/igt@i915_susp...@basic-s2idle-without-i915.html
* igt@kms_async_flips@alternate-sync-async-flip@pipe-a-vga-1:
- shard-snb: [FAIL][18] ([i915#2521]) -> [PASS][19]
[18]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-snb7/igt@kms_async_flips@alternate-sync-async-f...@pipe-a-vga-1.html
[19]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119138v1/shard-snb4/igt@kms_async_flips@alternate-sync-async-f...@pipe-a-vga-1.html
* igt@kms_async_flips@alternate-sync-async-flip@pipe-b-hdmi-a-1:
- shard-glk: [FAIL][20] ([i915#2521]) -> [PASS][21]
[20]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13256/shard-glk7/igt@kms_async_flips@alternate-sync-async-f...@pipe-b-hdmi-a-1.html
[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dp: Cable type identification for DP2.1
== Series Details ==
Series: drm/i915/dp: Cable type identification for DP2.1
URL : https://patchwork.freedesktop.org/series/119109/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13255_full -> Patchwork_119109v1_full
Summary
---
**SUCCESS**
No regressions found.
Participating hosts (7 -> 7)
--
No changes in participating hosts
Known issues
Here are the changes found in Patchwork_119109v1_full that come from known
issues:
### IGT changes ###
Issues hit
* igt@gem_exec_fair@basic-pace@vcs0:
- shard-glk: [PASS][1] -> [FAIL][2] ([i915#2842])
[1]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13255/shard-glk2/igt@gem_exec_fair@basic-p...@vcs0.html
[2]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-glk4/igt@gem_exec_fair@basic-p...@vcs0.html
* igt@i915_selftest@live@gt_heartbeat:
- shard-apl: [PASS][3] -> [DMESG-FAIL][4] ([i915#5334])
[3]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13255/shard-apl1/igt@i915_selftest@live@gt_heartbeat.html
[4]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-apl2/igt@i915_selftest@live@gt_heartbeat.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-glk: [PASS][5] -> [FAIL][6] ([i915#2346])
[5]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13255/shard-glk5/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html
[6]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-glk7/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@bc-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][7] -> [FAIL][8] ([i915#79]) +1 similar issue
[7]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13255/shard-glk7/igt@kms_flip@2x-flip-vs-expired-vblank-interrupti...@bc-hdmi-a1-hdmi-a2.html
[8]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-glk2/igt@kms_flip@2x-flip-vs-expired-vblank-interrupti...@bc-hdmi-a1-hdmi-a2.html
* igt@kms_plane_scaling@plane-upscale-with-modifiers-20x20@pipe-b-vga-1:
- shard-snb: NOTRUN -> [SKIP][9] ([fdo#109271] / [i915#4579]) +12
similar issues
[9]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-snb6/igt@kms_plane_scaling@plane-upscale-with-modifiers-20...@pipe-b-vga-1.html
*
igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-a-vga-1:
- shard-snb: NOTRUN -> [SKIP][10] ([fdo#109271]) +15 similar issues
[10]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-snb4/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0...@pipe-a-vga-1.html
Possible fixes
* igt@i915_pm_dc@dc9-dpms:
- {shard-tglu}: [SKIP][11] ([i915#4281]) -> [PASS][12]
[11]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13255/shard-tglu-6/igt@i915_pm...@dc9-dpms.html
[12]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-tglu-4/igt@i915_pm...@dc9-dpms.html
* igt@i915_pm_rpm@modeset-lpsp-stress:
- {shard-rkl}:[SKIP][13] ([i915#1397]) -> [PASS][14]
[13]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13255/shard-rkl-2/igt@i915_pm_...@modeset-lpsp-stress.html
[14]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-rkl-7/igt@i915_pm_...@modeset-lpsp-stress.html
* igt@i915_pm_rpm@modeset-non-lpsp-stress-no-wait:
- {shard-dg1}:[SKIP][15] ([i915#1397]) -> [PASS][16]
[15]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13255/shard-dg1-19/igt@i915_pm_...@modeset-non-lpsp-stress-no-wait.html
[16]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-dg1-13/igt@i915_pm_...@modeset-non-lpsp-stress-no-wait.html
* igt@i915_selftest@live@gt_heartbeat:
- shard-glk: [DMESG-FAIL][17] ([i915#5334]) -> [PASS][18]
[17]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13255/shard-glk1/igt@i915_selftest@live@gt_heartbeat.html
[18]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-glk6/igt@i915_selftest@live@gt_heartbeat.html
- {shard-rkl}:[DMESG-FAIL][19] -> [PASS][20]
[19]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13255/shard-rkl-2/igt@i915_selftest@live@gt_heartbeat.html
[20]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-rkl-7/igt@i915_selftest@live@gt_heartbeat.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-apl: [FAIL][21] ([i915#2346]) -> [PASS][22]
[21]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13255/shard-apl2/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html
[22]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119109v1/shard-apl6/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html
* igt@perf_pmu@most-busy-idle-check-all@bcs0:
[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/mtl: Add new vswing table for C20 phy to support DP 1.4 (rev4)
== Series Details ==
Series: drm/i915/mtl: Add new vswing table for C20 phy to support DP 1.4 (rev4)
URL : https://patchwork.freedesktop.org/series/118925/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13253_full -> Patchwork_118925v4_full
Summary
---
**SUCCESS**
No regressions found.
Participating hosts (7 -> 7)
--
No changes in participating hosts
Known issues
Here are the changes found in Patchwork_118925v4_full that come from known
issues:
### IGT changes ###
Issues hit
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [PASS][1] -> [FAIL][2] ([i915#2842])
[1]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-glk5/igt@gem_exec_fair@basic-pace-sh...@rcs0.html
[2]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-glk1/igt@gem_exec_fair@basic-pace-sh...@rcs0.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-glk: NOTRUN -> [FAIL][3] ([i915#2842])
[3]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-glk2/igt@gem_exec_fair@basic-pace-s...@rcs0.html
* igt@gem_lmem_swapping@heavy-multi:
- shard-apl: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#4613])
[4]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-apl1/igt@gem_lmem_swapp...@heavy-multi.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-apl: NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#1937] /
[i915#4579])
[5]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-apl1/igt@i915_pm_lpsp@kms-l...@kms-lpsp-dp.html
* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#3886])
[6]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-glk2/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-glk: [PASS][7] -> [FAIL][8] ([i915#2346]) +1 similar issue
[7]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-glk5/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html
[8]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-glk1/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html
* igt@kms_flip@flip-vs-suspend-interruptible@b-dp1:
- shard-apl: [PASS][9] -> [ABORT][10] ([i915#180])
[9]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-apl6/igt@kms_flip@flip-vs-suspend-interrupti...@b-dp1.html
[10]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-apl6/igt@kms_flip@flip-vs-suspend-interrupti...@b-dp1.html
*
igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscaling@pipe-a-valid-mode:
- shard-apl: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4579]) +1
similar issue
[11]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-apl1/igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscal...@pipe-a-valid-mode.html
*
igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-valid-mode:
- shard-glk: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#4579])
[12]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-glk2/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscal...@pipe-a-valid-mode.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-shrfb-draw-mmap-cpu:
- shard-apl: NOTRUN -> [SKIP][13] ([fdo#109271]) +17 similar issues
[13]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-apl1/igt@kms_frontbuffer_track...@psr-2p-scndscrn-pri-shrfb-draw-mmap-cpu.html
*
igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-a-vga-1:
- shard-snb: NOTRUN -> [SKIP][14] ([fdo#109271]) +22 similar issues
[14]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-snb6/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotat...@pipe-a-vga-1.html
* igt@kms_plane_scaling@plane-upscale-with-modifiers-20x20@pipe-b-hdmi-a-1:
- shard-snb: NOTRUN -> [SKIP][15] ([fdo#109271] / [i915#4579]) +12
similar issues
[15]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-snb1/igt@kms_plane_scaling@plane-upscale-with-modifiers-20...@pipe-b-hdmi-a-1.html
* igt@kms_vblank@pipe-d-wait-busy-hang:
- shard-glk: NOTRUN -> [SKIP][16] ([fdo#109271]) +15 similar issues
[16]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118925v4/shard-glk2/igt@kms_vbl...@pipe-d-wait-busy-hang.html
Possible fixes
* igt@drm_fdinfo@most-busy-idle-check-all@rcs0:
- {shard-rkl}:[FAIL][17] ([i915#7742]) -> [PASS][18]
[17]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-rkl-3/igt@drm_fdinfo@most-busy-idle-check-...@rcs0.html
[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/gsc: take a wakeref for the proxy-init-completion check (rev2)
== Series Details ==
Series: drm/i915/gsc: take a wakeref for the proxy-init-completion check (rev2)
URL : https://patchwork.freedesktop.org/series/119092/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13253_full -> Patchwork_119092v2_full
Summary
---
**SUCCESS**
No regressions found.
Participating hosts (7 -> 7)
--
No changes in participating hosts
Known issues
Here are the changes found in Patchwork_119092v2_full that come from known
issues:
### IGT changes ###
Issues hit
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-glk: NOTRUN -> [FAIL][1] ([i915#2842])
[1]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-glk8/igt@gem_exec_fair@basic-pace-s...@rcs0.html
* igt@gem_lmem_swapping@heavy-multi:
- shard-apl: NOTRUN -> [SKIP][2] ([fdo#109271] / [i915#4613])
[2]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-apl3/igt@gem_lmem_swapp...@heavy-multi.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-apl: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#1937] /
[i915#4579])
[3]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-apl3/igt@i915_pm_lpsp@kms-l...@kms-lpsp-dp.html
* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#3886])
[4]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-glk8/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-glk: [PASS][5] -> [FAIL][6] ([i915#2346])
[5]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-glk5/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html
[6]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-glk5/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html
*
igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscaling@pipe-a-valid-mode:
- shard-apl: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#4579]) +1
similar issue
[7]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-apl3/igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscal...@pipe-a-valid-mode.html
*
igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-valid-mode:
- shard-glk: NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#4579])
[8]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-glk8/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscal...@pipe-a-valid-mode.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-shrfb-draw-mmap-cpu:
- shard-apl: NOTRUN -> [SKIP][9] ([fdo#109271]) +17 similar issues
[9]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-apl3/igt@kms_frontbuffer_track...@psr-2p-scndscrn-pri-shrfb-draw-mmap-cpu.html
*
igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-a-vga-1:
- shard-snb: NOTRUN -> [SKIP][10] ([fdo#109271]) +22 similar issues
[10]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-snb6/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotat...@pipe-a-vga-1.html
*
igt@kms_plane_scaling@planes-downscale-factor-0-75-unity-scaling@pipe-b-vga-1:
- shard-snb: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4579]) +14
similar issues
[11]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-snb7/igt@kms_plane_scaling@planes-downscale-factor-0-75-unity-scal...@pipe-b-vga-1.html
* igt@kms_vblank@pipe-d-wait-busy-hang:
- shard-glk: NOTRUN -> [SKIP][12] ([fdo#109271]) +15 similar issues
[12]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-glk8/igt@kms_vbl...@pipe-d-wait-busy-hang.html
Possible fixes
* igt@drm_fdinfo@most-busy-idle-check-all@rcs0:
- {shard-rkl}:[FAIL][13] ([i915#7742]) -> [PASS][14]
[13]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-rkl-3/igt@drm_fdinfo@most-busy-idle-check-...@rcs0.html
[14]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-rkl-1/igt@drm_fdinfo@most-busy-idle-check-...@rcs0.html
* igt@gem_spin_batch@spin-each:
- shard-apl: [FAIL][15] ([i915#2898]) -> [PASS][16]
[15]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-apl2/igt@gem_spin_ba...@spin-each.html
[16]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119092v2/shard-apl3/igt@gem_spin_ba...@spin-each.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-hdmi-a:
- {shard-rkl}:[SKIP][17] ([i915#1937] / [i915#4579]) -> [PASS][18]
[17]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-rkl-1/igt@i915_pm_lpsp@kms-l...@kms-lpsp-hdmi-a.html
[18]:
[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/dp_mst: Clear MSG_RDY flag before sending new message (rev3)
== Series Details == Series: drm/dp_mst: Clear MSG_RDY flag before sending new message (rev3) URL : https://patchwork.freedesktop.org/series/116623/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.
[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/tc: Use standard ternary operator instead of GCC extension
== Series Details ==
Series: drm/i915/tc: Use standard ternary operator instead of GCC extension
URL : https://patchwork.freedesktop.org/series/119098/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13253_full -> Patchwork_119098v1_full
Summary
---
**SUCCESS**
No regressions found.
Participating hosts (7 -> 7)
--
No changes in participating hosts
Possible new issues
---
Here are the unknown changes that may have been introduced in
Patchwork_119098v1_full:
### IGT changes ###
Suppressed
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@gem_ctx_shared@detached-shared-gtt:
- {shard-tglu}: [PASS][1] -> [INCOMPLETE][2]
[1]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-tglu-4/igt@gem_ctx_sha...@detached-shared-gtt.html
[2]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-tglu-5/igt@gem_ctx_sha...@detached-shared-gtt.html
Known issues
Here are the changes found in Patchwork_119098v1_full that come from known
issues:
### IGT changes ###
Issues hit
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-glk: NOTRUN -> [FAIL][3] ([i915#2842])
[3]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-glk2/igt@gem_exec_fair@basic-pace-s...@rcs0.html
* igt@gem_lmem_swapping@heavy-multi:
- shard-apl: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#4613])
[4]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-apl2/igt@gem_lmem_swapp...@heavy-multi.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-apl: NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#1937] /
[i915#4579])
[5]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-apl2/igt@i915_pm_lpsp@kms-l...@kms-lpsp-dp.html
* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#3886])
[6]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-glk2/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-glk: [PASS][7] -> [FAIL][8] ([i915#2346]) +1 similar issue
[7]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-glk5/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html
[8]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-glk5/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html
* igt@kms_flip@2x-flip-vs-expired-vblank@ac-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][9] -> [FAIL][10] ([i915#79])
[9]:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-glk4/igt@kms_flip@2x-flip-vs-expired-vbl...@ac-hdmi-a1-hdmi-a2.html
[10]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-glk7/igt@kms_flip@2x-flip-vs-expired-vbl...@ac-hdmi-a1-hdmi-a2.html
*
igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscaling@pipe-a-valid-mode:
- shard-apl: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4579]) +1
similar issue
[11]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-apl2/igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscal...@pipe-a-valid-mode.html
*
igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-valid-mode:
- shard-glk: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#4579])
[12]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-glk2/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscal...@pipe-a-valid-mode.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-shrfb-draw-mmap-cpu:
- shard-apl: NOTRUN -> [SKIP][13] ([fdo#109271]) +17 similar issues
[13]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-apl2/igt@kms_frontbuffer_track...@psr-2p-scndscrn-pri-shrfb-draw-mmap-cpu.html
*
igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-a-vga-1:
- shard-snb: NOTRUN -> [SKIP][14] ([fdo#109271]) +10 similar issues
[14]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-snb2/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotat...@pipe-a-vga-1.html
* igt@kms_plane_scaling@plane-upscale-with-modifiers-20x20@pipe-b-hdmi-a-1:
- shard-snb: NOTRUN -> [SKIP][15] ([fdo#109271] / [i915#4579]) +5
similar issues
[15]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_119098v1/shard-snb1/igt@kms_plane_scaling@plane-upscale-with-modifiers-20...@pipe-b-hdmi-a-1.html
* igt@kms_vblank@pipe-d-wait-busy-hang:
- shard-glk: NOTRUN -> [SKIP][16] ([fdo#109271]) +15 similar issues
[16]:
Re: [Intel-gfx] [PATCH v5] drm/dp_mst: Clear MSG_RDY flag before sending new message
On Fri, 09 Jun 2023, Wayne Lin wrote:
> [Why]
> The sequence for collecting down_reply from source perspective should
> be:
>
> Request_n->repeat (get partial reply of Request_n->clear message ready
> flag to ack DPRX that the message is received) till all partial
> replies for Request_n are received->new Request_n+1.
>
> Now there is chance that drm_dp_mst_hpd_irq() will fire new down
> request in the tx queue when the down reply is incomplete. Source is
> restricted to generate interveleaved message transactions so we should
> avoid it.
>
> Also, while assembling partial reply packets, reading out DPCD DOWN_REP
> Sideband MSG buffer + clearing DOWN_REP_MSG_RDY flag should be
> wrapped up as a complete operation for reading out a reply packet.
> Kicking off a new request before clearing DOWN_REP_MSG_RDY flag might
> be risky. e.g. If the reply of the new request has overwritten the
> DPRX DOWN_REP Sideband MSG buffer before source writing one to clear
> DOWN_REP_MSG_RDY flag, source then unintentionally flushes the reply
> for the new request. Should handle the up request in the same way.
>
> [How]
> Separete drm_dp_mst_hpd_irq() into 2 steps. After acking the MST IRQ
> event, driver calls drm_dp_mst_hpd_irq_send_new_request() and might
> trigger drm_dp_mst_kick_tx() only when there is no on going message
> transaction.
>
> Changes since v1:
> * Reworked on review comments received
> -> Adjust the fix to let driver explicitly kick off new down request
> when mst irq event is handled and acked
> -> Adjust the commit message
>
> Changes since v2:
> * Adjust the commit message
> * Adjust the naming of the divided 2 functions and add a new input
> parameter "ack".
> * Adjust code flow as per review comments.
>
> Changes since v3:
> * Update the function description of drm_dp_mst_hpd_irq_handle_event
>
> Changes since v4:
> * Change ack of drm_dp_mst_hpd_irq_handle_event() to be an array align
> the size of esi[]
I don't have the time for detailed review right now, but assuming
someone does that, and Intel CI passes (I bounced this to
intel-gfx@lists.freedesktop.org which should get it going),
Acked-by: Jani Nikula
>
> Signed-off-by: Wayne Lin
> Cc: sta...@vger.kernel.org
> ---
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 32 +--
> drivers/gpu/drm/display/drm_dp_mst_topology.c | 54 ---
> drivers/gpu/drm/i915/display/intel_dp.c | 7 +--
> drivers/gpu/drm/nouveau/dispnv50/disp.c | 12 +++--
> include/drm/display/drm_dp_mst_helper.h | 7 ++-
> 5 files changed, 81 insertions(+), 31 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> index d5cec03eaa8d..ec629b4037e4 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> @@ -3263,6 +3263,7 @@ static void dm_handle_mst_sideband_msg(struct
> amdgpu_dm_connector *aconnector)
>
> while (dret == dpcd_bytes_to_read &&
> process_count < max_process_count) {
> + u8 ack[DP_PSR_ERROR_STATUS - DP_SINK_COUNT_ESI] = {};
> u8 retry;
> dret = 0;
>
> @@ -3271,28 +3272,29 @@ static void dm_handle_mst_sideband_msg(struct
> amdgpu_dm_connector *aconnector)
> DRM_DEBUG_DRIVER("ESI %02x %02x %02x\n", esi[0], esi[1],
> esi[2]);
> /* handle HPD short pulse irq */
> if (aconnector->mst_mgr.mst_state)
> - drm_dp_mst_hpd_irq(
> - >mst_mgr,
> - esi,
> - _irq_handled);
> + drm_dp_mst_hpd_irq_handle_event(>mst_mgr,
> + esi,
> + ack,
> + _irq_handled);
>
> if (new_irq_handled) {
> /* ACK at DPCD to notify down stream */
> - const int ack_dpcd_bytes_to_write =
> - dpcd_bytes_to_read - 1;
> -
> for (retry = 0; retry < 3; retry++) {
> - u8 wret;
> -
> - wret = drm_dp_dpcd_write(
> - >dm_dp_aux.aux,
> - dpcd_addr + 1,
> - [1],
> - ack_dpcd_bytes_to_write);
> - if (wret == ack_dpcd_bytes_to_write)
> + ssize_t wret;
> +
> + wret =
> drm_dp_dpcd_writeb(>dm_dp_aux.aux,
> + dpcd_addr + 1,
> + ack[1]);
> + if (wret == 1)
> break;
>
[Intel-gfx] [PATCH v5] drm/dp_mst: Clear MSG_RDY flag before sending new message
[Why]
The sequence for collecting down_reply from source perspective should
be:
Request_n->repeat (get partial reply of Request_n->clear message ready
flag to ack DPRX that the message is received) till all partial
replies for Request_n are received->new Request_n+1.
Now there is chance that drm_dp_mst_hpd_irq() will fire new down
request in the tx queue when the down reply is incomplete. Source is
restricted to generate interveleaved message transactions so we should
avoid it.
Also, while assembling partial reply packets, reading out DPCD DOWN_REP
Sideband MSG buffer + clearing DOWN_REP_MSG_RDY flag should be
wrapped up as a complete operation for reading out a reply packet.
Kicking off a new request before clearing DOWN_REP_MSG_RDY flag might
be risky. e.g. If the reply of the new request has overwritten the
DPRX DOWN_REP Sideband MSG buffer before source writing one to clear
DOWN_REP_MSG_RDY flag, source then unintentionally flushes the reply
for the new request. Should handle the up request in the same way.
[How]
Separete drm_dp_mst_hpd_irq() into 2 steps. After acking the MST IRQ
event, driver calls drm_dp_mst_hpd_irq_send_new_request() and might
trigger drm_dp_mst_kick_tx() only when there is no on going message
transaction.
Changes since v1:
* Reworked on review comments received
-> Adjust the fix to let driver explicitly kick off new down request
when mst irq event is handled and acked
-> Adjust the commit message
Changes since v2:
* Adjust the commit message
* Adjust the naming of the divided 2 functions and add a new input
parameter "ack".
* Adjust code flow as per review comments.
Changes since v3:
* Update the function description of drm_dp_mst_hpd_irq_handle_event
Changes since v4:
* Change ack of drm_dp_mst_hpd_irq_handle_event() to be an array align
the size of esi[]
Signed-off-by: Wayne Lin
Cc: sta...@vger.kernel.org
---
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 32 +--
drivers/gpu/drm/display/drm_dp_mst_topology.c | 54 ---
drivers/gpu/drm/i915/display/intel_dp.c | 7 +--
drivers/gpu/drm/nouveau/dispnv50/disp.c | 12 +++--
include/drm/display/drm_dp_mst_helper.h | 7 ++-
5 files changed, 81 insertions(+), 31 deletions(-)
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index d5cec03eaa8d..ec629b4037e4 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -3263,6 +3263,7 @@ static void dm_handle_mst_sideband_msg(struct
amdgpu_dm_connector *aconnector)
while (dret == dpcd_bytes_to_read &&
process_count < max_process_count) {
+ u8 ack[DP_PSR_ERROR_STATUS - DP_SINK_COUNT_ESI] = {};
u8 retry;
dret = 0;
@@ -3271,28 +3272,29 @@ static void dm_handle_mst_sideband_msg(struct
amdgpu_dm_connector *aconnector)
DRM_DEBUG_DRIVER("ESI %02x %02x %02x\n", esi[0], esi[1],
esi[2]);
/* handle HPD short pulse irq */
if (aconnector->mst_mgr.mst_state)
- drm_dp_mst_hpd_irq(
- >mst_mgr,
- esi,
- _irq_handled);
+ drm_dp_mst_hpd_irq_handle_event(>mst_mgr,
+ esi,
+ ack,
+ _irq_handled);
if (new_irq_handled) {
/* ACK at DPCD to notify down stream */
- const int ack_dpcd_bytes_to_write =
- dpcd_bytes_to_read - 1;
-
for (retry = 0; retry < 3; retry++) {
- u8 wret;
-
- wret = drm_dp_dpcd_write(
- >dm_dp_aux.aux,
- dpcd_addr + 1,
- [1],
- ack_dpcd_bytes_to_write);
- if (wret == ack_dpcd_bytes_to_write)
+ ssize_t wret;
+
+ wret =
drm_dp_dpcd_writeb(>dm_dp_aux.aux,
+ dpcd_addr + 1,
+ ack[1]);
+ if (wret == 1)
break;
}
+ if (retry == 3) {
+ DRM_ERROR("Failed to ack MST event.\n");
+ return;
+ }
+
+
drm_dp_mst_hpd_irq_send_new_request(>mst_mgr);
/* check if there is new irq to be handled */
dret = drm_dp_dpcd_read(
[Intel-gfx] [PULL] drm-intel-next #2 for v6.5
Hi Dave & Daniel - This is the last drm-intel-next feature pull for v6.5. Fairly small, as the previous one was this week too. I guess the highlight is the removal of the last flush_scheduled_work() user in kernel, so Tetsuo can proceed to remove it altogether once this lands upstream. BR, Jani. drm-intel-next-2023-06-10: drm/i915 feature pull #2 for v6.5: Features and functionality: - Meteorlake PM demand (Vinod, Mika) - Switch to dedicated workqueues to stop using flush_scheduled_work() (Luca) Refactoring and cleanups: - Move display runtime init under display/ (Matt) - Async flip error message clarifications (Arun) Fixes: - Remove 10bit gamma on desktop gen3 parts, they don't support it (Ville) - Fix driver probe error handling if driver creation fails (Matt) - Fix all -Wunused-but-set-variable warnings, and enable it for i915 (Jani) - Stop using edid_blob_ptr (Jani) - Fix log level for "CDS interlane align done" (Khaled) - Fix an unnecessary include prefix (Matt) Merges: - Backmerge drm-next to sync with drm-intel-gt-next (Jani) BR, Jani. The following changes since commit ba57b9b11f78530146f02b776854b2b6b6d344a4: Merge tag 'drm-intel-gt-next-2023-06-08' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2023-06-09 16:43:36 +1000) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2023-06-10 for you to fetch changes up to 69f06e4fa098420e94f6970332e84f0ed493271c: Merge drm/drm-next into drm-intel-next (2023-06-10 10:04:00 +0300) drm/i915 feature pull #2 for v6.5: Features and functionality: - Meteorlake PM demand (Vinod, Mika) - Switch to dedicated workqueues to stop using flush_scheduled_work() (Luca) Refactoring and cleanups: - Move display runtime init under display/ (Matt) - Async flip error message clarifications (Arun) Fixes: - Remove 10bit gamma on desktop gen3 parts, they don't support it (Ville) - Fix driver probe error handling if driver creation fails (Matt) - Fix all -Wunused-but-set-variable warnings, and enable it for i915 (Jani) - Stop using edid_blob_ptr (Jani) - Fix log level for "CDS interlane align done" (Khaled) - Fix an unnecessary include prefix (Matt) Merges: - Backmerge drm-next to sync with drm-intel-gt-next (Jani) Arun R Murthy (1): drm/i915/display: Print useful information on error Jani Nikula (16): drm/i915/debugfs: stop using edid_blob_ptr drm/i915/plane: warn on non-zero plane offset drm/i915/ddi: drop unused but set variable intel_dp drm/i915/dsi: drop unused but set variable data drm/i915/dsi: drop unused but set variable vbp drm/i915/dpll: drop unused but set variables bestn and bestm1 drm/i915/fb: drop unused but set variable cpp drm/i915/irq: drop unused but set variable tmp drm/i915/gt/uc: drop unused but set variable sseu drm/i915/gem: drop unused but set variable unpinned drm/i915/gem: annotate maybe unused but set variable c drm/i915/selftest: annotate maybe unused but set variable unused drm/i915: annotate maybe unused but set intel_plane_state variables drm/i915: annotate maybe unused but set intel_crtc_state variables drm/i915: re-enable -Wunused-but-set-variable Merge drm/drm-next into drm-intel-next Khaled Almahallawy (1): drm/i915/dp: Fix log level for "CDS interlane align done" Luca Coelho (3): drm/i915: use pointer to i915 instead of rpm in wakeref drm/i915: add a dedicated workqueue inside drm_i915_private drm/i915/selftests: add local workqueue for SW fence selftest Matt Roper (3): drm/i915/display: Extract display init from intel_device_info_runtime_init drm/i915: Fix error handling if driver creation fails during probe drm/i915/display: Include of display limits doesn't need 'display/' Mika Kahola (1): drm/i915/mtl: Add support for PM DEMAND Ville Syrjälä (1): drm/i915: No 10bit gamma on desktop gen3 parts Vinod Govindapillai (6): drm/i915: fix the derating percentage for MTL drm/i915: update the QGV point frequency calculations drm/i915: store the peak bw per QGV point drm/i915: extract intel_bw_check_qgv_points() drm/i915: modify max_bw to return index to intel_bw_info drm/i915/mtl: find the best QGV point for the SAGV configuration Zhi Wang (1): drm/i915/gvt: remove unused variable gma_bottom in command parser drivers/gpu/drm/i915/Makefile | 3 +- drivers/gpu/drm/i915/display/i9xx_plane.c | 3 + drivers/gpu/drm/i915/display/intel_atomic_plane.c | 2 +- drivers/gpu/drm/i915/display/intel_bw.c| 345 drivers/gpu/drm/i915/display/intel_bw.h| 6 + drivers/gpu/drm/i915/display/intel_cdclk.c | 2 +- drivers/gpu/drm/i915/display/intel_ddi.c
Re: [Intel-gfx] [PATCH v5] drm/i915: avoid flush_scheduled_work() usage
On Mon, 22 May 2023, Tetsuo Handa wrote:
> Like commit c4f135d643823a86 ("workqueue: Wrap flush_workqueue() using a
> macro") says, flush_scheduled_work() is dangerous and will be forbidden.
>
> i915 became the last flush_scheduled_work() user, but developers cannot
> find time for auditing which work items does this flush_scheduled_work()
> need to wait.
>
> Therefore, for now let's start with blind/mechanical conversion within
> the whole drivers/gpu/drm/i915/ directory, based on an assumption that
> i915 does not need to wait for work items outside of this directory.
I'll note also here that I've just pushed Luca's series [1] to switch
i915 to internal device specific workqueues, for the same effect as this
one.
Thanks,
Jani.
[1] https://patchwork.freedesktop.org/series/118947/
--
Jani Nikula, Intel Open Source Graphics Center
Re: [Intel-gfx] [PATCH v6 0/3] drm/i915: implement internal workqueues
On Thu, 08 Jun 2023, Jani Nikula wrote: > This is v6 of [1], creating i915->unordered_wq also for mock devices. Pushed to drm-intel-next. Thanks for the patches and review. This also superseeds [1], and finally removes the last user of flush_scheduled_work(). Tetsuo, this will make its way to v6.5. Apologies about all the procrastination and delay. BR, Jani. [1] https://patchwork.freedesktop.org/patch/msgid/47c5fe59-faec-8eb6-7f3c-f76a4bb0f...@i-love.sakura.ne.jp > > BR, > Jani. > > [1] https://patchwork.freedesktop.org/series/118947/ > > > Luca Coelho (3): > drm/i915: use pointer to i915 instead of rpm in wakeref > drm/i915: add a dedicated workqueue inside drm_i915_private > drm/i915/selftests: add local workqueue for SW fence selftest > > drivers/gpu/drm/i915/display/intel_display.c | 5 ++-- > .../drm/i915/display/intel_display_driver.c | 2 +- > drivers/gpu/drm/i915/display/intel_dmc.c | 2 +- > drivers/gpu/drm/i915/display/intel_dp.c | 2 +- > .../drm/i915/display/intel_dp_link_training.c | 3 ++- > drivers/gpu/drm/i915/display/intel_drrs.c | 4 +++- > drivers/gpu/drm/i915/display/intel_fbc.c | 2 +- > drivers/gpu/drm/i915/display/intel_fbdev.c| 3 ++- > drivers/gpu/drm/i915/display/intel_hdcp.c | 23 +++ > drivers/gpu/drm/i915/display/intel_hotplug.c | 18 ++- > drivers/gpu/drm/i915/display/intel_opregion.c | 3 ++- > drivers/gpu/drm/i915/display/intel_pps.c | 4 +++- > drivers/gpu/drm/i915/display/intel_psr.c | 8 --- > drivers/gpu/drm/i915/gt/intel_engine_pm.c | 4 +--- > .../drm/i915/gt/intel_execlists_submission.c | 5 ++-- > .../gpu/drm/i915/gt/intel_gt_buffer_pool.c| 10 > drivers/gpu/drm/i915/gt/intel_gt_irq.c| 2 +- > drivers/gpu/drm/i915/gt/intel_gt_pm.c | 2 +- > drivers/gpu/drm/i915/gt/intel_gt_requests.c | 10 > drivers/gpu/drm/i915/gt/intel_reset.c | 2 +- > drivers/gpu/drm/i915/gt/intel_rps.c | 20 > drivers/gpu/drm/i915/gt/selftest_engine_cs.c | 2 +- > drivers/gpu/drm/i915/i915_driver.c| 13 +++ > drivers/gpu/drm/i915/i915_drv.h | 10 > drivers/gpu/drm/i915/i915_request.c | 2 +- > drivers/gpu/drm/i915/intel_runtime_pm.c | 2 +- > drivers/gpu/drm/i915/intel_wakeref.c | 22 ++ > drivers/gpu/drm/i915/intel_wakeref.h | 12 +- > .../gpu/drm/i915/selftests/i915_sw_fence.c| 16 ++--- > .../gpu/drm/i915/selftests/mock_gem_device.c | 7 ++ > 30 files changed, 143 insertions(+), 77 deletions(-) -- Jani Nikula, Intel Open Source Graphics Center
[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Fix a VMA UAF for multi-gt platform (rev7)
== Series Details == Series: drm/i915: Fix a VMA UAF for multi-gt platform (rev7) URL : https://patchwork.freedesktop.org/series/118887/ State : success == Summary == CI Bug Log - changes from CI_DRM_13253_full -> Patchwork_118887v7_full Summary --- **SUCCESS** No regressions found. Participating hosts (7 -> 7) -- No changes in participating hosts Known issues Here are the changes found in Patchwork_118887v7_full that come from known issues: ### IGT changes ### Issues hit * igt@gem_busy@close-race: - shard-snb: [PASS][1] -> [ABORT][2] ([i915#6016]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-snb1/igt@gem_b...@close-race.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-snb2/igt@gem_b...@close-race.html * igt@gem_exec_fair@basic-pace-solo@rcs0: - shard-glk: NOTRUN -> [FAIL][3] ([i915#2842]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-glk6/igt@gem_exec_fair@basic-pace-s...@rcs0.html * igt@gem_exec_reloc@basic-scanout@bcs0: - shard-snb: [PASS][4] -> [SKIP][5] ([fdo#109271]) +1 similar issue [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-snb7/igt@gem_exec_reloc@basic-scan...@bcs0.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-snb2/igt@gem_exec_reloc@basic-scan...@bcs0.html * igt@gem_exec_reloc@basic-scanout@vcs0: - shard-snb: [PASS][6] -> [SKIP][7] ([fdo#109271] / [i915#4579]) [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-snb7/igt@gem_exec_reloc@basic-scan...@vcs0.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-snb2/igt@gem_exec_reloc@basic-scan...@vcs0.html * igt@gem_lmem_swapping@heavy-multi: - shard-apl: NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#4613]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-apl6/igt@gem_lmem_swapp...@heavy-multi.html * igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp: - shard-apl: NOTRUN -> [SKIP][9] ([fdo#109271] / [i915#1937] / [i915#4579]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-apl6/igt@i915_pm_lpsp@kms-l...@kms-lpsp-dp.html * igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs: - shard-glk: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#3886]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-glk6/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_mc_ccs.html * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions: - shard-glk: [PASS][11] -> [FAIL][12] ([i915#2346]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13253/shard-glk5/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-glk2/igt@kms_cursor_leg...@flip-vs-cursor-atomic-transitions.html * igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscaling@pipe-a-valid-mode: - shard-apl: NOTRUN -> [SKIP][13] ([fdo#109271] / [i915#4579]) +1 similar issue [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-apl6/igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscal...@pipe-a-valid-mode.html * igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-valid-mode: - shard-glk: NOTRUN -> [SKIP][14] ([fdo#109271] / [i915#4579]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-glk6/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscal...@pipe-a-valid-mode.html * igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-shrfb-draw-mmap-cpu: - shard-apl: NOTRUN -> [SKIP][15] ([fdo#109271]) +17 similar issues [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-apl6/igt@kms_frontbuffer_track...@psr-2p-scndscrn-pri-shrfb-draw-mmap-cpu.html * igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-a-vga-1: - shard-snb: NOTRUN -> [SKIP][16] ([fdo#109271]) +12 similar issues [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-snb7/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotat...@pipe-a-vga-1.html * igt@kms_plane_scaling@plane-upscale-with-modifiers-factor-0-25@pipe-b-vga-1: - shard-snb: NOTRUN -> [SKIP][17] ([fdo#109271] / [i915#4579]) +6 similar issues [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_118887v7/shard-snb7/igt@kms_plane_scaling@plane-upscale-with-modifiers-factor-0...@pipe-b-vga-1.html * igt@kms_vblank@pipe-d-wait-busy-hang: - shard-glk: NOTRUN -> [SKIP][18] ([fdo#109271]) +15 similar issues [18]:
