[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: vblank stuff (rev3)

2023-03-04 Thread Patchwork
== Series Details ==

Series: drm/i915: vblank stuff (rev3)
URL   : https://patchwork.freedesktop.org/series/112170/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_12799_full -> Patchwork_112170v3_full


Summary
---

  **FAILURE**

  Serious unknown changes coming with Patchwork_112170v3_full absolutely need 
to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_112170v3_full, please notify your bug team to allow 
them
  to document this new failure mode, which will reduce false positives in CI.

  

Participating hosts (19 -> 19)
--

  No changes in participating hosts

Possible new issues
---

  Here are the unknown changes that may have been introduced in 
Patchwork_112170v3_full:

### IGT changes ###

 Possible regressions 

  * igt@kms_cursor_legacy@cursorb-vs-flipb-toggle:
- shard-glk:  [PASS][1] -> [TIMEOUT][2] +2 similar issues
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12799/shard-glk5/igt@kms_cursor_leg...@cursorb-vs-flipb-toggle.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112170v3/shard-glk8/igt@kms_cursor_leg...@cursorb-vs-flipb-toggle.html

  * igt@kms_plane@pixel-format:
- shard-glk:  NOTRUN -> [TIMEOUT][3]
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112170v3/shard-glk8/igt@kms_pl...@pixel-format.html

  
 Warnings 

  * igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-180:
- shard-glk:  [SKIP][4] ([fdo#109271]) -> [TIMEOUT][5] +2 similar 
issues
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12799/shard-glk5/igt@kms_big...@yf-tiled-max-hw-stride-64bpp-rotate-180.html
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112170v3/shard-glk8/igt@kms_big...@yf-tiled-max-hw-stride-64bpp-rotate-180.html

  
 Suppressed 

  The following results come from untrusted machines, tests, or statuses.
  They do not affect the overall result.

  * igt@gem_create@create-clear@smem0:
- {shard-rkl}:NOTRUN -> [ABORT][6]
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112170v3/shard-rkl-4/igt@gem_create@create-cl...@smem0.html

  * igt@gem_create@create-ext-cpu-access-big:
- {shard-dg2-6}:  NOTRUN -> [ABORT][7] +1 similar issue
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112170v3/shard-dg2-6/igt@gem_cre...@create-ext-cpu-access-big.html

  * igt@kms_content_protection@srm@pipe-a-dp-2:
- {shard-dg2-12}: NOTRUN -> [TIMEOUT][8] +1 similar issue
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112170v3/shard-dg2-12/igt@kms_content_protection@s...@pipe-a-dp-2.html

  * 
{igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-20x20@pipe-c-dp-2}:
- {shard-dg2-12}: NOTRUN -> [SKIP][9] +2 similar issues
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112170v3/shard-dg2-12/igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-20...@pipe-c-dp-2.html

  * igt@kms_vblank@pipe-c-ts-continuation-modeset-hang:
- {shard-dg2-11}: NOTRUN -> [FAIL][10] +2 similar issues
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112170v3/shard-dg2-11/igt@kms_vbl...@pipe-c-ts-continuation-modeset-hang.html

  
New tests
-

  New tests have been introduced between CI_DRM_12799_full and 
Patchwork_112170v3_full:

### New IGT tests (10) ###

  * igt@kms_cursor_crc@cursor-onscreen-64x21@pipe-d-dp-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@plain-flip-ts-check@d-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_setmode@basic@pipe-a-dp-1-pipe-b-dp-3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_setmode@basic@pipe-a-dp-2-pipe-b-dp-3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_setmode@basic@pipe-a-dp-2-pipe-b-dp-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_setmode@basic@pipe-a-dp-3-pipe-b-dp-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_setmode@basic@pipe-b-dp-1-pipe-a-dp-3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_setmode@basic@pipe-b-dp-2-pipe-a-dp-3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_setmode@basic@pipe-b-dp-2-pipe-a-dp-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_setmode@basic@pipe-b-dp-3-pipe-a-dp-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  

Known issues


  Here are the changes found in Patchwork_112170v3_full that come from known 
issues:

### IGT changes ###

 Issues hit 

  * igt@api_intel_bb@crc32:
- shard-tglu-9:   NOTRUN -> [SKIP][11] ([i915#6230])
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112170v3/shard-tglu-9/igt@api_intel...@crc32.html

  * igt@debugfs_test@basic-hwmon:
- shard-tglu-9:   NOTRUN -> [SKIP][12] ([i915#7456]

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display: split out DSC and DSS registers

2023-03-04 Thread Patchwork
== Series Details ==

Series: drm/i915/display: split out DSC and DSS registers
URL   : https://patchwork.freedesktop.org/series/114523/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_12799_full -> Patchwork_114523v1_full


Summary
---

  **FAILURE**

  Serious unknown changes coming with Patchwork_114523v1_full absolutely need 
to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_114523v1_full, please notify your bug team to allow 
them
  to document this new failure mode, which will reduce false positives in CI.

  

Participating hosts (19 -> 19)
--

  No changes in participating hosts

Possible new issues
---

  Here are the unknown changes that may have been introduced in 
Patchwork_114523v1_full:

### IGT changes ###

 Possible regressions 

  * igt@i915_pm_rps@reset:
- shard-snb:  [PASS][1] -> [DMESG-FAIL][2]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12799/shard-snb1/igt@i915_pm_...@reset.html
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114523v1/shard-snb5/igt@i915_pm_...@reset.html

  
 Suppressed 

  The following results come from untrusted machines, tests, or statuses.
  They do not affect the overall result.

  * igt@gem_create@create-clear@smem0:
- {shard-rkl}:NOTRUN -> [ABORT][3]
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114523v1/shard-rkl-4/igt@gem_create@create-cl...@smem0.html

  * igt@gem_create@create-ext-cpu-access-big:
- {shard-dg2-7}:  NOTRUN -> [ABORT][4]
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114523v1/shard-dg2-7/igt@gem_cre...@create-ext-cpu-access-big.html

  * igt@gem_eio@hibernate:
- {shard-dg2-6}:  NOTRUN -> [ABORT][5]
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114523v1/shard-dg2-6/igt@gem_...@hibernate.html

  * igt@kms_content_protection@srm@pipe-a-dp-2:
- {shard-dg2-12}: NOTRUN -> [TIMEOUT][6]
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114523v1/shard-dg2-12/igt@kms_content_protection@s...@pipe-a-dp-2.html

  * igt@kms_flip@flip-vs-blocking-wf-vblank@d-dp3:
- {shard-dg2-11}: NOTRUN -> [FAIL][7] +5 similar issues
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114523v1/shard-dg2-11/igt@kms_flip@flip-vs-blocking-wf-vbl...@d-dp3.html

  * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-mmap-cpu:
- {shard-dg2-12}: NOTRUN -> [FAIL][8]
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114523v1/shard-dg2-12/igt@kms_frontbuffer_track...@fbc-1p-primscrn-pri-indfb-draw-mmap-cpu.html

  * igt@kms_frontbuffer_tracking@fbc-badstride:
- {shard-dg2-1}:  NOTRUN -> [FAIL][9]
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114523v1/shard-dg2-1/igt@kms_frontbuffer_track...@fbc-badstride.html

  
New tests
-

  New tests have been introduced between CI_DRM_12799_full and 
Patchwork_114523v1_full:

### New IGT tests (37) ###

  * igt@kms_cursor_crc@cursor-onscreen-128x42@pipe-d-dp-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_cursor_crc@cursor-random-64x64@pipe-d-dp-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_cursor_crc@cursor-suspend@pipe-d-dp-4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@ab-dp2-dp3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@ab-dp2-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@ab-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@ac-dp2-dp3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@ac-dp2-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@ac-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@ad-dp2-dp3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@ad-dp2-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@ad-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@bc-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@bd-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible@cd-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-plain-flip-ts-check-interruptible@ab-dp2-dp3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * 

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/mtl: Extend Wa_14017073508 in suspend/resume flow

2023-03-04 Thread Patchwork
== Series Details ==

Series: drm/i915/mtl: Extend Wa_14017073508 in suspend/resume flow
URL   : https://patchwork.freedesktop.org/series/114657/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_12810 -> Patchwork_114657v1


Summary
---

  **SUCCESS**

  No regressions found.

  External URL: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/index.html

Participating hosts (39 -> 37)
--

  Missing(2): bat-adls-5 bat-dg1-6 

Known issues


  Here are the changes found in Patchwork_114657v1 that come from known issues:

### IGT changes ###

 Issues hit 

  * igt@i915_selftest@live@slpc:
- bat-rpls-2: NOTRUN -> [DMESG-FAIL][1] ([i915#6367] / [i915#7913])
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/bat-rpls-2/igt@i915_selftest@l...@slpc.html
- bat-rpls-1: [PASS][2] -> [DMESG-FAIL][3] ([i915#6367])
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12810/bat-rpls-1/igt@i915_selftest@l...@slpc.html
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/bat-rpls-1/igt@i915_selftest@l...@slpc.html

  * igt@kms_chamelium_hpd@common-hpd-after-suspend:
- bat-rpls-2: NOTRUN -> [SKIP][4] ([i915#7828])
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/bat-rpls-2/igt@kms_chamelium_...@common-hpd-after-suspend.html
- bat-rpls-1: NOTRUN -> [SKIP][5] ([i915#7828])
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/bat-rpls-1/igt@kms_chamelium_...@common-hpd-after-suspend.html

  * igt@kms_pipe_crc_basic@suspend-read-crc:
- bat-rpls-1: NOTRUN -> [SKIP][6] ([i915#1845])
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/bat-rpls-1/igt@kms_pipe_crc_ba...@suspend-read-crc.html
- bat-rpls-2: NOTRUN -> [SKIP][7] ([i915#1845])
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/bat-rpls-2/igt@kms_pipe_crc_ba...@suspend-read-crc.html

  
 Possible fixes 

  * igt@gem_exec_suspend@basic-s3@smem:
- bat-rpls-1: [ABORT][8] ([i915#6687] / [i915#7978]) -> [PASS][9]
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12810/bat-rpls-1/igt@gem_exec_suspend@basic...@smem.html
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/bat-rpls-1/igt@gem_exec_suspend@basic...@smem.html

  * igt@i915_selftest@live@gt_heartbeat:
- fi-apl-guc: [DMESG-FAIL][10] ([i915#5334]) -> [PASS][11]
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12810/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html

  * igt@i915_selftest@live@migrate:
- bat-adlp-6: [DMESG-FAIL][12] ([i915#7699]) -> [PASS][13]
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12810/bat-adlp-6/igt@i915_selftest@l...@migrate.html
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/bat-adlp-6/igt@i915_selftest@l...@migrate.html

  * igt@i915_selftest@live@requests:
- bat-rpls-2: [ABORT][14] ([i915#7694] / [i915#7913] / [i915#7982]) 
-> [PASS][15]
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12810/bat-rpls-2/igt@i915_selftest@l...@requests.html
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/bat-rpls-2/igt@i915_selftest@l...@requests.html

  
  [i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
  [i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
  [i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
  [i915#6687]: https://gitlab.freedesktop.org/drm/intel/issues/6687
  [i915#7694]: https://gitlab.freedesktop.org/drm/intel/issues/7694
  [i915#7699]: https://gitlab.freedesktop.org/drm/intel/issues/7699
  [i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
  [i915#7913]: https://gitlab.freedesktop.org/drm/intel/issues/7913
  [i915#7978]: https://gitlab.freedesktop.org/drm/intel/issues/7978
  [i915#7982]: https://gitlab.freedesktop.org/drm/intel/issues/7982


Build changes
-

  * Linux: CI_DRM_12810 -> Patchwork_114657v1

  CI-20190529: 20190529
  CI_DRM_12810: 030c24d089b9c566f8cf9e15f49fc4e298396740 @ 
git://anongit.freedesktop.org/gfx-ci/linux
  IGT_7180: b6b1ceb4fc4d8f83a9540e4628a6c2648514bb19 @ 
https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  Patchwork_114657v1: 030c24d089b9c566f8cf9e15f49fc4e298396740 @ 
git://anongit.freedesktop.org/gfx-ci/linux


### Linux commits

6ef4d450e532 drm/i915/mtl: Extend Wa_14017073508 in suspend/resume flow

== Logs ==

For more details see: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114657v1/index.html


[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/mtl: Extend Wa_14017073508 in suspend/resume flow

2023-03-04 Thread Patchwork
== Series Details ==

Series: drm/i915/mtl: Extend Wa_14017073508 in suspend/resume flow
URL   : https://patchwork.freedesktop.org/series/114657/
State : warning

== Summary ==

Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.




[Intel-gfx] [PATCH] drm/i915/mtl: Extend Wa_14017073508 in suspend/resume flow

2023-03-04 Thread Badal Nilawar
During suspend resume flow it was seen that lots forcewakes
are taken and released for media. So to avoid HANG due to MC6
entry/exit while accessing media applied Wa_14017073508 in
suspend/resume flow.

Signed-off-by: Badal Nilawar 
---
 drivers/gpu/drm/i915/gem/i915_gem_pm.c   |  6 -
 drivers/gpu/drm/i915/gt/intel_gt_pm.c| 32 
 drivers/gpu/drm/i915/gt/intel_gt_pm.h|  3 +++
 drivers/gpu/drm/i915/gt/intel_gt_types.h |  1 +
 drivers/gpu/drm/i915/i915_driver.c   | 32 
 5 files changed, 62 insertions(+), 12 deletions(-)

diff --git a/drivers/gpu/drm/i915/gem/i915_gem_pm.c 
b/drivers/gpu/drm/i915/gem/i915_gem_pm.c
index 0d812f4d787d..60deac41104d 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_pm.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_pm.c
@@ -160,8 +160,12 @@ void i915_gem_suspend_late(struct drm_i915_private *i915)
 * machine in an unusable condition.
 */
 
-   for_each_gt(gt, i915, i)
+   for_each_gt(gt, i915, i) {
+   /* Wa_14017073508: mtl */
+   mtl_media_busy(gt);
intel_gt_suspend_late(gt);
+   mtl_media_idle(gt);
+   }
 
spin_lock_irqsave(&i915->mm.obj_lock, flags);
for (phase = phases; *phase; phase++) {
diff --git a/drivers/gpu/drm/i915/gt/intel_gt_pm.c 
b/drivers/gpu/drm/i915/gt/intel_gt_pm.c
index cef3d6f5c34e..1f3bf1cf0421 100644
--- a/drivers/gpu/drm/i915/gt/intel_gt_pm.c
+++ b/drivers/gpu/drm/i915/gt/intel_gt_pm.c
@@ -26,24 +26,34 @@
 
 #define I915_GT_SUSPEND_IDLE_TIMEOUT (HZ / 2)
 
-static void mtl_media_busy(struct intel_gt *gt)
+void mtl_media_busy(struct intel_gt *gt)
 {
/* Wa_14017073508: mtl */
-   if (IS_MTL_GRAPHICS_STEP(gt->i915, P, STEP_A0, STEP_B0) &&
+   if (gt && IS_MTL_GRAPHICS_STEP(gt->i915, P, STEP_A0, STEP_B0) &&
gt->type == GT_MEDIA)
-   snb_pcode_write_p(gt->uncore, PCODE_MBOX_GT_STATE,
- PCODE_MBOX_GT_STATE_MEDIA_BUSY,
- PCODE_MBOX_GT_STATE_DOMAIN_MEDIA, 0);
+   if (!atomic_inc_not_zero(>->media_wakeref)) {
+   drm_err(>->i915->drm, "Media busy\n");
+   snb_pcode_write_p(gt->uncore, PCODE_MBOX_GT_STATE,
+ PCODE_MBOX_GT_STATE_MEDIA_BUSY,
+ PCODE_MBOX_GT_STATE_DOMAIN_MEDIA, 0);
+   atomic_inc(>->media_wakeref);
+   }
 }
 
-static void mtl_media_idle(struct intel_gt *gt)
+void mtl_media_idle(struct intel_gt *gt)
 {
/* Wa_14017073508: mtl */
-   if (IS_MTL_GRAPHICS_STEP(gt->i915, P, STEP_A0, STEP_B0) &&
-   gt->type == GT_MEDIA)
-   snb_pcode_write_p(gt->uncore, PCODE_MBOX_GT_STATE,
- PCODE_MBOX_GT_STATE_MEDIA_NOT_BUSY,
- PCODE_MBOX_GT_STATE_DOMAIN_MEDIA, 0);
+   if (gt && IS_MTL_GRAPHICS_STEP(gt->i915, P, STEP_A0, STEP_B0) &&
+   gt->type == GT_MEDIA) {
+   WARN_ON(atomic_read(>->media_wakeref) <= 0);
+   if (!atomic_add_unless(>->media_wakeref, -1, 1)) {
+   drm_err(>->i915->drm, "Media idle\n");
+   snb_pcode_write_p(gt->uncore, PCODE_MBOX_GT_STATE,
+ PCODE_MBOX_GT_STATE_MEDIA_NOT_BUSY,
+ PCODE_MBOX_GT_STATE_DOMAIN_MEDIA, 0);
+   atomic_dec(>->media_wakeref);
+   }
+   }
 }
 
 static void user_forcewake(struct intel_gt *gt, bool suspend)
diff --git a/drivers/gpu/drm/i915/gt/intel_gt_pm.h 
b/drivers/gpu/drm/i915/gt/intel_gt_pm.h
index 6c9a46452364..43ffabf9babe 100644
--- a/drivers/gpu/drm/i915/gt/intel_gt_pm.h
+++ b/drivers/gpu/drm/i915/gt/intel_gt_pm.h
@@ -89,4 +89,7 @@ static inline bool is_mock_gt(const struct intel_gt *gt)
return I915_SELFTEST_ONLY(gt->awake == -ENODEV);
 }
 
+void mtl_media_busy(struct intel_gt *gt);
+void mtl_media_idle(struct intel_gt *gt);
+
 #endif /* INTEL_GT_PM_H */
diff --git a/drivers/gpu/drm/i915/gt/intel_gt_types.h 
b/drivers/gpu/drm/i915/gt/intel_gt_types.h
index f08c2556aa25..321ccfef4028 100644
--- a/drivers/gpu/drm/i915/gt/intel_gt_types.h
+++ b/drivers/gpu/drm/i915/gt/intel_gt_types.h
@@ -145,6 +145,7 @@ struct intel_gt {
 
struct intel_wakeref wakeref;
atomic_t user_wakeref;
+   atomic_t media_wakeref;
 
struct list_head closed_vma;
spinlock_t closed_lock; /* guards the list of closed_vma */
diff --git a/drivers/gpu/drm/i915/i915_driver.c 
b/drivers/gpu/drm/i915/i915_driver.c
index 8bc76dede332..c7625ea28022 100644
--- a/drivers/gpu/drm/i915/i915_driver.c
+++ b/drivers/gpu/drm/i915/i915_driver.c
@@ -327,6 +327,8 @@ static int i915_driver_mmio_probe(struct drm_i915_private 
*dev_priv)
intel_gmch_bar_setup(dev_priv);
intel_device_info_runtime_init(dev_priv);
 
+   /* Wa_1401

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dsi: fix DSS CTL register offsets for TGL+

2023-03-04 Thread Patchwork
== Series Details ==

Series: drm/i915/dsi: fix DSS CTL register offsets for TGL+
URL   : https://patchwork.freedesktop.org/series/114522/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_12799_full -> Patchwork_114522v1_full


Summary
---

  **SUCCESS**

  No regressions found.

  

Participating hosts (19 -> 19)
--

  No changes in participating hosts

Possible new issues
---

  Here are the unknown changes that may have been introduced in 
Patchwork_114522v1_full:

### IGT changes ###

 Suppressed 

  The following results come from untrusted machines, tests, or statuses.
  They do not affect the overall result.

  * igt@gem_create@create-clear@smem0:
- {shard-rkl}:NOTRUN -> [ABORT][1]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-rkl-2/igt@gem_create@create-cl...@smem0.html

  * igt@gem_create@create-ext-cpu-access-big:
- {shard-dg2-6}:  NOTRUN -> [ABORT][2]
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-dg2-6/igt@gem_cre...@create-ext-cpu-access-big.html

  * igt@gem_eio@hibernate:
- {shard-dg2-8}:  NOTRUN -> [ABORT][3]
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-dg2-8/igt@gem_...@hibernate.html

  * igt@kms_content_protection@srm@pipe-a-dp-2:
- {shard-dg2-12}: NOTRUN -> [TIMEOUT][4]
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-dg2-12/igt@kms_content_protection@s...@pipe-a-dp-2.html

  * igt@kms_lease@empty_lease@pipe-a-hdmi-a-3:
- {shard-dg2-7}:  NOTRUN -> [ABORT][5]
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-dg2-7/igt@kms_lease@empty_le...@pipe-a-hdmi-a-3.html

  * igt@kms_lease@empty_lease@pipe-b-hdmi-a-3:
- {shard-dg2-7}:  NOTRUN -> [DMESG-WARN][6]
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-dg2-7/igt@kms_lease@empty_le...@pipe-b-hdmi-a-3.html

  
New tests
-

  New tests have been introduced between CI_DRM_12799_full and 
Patchwork_114522v1_full:

### New IGT tests (2) ###

  * igt@kms_cursor_edge_walk@128x128-left-edge@pipe-a-dp-2:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_cursor_edge_walk@128x128-left-edge@pipe-d-dp-2:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  

Known issues


  Here are the changes found in Patchwork_114522v1_full that come from known 
issues:

### IGT changes ###

 Issues hit 

  * igt@api_intel_bb@crc32:
- shard-tglu-10:  NOTRUN -> [SKIP][7] ([i915#6230])
   [7]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-tglu-10/igt@api_intel...@crc32.html

  * igt@drm_buddy@all-tests:
- shard-tglu-10:  NOTRUN -> [SKIP][8] ([i915#6433]) +1 similar issue
   [8]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-tglu-10/igt@drm_bu...@all-tests.html

  * igt@fbdev@info:
- shard-tglu-9:   NOTRUN -> [SKIP][9] ([i915#2582]) +1 similar issue
   [9]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-tglu-9/igt@fb...@info.html

  * igt@gem_ccs@ctrl-surf-copy:
- shard-tglu-9:   NOTRUN -> [SKIP][10] ([i915#3555] / [i915#5325])
   [10]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-tglu-9/igt@gem_...@ctrl-surf-copy.html

  * igt@gem_close_race@multigpu-basic-process:
- shard-tglu-10:  NOTRUN -> [SKIP][11] ([i915#7697])
   [11]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-tglu-10/igt@gem_close_r...@multigpu-basic-process.html

  * igt@gem_create@create-ext-cpu-access-big:
- shard-tglu-10:  NOTRUN -> [SKIP][12] ([i915#6335])
   [12]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-tglu-10/igt@gem_cre...@create-ext-cpu-access-big.html

  * igt@gem_ctx_persistence@process:
- shard-snb:  NOTRUN -> [SKIP][13] ([fdo#109271] / [i915#1099])
   [13]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-snb1/igt@gem_ctx_persiste...@process.html

  * igt@gem_exec_capture@capture-invisible@smem0:
- shard-tglu-9:   NOTRUN -> [SKIP][14] ([i915#6334])
   [14]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-tglu-9/igt@gem_exec_capture@capture-invisi...@smem0.html

  * igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-tglu-10:  NOTRUN -> [FAIL][15] ([i915#2842])
   [15]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-tglu-10/igt@gem_exec_fair@basic-none-r...@rcs0.html

  * igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl:  [PASS][16] -> [FAIL][17] ([i915#2842])
   [16]: 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12799/shard-apl3/igt@gem_exec_fair@basic-none-s...@rcs0.html
   [17]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114522v1/shard-apl4/igt@gem_exec_fair@basic-none-s...@rcs0.html

  * igt@gem_exec_suspend@basic-s4-devices@smem:

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: pm cleanups, rename to clock gating

2023-03-04 Thread Patchwork
== Series Details ==

Series: drm/i915: pm cleanups, rename to clock gating
URL   : https://patchwork.freedesktop.org/series/114519/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_12799_full -> Patchwork_114519v1_full


Summary
---

  **SUCCESS**

  No regressions found.

  

Participating hosts (19 -> 19)
--

  No changes in participating hosts

Possible new issues
---

  Here are the unknown changes that may have been introduced in 
Patchwork_114519v1_full:

### IGT changes ###

 Possible regressions 

  * igt@kms_atomic_transition@modeset-transition-nonblocking@3x-outputs (NEW):
- {shard-dg2-11}: NOTRUN -> [FAIL][1]
   [1]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114519v1/shard-dg2-11/igt@kms_atomic_transition@modeset-transition-nonblock...@3x-outputs.html

  
 Suppressed 

  The following results come from untrusted machines, tests, or statuses.
  They do not affect the overall result.

  * igt@gem_create@create-ext-cpu-access-big:
- {shard-dg2-10}: NOTRUN -> [ABORT][2]
   [2]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114519v1/shard-dg2-10/igt@gem_cre...@create-ext-cpu-access-big.html

  * igt@gem_eio@hibernate:
- {shard-dg2-3}:  NOTRUN -> [ABORT][3]
   [3]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114519v1/shard-dg2-3/igt@gem_...@hibernate.html

  * igt@kms_async_flips@crc@pipe-b-dp-2:
- {shard-dg2-12}: NOTRUN -> [FAIL][4] +3 similar issues
   [4]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114519v1/shard-dg2-12/igt@kms_async_flips@c...@pipe-b-dp-2.html

  * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-mmap-cpu:
- {shard-dg2-6}:  NOTRUN -> [FAIL][5]
   [5]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114519v1/shard-dg2-6/igt@kms_frontbuffer_track...@fbc-1p-primscrn-pri-indfb-draw-mmap-cpu.html

  * igt@kms_frontbuffer_tracking@fbc-rgb565-draw-render:
- {shard-dg2-5}:  NOTRUN -> [FAIL][6]
   [6]: 
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114519v1/shard-dg2-5/igt@kms_frontbuffer_track...@fbc-rgb565-draw-render.html

  
New tests
-

  New tests have been introduced between CI_DRM_12799_full and 
Patchwork_114519v1_full:

### New IGT tests (41) ###

  * igt@kms_atomic_transition@modeset-transition-nonblocking@3x-outputs:
- Statuses : 1 fail(s)
- Exec time: [0.0] s

  * igt@kms_cursor_edge_walk@256x256-top-bottom@pipe-a-dp-2:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_cursor_edge_walk@256x256-top-bottom@pipe-d-dp-2:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@ab-dp2-dp3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@ab-dp2-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@ab-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@ac-dp2-dp3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@ac-dp2-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@ac-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@ad-dp2-dp3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@ad-dp2-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@ad-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@bc-dp2-dp3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@bc-dp2-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@bc-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@bd-dp2-dp3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@bd-dp2-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@bd-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@cd-dp2-dp3:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@cd-dp2-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-absolute-wf_vblank-interruptible@cd-dp3-dp4:
- Statuses : 1 pass(s)
- Exec time: [0.0] s

  * igt@kms_flip@2x-flip-vs-modeset-vs-hang@ab-dp2-dp3:
- Statuses :
- Exec time: [None] s

  * igt@kms_flip@2x-plain-flip@ab-dp2-dp3:
- Statuses : 1 pass(s

Re: [Intel-gfx] [PATCH v5 00/19] Add vfio_device cdev for iommufd support

2023-03-04 Thread Liu, Yi L
> From: Nicolin Chen 
> Sent: Saturday, March 4, 2023 3:01 PM
> 
> Oh. My test environment has been a single-core vCPU. So that
> doesn't happen to me. Can you try a vanilla QEMU branch that
> our nesting branch is rebased on? I took a branch from Yi as
> the baseline, while he might take from Eric for the rfcv3.

Yes, I took the qemu from Eric's rfcv3, just plus two commits to align the
uapi.

Regards
Yi Liu