Skip to contentSkip to conversation

drm/i915/gt: Do not use stolen on MTL

PATCH In review Nirmoy Das 7 participants 20 messages Jun 30, 2023 – Jul 12, 2023

Subsystems (3)
lore
Share & tools
lore

Nirmoy Das

author
#0 lore raw

PATCH 1/2 drm/i915/gt: Do not use stolen on MTL

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>
---
 drivers/gpu/drm/i915/gt/intel_gt.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/gt/intel_gt.c +1 -1
index 33a61046ba58..9f64d61dd5fc 100644
@@ -466,7 +466,7 @@ static int intel_gt_init_scratch(struct intel_gt *gt, unsigned int size)
 	obj = i915_gem_object_create_lmem(i915, size,
 					  I915_BO_ALLOC_VOLATILE |
 					  I915_BO_ALLOC_GPU_ONLY);
-	if (IS_ERR(obj))
+	if (IS_ERR(obj) && !IS_METEORLAKE(i915)) /* Wa_22018444074 */
 		obj = i915_gem_object_create_stolen(i915, size);
 	if (IS_ERR(obj))
 		obj = i915_gem_object_create_internal(i915, size);
Signature · 1 line
2.39.0
author
#1 lore raw

PATCH 2/2 drm/i915/display: Do not use stolen on MTL

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>
---
 drivers/gpu/drm/i915/display/intel_fbdev.c   | 2 ++
 drivers/gpu/drm/i915/display/intel_overlay.c | 7 ++++---
 2 files changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_fbdev.c +2 -0
index 1cc0ddc6a310..10e38d60f9ef 100644
@@ -182,6 +182,8 @@ static int intelfb_alloc(struct drm_fb_helper *helper,
 		obj = i915_gem_object_create_lmem(dev_priv, size,
 						  I915_BO_ALLOC_CONTIGUOUS |
 						  I915_BO_ALLOC_USER);
+	} else if (IS_METEORLAKE(dev_priv)) { /* Wa_22018444074 */
+		obj = i915_gem_object_create_shmem(dev_priv, size);
 	} else {
 		/*
 		 * If the FB is too big, just don't use it since fbdev is not very
drivers/gpu/drm/i915/display/intel_overlay.c +4 -3
index d6fe2bbabe55..05ae446c8a56 100644
@@ -1348,12 +1348,13 @@ int intel_overlay_attrs_ioctl(struct drm_device *dev, void *data,
 static int get_registers(struct intel_overlay *overlay, bool use_phys)
 {
 	struct drm_i915_private *i915 = overlay->i915;
-	struct drm_i915_gem_object *obj;
+	struct drm_i915_gem_object *obj = NULL;
 	struct i915_vma *vma;
 	int err;
 
-	obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
-	if (IS_ERR(obj))
+	if (!IS_METEORLAKE(i915)) /* Wa_22018444074 */
+		obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
+	if (IS_ERR_OR_NULL(obj))
 		obj = i915_gem_object_create_internal(i915, PAGE_SIZE);
 	if (IS_ERR(obj))
 		return PTR_ERR(obj);
Signature · 1 line
2.39.0
Reviewed-by on v1 2/2
#2 lore raw

Re: [Intel-gfx] [PATCH 2/2] drm/i915/display: Do not use stolen on MTL

Quoted 19 lines · Nirmoy Das

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>
---
  drivers/gpu/drm/i915/display/intel_fbdev.c   | 2 ++
  drivers/gpu/drm/i915/display/intel_overlay.c | 7 ++++---
  2 files changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_fbdev.c +0 -0
index 1cc0ddc6a310..10e38d60f9ef 100644

drivers/gpu/drm/i915/display/intel_fbdev.c static int intelfb_alloc(struct drm_fb_helper *helper, · line 186

Quoted 5 lines
drivers/gpu/drm/i915/display/intel_fbdev.c +2 -0
@@ -182,6 +182,8 @@ static int intelfb_alloc(struct drm_fb_helper *helper,
  		obj = i915_gem_object_create_lmem(dev_priv, size,
  						  I915_BO_ALLOC_CONTIGUOUS |
  						  I915_BO_ALLOC_USER);
+	} else if (IS_METEORLAKE(dev_priv)) { /* Wa_22018444074 */
+		obj = i915_gem_object_create_shmem(dev_priv, size);

If you put the check inside following else clause, you will have only one place to call i915_gem_object_create_shmem.

Quoted 11 lines
drivers/gpu/drm/i915/display/intel_fbdev.c +0 -0
  	} else {
  		/*
  		 * If the FB is too big, just don't use it since fbdev is not very
drivers/gpu/drm/i915/display/intel_overlay.c +0 -0
index d6fe2bbabe55..05ae446c8a56 100644
@@ -1348,12 +1348,13 @@ int intel_overlay_attrs_ioctl(struct drm_device *dev, void *data,
  static int get_registers(struct intel_overlay *overlay, bool use_phys)
  {
  	struct drm_i915_private *i915 = overlay->i915;

drivers/gpu/drm/i915/display/intel_overlay.c int intel_overlay_attrs_ioctl(struct drm_device *dev, void *data, · line 1357

Quoted 10 lines
drivers/gpu/drm/i915/display/intel_overlay.c +4 -3
-	struct drm_i915_gem_object *obj;
+	struct drm_i915_gem_object *obj = NULL;
  	struct i915_vma *vma;
  	int err;
 
-	obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
-	if (IS_ERR(obj))
+	if (!IS_METEORLAKE(i915)) /* Wa_22018444074 */
+		obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
+	if (IS_ERR_OR_NULL(obj))

Initializing obj with ERR_PTR(-ENODEV) and using IS_ERR here will be aligned to previous stanza (intelfb_alloc).

Since my comments are close to  bikeshedding, please go your way if you wish:

Regards
Andrzej

Quoted 3 lines
drivers/gpu/drm/i915/display/intel_overlay.c +0 -0
  		obj = i915_gem_object_create_internal(i915, PAGE_SIZE);
  	if (IS_ERR(obj))
  		return PTR_ERR(obj);
#3 lore raw

Re: [Intel-gfx] [PATCH 2/2] drm/i915/display: Do not use stolen on MTL

Quoted 55 lines · Andrzej Hajda
Quoted 21 lines · Nirmoy Das

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>

---
  drivers/gpu/drm/i915/display/intel_fbdev.c   | 2 ++ drivers/gpu/drm/i915/display/intel_overlay.c | 7 ++++---

  2 files changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_fbdev.c +0 -0
index 1cc0ddc6a310..10e38d60f9ef 100644
@@ -182,6 +182,8 @@ static int intelfb_alloc(struct drm_fb_helper 
 *helper,
           obj = i915_gem_object_create_lmem(dev_priv, size,
Quoted 4 lines

                            I915_BO_ALLOC_CONTIGUOUS | I915_BO_ALLOC_USER);
+    } else if (IS_METEORLAKE(dev_priv)) { /* Wa_22018444074 */ +        obj = i915_gem_object_create_shmem(dev_priv, size);

If you put the check inside following else clause, you will have only one place to call i915_gem_object_create_shmem.

Quoted 11 lines

      } else {
          /*
           * If the FB is too big, just don't use it since fbdev is not very

drivers/gpu/drm/i915/display/intel_overlay.c +0 -0
index d6fe2bbabe55..05ae446c8a56 100644
@@ -1348,12 +1348,13 @@ int intel_overlay_attrs_ioctl(struct 
 drm_device *dev, void *data,
   static int get_registers(struct intel_overlay *overlay, bool use_phys)
   {

drivers/gpu/drm/i915/display/intel_overlay.c int intel_overlay_attrs_ioctl(struct · line 1358

Quoted 10 lines
drivers/gpu/drm/i915/display/intel_overlay.c +4 -2
       struct drm_i915_private *i915 = overlay->i915;
-    struct drm_i915_gem_object *obj;
+    struct drm_i915_gem_object *obj = NULL;
       struct i915_vma *vma;
       int err;
   -    obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
-    if (IS_ERR(obj))
+    if (!IS_METEORLAKE(i915)) /* Wa_22018444074 */
+        obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
+    if (IS_ERR_OR_NULL(obj))

Initializing obj with ERR_PTR(-ENODEV) and using IS_ERR here will be aligned to previous stanza (intelfb_alloc).

Quoted 1 line

Since my comments are close to  bikeshedding,

I will resend with those suggestion.

Thanks,

Nirmoy

Quoted 10 lines

please go your way if you wish:

Regards
Andrzej

Quoted 3 lines
drivers/gpu/drm/i915/display/intel_overlay.c +0 -0
           obj = i915_gem_object_create_internal(i915, PAGE_SIZE);
       if (IS_ERR(obj))

          return PTR_ERR(obj);

#4 lore raw

Re: [Intel-gfx] [PATCH 2/2] drm/i915/display: Do not use stolen on MTL

In reply to Nirmoy Das
Quoted 2 lines · Nirmoy Das

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Does anything remain in stolen or could the memory region just not be created?

Regards,

Tvrtko

Quoted 45 lines
Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>
---
  drivers/gpu/drm/i915/display/intel_fbdev.c   | 2 ++
  drivers/gpu/drm/i915/display/intel_overlay.c | 7 ++++---
  2 files changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_fbdev.c +2 -0
index 1cc0ddc6a310..10e38d60f9ef 100644
@@ -182,6 +182,8 @@ static int intelfb_alloc(struct drm_fb_helper *helper,
  		obj = i915_gem_object_create_lmem(dev_priv, size,
  						  I915_BO_ALLOC_CONTIGUOUS |
  						  I915_BO_ALLOC_USER);
+	} else if (IS_METEORLAKE(dev_priv)) { /* Wa_22018444074 */
+		obj = i915_gem_object_create_shmem(dev_priv, size);
  	} else {
  		/*
  		 * If the FB is too big, just don't use it since fbdev is not very
drivers/gpu/drm/i915/display/intel_overlay.c +4 -3
index d6fe2bbabe55..05ae446c8a56 100644
@@ -1348,12 +1348,13 @@ int intel_overlay_attrs_ioctl(struct drm_device *dev, void *data,
  static int get_registers(struct intel_overlay *overlay, bool use_phys)
  {
  	struct drm_i915_private *i915 = overlay->i915;
-	struct drm_i915_gem_object *obj;
+	struct drm_i915_gem_object *obj = NULL;
  	struct i915_vma *vma;
  	int err;
 
-	obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
-	if (IS_ERR(obj))
+	if (!IS_METEORLAKE(i915)) /* Wa_22018444074 */
+		obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
+	if (IS_ERR_OR_NULL(obj))
  		obj = i915_gem_object_create_internal(i915, PAGE_SIZE);
  	if (IS_ERR(obj))
  		return PTR_ERR(obj);
#5 lore raw

Re: [Intel-gfx] [PATCH 2/2] drm/i915/display: Do not use stolen on MTL

Quoted 6 lines · Tvrtko Ursulin
Quoted 2 lines · Nirmoy Das

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Does anything remain in stolen or could the memory region just not be created?

GSC requires DSM which can't use smem for another bug.

Regards,

Nirmoy

Quoted 51 lines

Regards,

Tvrtko

Quoted 46 lines
Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>

---
  drivers/gpu/drm/i915/display/intel_fbdev.c   | 2 ++ drivers/gpu/drm/i915/display/intel_overlay.c | 7 ++++---

  2 files changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_fbdev.c +0 -0
index 1cc0ddc6a310..10e38d60f9ef 100644
@@ -182,6 +182,8 @@ static int intelfb_alloc(struct drm_fb_helper 
 *helper,
           obj = i915_gem_object_create_lmem(dev_priv, size,

                            I915_BO_ALLOC_CONTIGUOUS | I915_BO_ALLOC_USER);
+    } else if (IS_METEORLAKE(dev_priv)) { /* Wa_22018444074 */ +        obj = i915_gem_object_create_shmem(dev_priv, size);
      } else {
          /*
           * If the FB is too big, just don't use it since fbdev is not very

drivers/gpu/drm/i915/display/intel_overlay.c +4 -2
index d6fe2bbabe55..05ae446c8a56 100644
@@ -1348,12 +1348,13 @@ int intel_overlay_attrs_ioctl(struct 
 drm_device *dev, void *data,
   static int get_registers(struct intel_overlay *overlay, bool use_phys)
   {
       struct drm_i915_private *i915 = overlay->i915;
-    struct drm_i915_gem_object *obj;
+    struct drm_i915_gem_object *obj = NULL;
       struct i915_vma *vma;
       int err;
   -    obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
-    if (IS_ERR(obj))
+    if (!IS_METEORLAKE(i915)) /* Wa_22018444074 */
+        obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
+    if (IS_ERR_OR_NULL(obj))
           obj = i915_gem_object_create_internal(i915, PAGE_SIZE);
       if (IS_ERR(obj))

          return PTR_ERR(obj);

#6 lore raw

Re: [Intel-gfx] [PATCH 2/2] drm/i915/display: Do not use stolen on MTL

Quoted 11 lines · Nirmoy Das
Quoted 6 lines · Tvrtko Ursulin
Quoted 2 lines · Nirmoy Das

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Does anything remain in stolen or could the memory region just not be created?

GSC requires DSM which can't use smem for another bug.

Okay, thanks.

As a related comment, these if-if-if object creation ladders were always a bit ugly and some years ago I was suggesting we create a helper with some "intent/usage" flags. Which could then dtrt ie. create the right object for that intent/usage and platform. I *think* I possibly even had a RFC... need to try and find it.

Regards,

Tvrtko

Quoted 57 lines

Regards,

Nirmoy

Quoted 51 lines

Regards,

Tvrtko

Quoted 46 lines
Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>

---
  drivers/gpu/drm/i915/display/intel_fbdev.c   | 2 ++ drivers/gpu/drm/i915/display/intel_overlay.c | 7 ++++---

  2 files changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_fbdev.c +0 -0
index 1cc0ddc6a310..10e38d60f9ef 100644
@@ -182,6 +182,8 @@ static int intelfb_alloc(struct drm_fb_helper 
 *helper,
           obj = i915_gem_object_create_lmem(dev_priv, size,

                            I915_BO_ALLOC_CONTIGUOUS | I915_BO_ALLOC_USER);
+    } else if (IS_METEORLAKE(dev_priv)) { /* Wa_22018444074 */ +        obj = i915_gem_object_create_shmem(dev_priv, size);
      } else {
          /*
           * If the FB is too big, just don't use it since fbdev is not very

drivers/gpu/drm/i915/display/intel_overlay.c +4 -2
index d6fe2bbabe55..05ae446c8a56 100644
@@ -1348,12 +1348,13 @@ int intel_overlay_attrs_ioctl(struct 
 drm_device *dev, void *data,
   static int get_registers(struct intel_overlay *overlay, bool use_phys)
   {
       struct drm_i915_private *i915 = overlay->i915;
-    struct drm_i915_gem_object *obj;
+    struct drm_i915_gem_object *obj = NULL;
       struct i915_vma *vma;
       int err;
   -    obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
-    if (IS_ERR(obj))
+    if (!IS_METEORLAKE(i915)) /* Wa_22018444074 */
+        obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
+    if (IS_ERR_OR_NULL(obj))
           obj = i915_gem_object_create_internal(i915, PAGE_SIZE);
       if (IS_ERR(obj))

          return PTR_ERR(obj);

#7 lore raw

Re: [Intel-gfx] [PATCH 2/2] drm/i915/display: Do not use stolen on MTL

Hi Tvrkto,

Quoted 9 lines · Tvrtko Ursulin
Quoted 7 lines · Nirmoy Das
Quoted 5 lines · Tvrtko Ursulin
Quoted 2 lines · Nirmoy Das

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

Does anything remain in stolen or could the memory region just not be created?

GSC requires DSM which can't use smem for another bug.

Okay, thanks.

As a related comment, these if-if-if object creation ladders were always a bit ugly and some years ago I was suggesting we create a helper with some "intent/usage" flags. Which could then dtrt ie. create the right object for that intent/usage and platform. I *think* I possibly even had a RFC... need to try and find it.

Did you find it :) Would be nice to have a better way to detect and apply memory region as per platfrom/usecase.

Regards,

Nirmoy

Quoted 62 lines

Regards,

Tvrtko

Quoted 57 lines

Regards,

Nirmoy

Quoted 51 lines

Regards,

Tvrtko

Quoted 46 lines
Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>

---
  drivers/gpu/drm/i915/display/intel_fbdev.c   | 2 ++ drivers/gpu/drm/i915/display/intel_overlay.c | 7 ++++---

  2 files changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_fbdev.c +0 -0
index 1cc0ddc6a310..10e38d60f9ef 100644
@@ -182,6 +182,8 @@ static int intelfb_alloc(struct drm_fb_helper 
 *helper,
           obj = i915_gem_object_create_lmem(dev_priv, size,

                            I915_BO_ALLOC_CONTIGUOUS | I915_BO_ALLOC_USER);
+    } else if (IS_METEORLAKE(dev_priv)) { /* Wa_22018444074 */ +        obj = i915_gem_object_create_shmem(dev_priv, size);
      } else {
          /*
           * If the FB is too big, just don't use it since fbdev is not very

drivers/gpu/drm/i915/display/intel_overlay.c +4 -2
index d6fe2bbabe55..05ae446c8a56 100644
@@ -1348,12 +1348,13 @@ int intel_overlay_attrs_ioctl(struct 
 drm_device *dev, void *data,
   static int get_registers(struct intel_overlay *overlay, bool use_phys)
   {
       struct drm_i915_private *i915 = overlay->i915;
-    struct drm_i915_gem_object *obj;
+    struct drm_i915_gem_object *obj = NULL;
       struct i915_vma *vma;
       int err;
   -    obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
-    if (IS_ERR(obj))
+    if (!IS_METEORLAKE(i915)) /* Wa_22018444074 */
+        obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
+    if (IS_ERR_OR_NULL(obj))
           obj = i915_gem_object_create_internal(i915, PAGE_SIZE);
       if (IS_ERR(obj))

          return PTR_ERR(obj);

#8 lore raw

Re: [Intel-gfx] [PATCH 2/2] drm/i915/display: Do not use stolen on MTL

Quoted 15 lines · Nirmoy Das

Hi Tvrkto,

Quoted 12 lines · Tvrtko Ursulin
Quoted 10 lines · Nirmoy Das
Quoted 6 lines · Tvrtko Ursulin
Quoted 2 lines · Nirmoy Das

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Does anything remain in stolen or could the memory region just not be created?

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

GSC requires DSM which can't use smem for another bug.

Okay, thanks.

As a related comment, these if-if-if object creation ladders were always a bit ugly and some years ago I was suggesting we create a helper with some "intent/usage" flags. Which could then dtrt ie. create the right object for that intent/usage and platform. I *think* I possibly even had a RFC... need to try and find it.

Did you find it :) Would be nice to have a better way to detect and apply memory region as per platfrom/usecase.

Nope. Basically the idea boiled down to figuring out if it is possible to express the "requirements" via intent flags. Like do we need CPU access, is it mostly GPU, can it be volatile etc. And then combine the intent with the platform to figure out what kind of object to create. But it was many years ago and I am not sure if the idea would still apply so easily, without looking at the all call sites. Could easily end up complicated so I cannot dare to say it is worth spending time looking at this.

Regards,

Tvrtko

Quoted 68 lines

Regards,

Nirmoy

Quoted 62 lines

Regards,

Tvrtko

Quoted 57 lines

Regards,

Nirmoy

Quoted 51 lines

Regards,

Tvrtko

Quoted 46 lines
Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>

---
  drivers/gpu/drm/i915/display/intel_fbdev.c   | 2 ++ drivers/gpu/drm/i915/display/intel_overlay.c | 7 ++++---

  2 files changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_fbdev.c +0 -0
index 1cc0ddc6a310..10e38d60f9ef 100644
@@ -182,6 +182,8 @@ static int intelfb_alloc(struct drm_fb_helper 
 *helper,
           obj = i915_gem_object_create_lmem(dev_priv, size,

                            I915_BO_ALLOC_CONTIGUOUS | I915_BO_ALLOC_USER);
+    } else if (IS_METEORLAKE(dev_priv)) { /* Wa_22018444074 */ +        obj = i915_gem_object_create_shmem(dev_priv, size);
      } else {
          /*
           * If the FB is too big, just don't use it since fbdev is not very

drivers/gpu/drm/i915/display/intel_overlay.c +4 -2
index d6fe2bbabe55..05ae446c8a56 100644
@@ -1348,12 +1348,13 @@ int intel_overlay_attrs_ioctl(struct 
 drm_device *dev, void *data,
   static int get_registers(struct intel_overlay *overlay, bool use_phys)
   {
       struct drm_i915_private *i915 = overlay->i915;
-    struct drm_i915_gem_object *obj;
+    struct drm_i915_gem_object *obj = NULL;
       struct i915_vma *vma;
       int err;
   -    obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
-    if (IS_ERR(obj))
+    if (!IS_METEORLAKE(i915)) /* Wa_22018444074 */
+        obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
+    if (IS_ERR_OR_NULL(obj))
           obj = i915_gem_object_create_internal(i915, PAGE_SIZE);
       if (IS_ERR(obj))

          return PTR_ERR(obj);

#9 lore raw

Re: [Intel-gfx] [PATCH 2/2] drm/i915/display: Do not use stolen on MTL

Quoted 19 lines · Tvrtko Ursulin
Quoted 17 lines · Nirmoy Das

Hi Tvrkto,

Quoted 14 lines · Tvrtko Ursulin
Quoted 11 lines · Nirmoy Das
Quoted 6 lines · Tvrtko Ursulin
Quoted 2 lines · Nirmoy Das

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Does anything remain in stolen or could the memory region just not be created?

GSC requires DSM which can't use smem for another bug.

Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

Okay, thanks.

As a related comment, these if-if-if object creation ladders were always a bit ugly and some years ago I was suggesting we create a helper with some "intent/usage" flags. Which could then dtrt ie. create the right object for that intent/usage and platform. I *think* I possibly even had a RFC... need to try and find it.

Did you find it :) Would be nice to have a better way to detect and apply memory region as per platfrom/usecase.

Nope. Basically the idea boiled down to figuring out if it is possible to express the "requirements" via intent flags. Like do we need CPU access, is it mostly GPU, can it be volatile etc. And then combine the intent with the platform to figure out what kind of object to create.

Yes, that would be nice.

Quoted 1 line

But it was many years ago and I am not sure if the idea would still apply so easily, without looking at the all call sites. Could easily end up complicated so I cannot dare to say it is worth spending time looking at this.

I will record this in a Jira and hopefully get back to this when I have less urgent work.

Thanks,

Nirmoy

Quoted 73 lines

Regards,

Tvrtko

Quoted 68 lines

Regards,

Nirmoy

Quoted 62 lines

Regards,

Tvrtko

Quoted 57 lines

Regards,

Nirmoy

Quoted 51 lines

Regards,

Tvrtko

Quoted 46 lines
Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>

---
  drivers/gpu/drm/i915/display/intel_fbdev.c   | 2 ++ drivers/gpu/drm/i915/display/intel_overlay.c | 7 ++++---

  2 files changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_fbdev.c +0 -0
index 1cc0ddc6a310..10e38d60f9ef 100644
@@ -182,6 +182,8 @@ static int intelfb_alloc(struct drm_fb_helper 
 *helper,
           obj = i915_gem_object_create_lmem(dev_priv, size,

                            I915_BO_ALLOC_CONTIGUOUS | I915_BO_ALLOC_USER);
+    } else if (IS_METEORLAKE(dev_priv)) { /* Wa_22018444074 */ +        obj = i915_gem_object_create_shmem(dev_priv, size);
      } else {
          /*
           * If the FB is too big, just don't use it since fbdev is not very

drivers/gpu/drm/i915/display/intel_overlay.c +4 -2
index d6fe2bbabe55..05ae446c8a56 100644
@@ -1348,12 +1348,13 @@ int intel_overlay_attrs_ioctl(struct 
 drm_device *dev, void *data,
   static int get_registers(struct intel_overlay *overlay, bool use_phys)
   {
       struct drm_i915_private *i915 = overlay->i915;
-    struct drm_i915_gem_object *obj;
+    struct drm_i915_gem_object *obj = NULL;
       struct i915_vma *vma;
       int err;
   -    obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
-    if (IS_ERR(obj))
+    if (!IS_METEORLAKE(i915)) /* Wa_22018444074 */
+        obj = i915_gem_object_create_stolen(i915, PAGE_SIZE);
+    if (IS_ERR_OR_NULL(obj))
           obj = i915_gem_object_create_internal(i915, PAGE_SIZE);
       if (IS_ERR(obj))

          return PTR_ERR(obj);

Reviewed-by on v1 2/2
#10 lore raw

Re: [Intel-gfx] [PATCH 2/2] drm/i915/display: Do not use stolen on MTL

In reply to Nirmoy Das

Hi Nirmoy,

Quoted 9 lines · Nirmoy Das

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>

Andi

#11 lore raw

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/i915/gt: Do not use stolen on MTL

In reply to Nirmoy Das
== Series Details ==

== Series Details ==

Series: series starting with [1/2] drm/i915/gt: Do not use stolen on MTL
URL : https://patchwork.freedesktop.org/series/120086/
State : warning

== Summary ==

Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately. +./arch/x86/include/asm/bitops.h:117:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:148:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:150:9: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:154:26: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:156:16: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:156:9: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:174:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:176:9: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:180:35: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:182:16: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:182:9: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:186:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:188:9: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:192:35: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:195:16: warning: unreplaced symbol 'oldbit' +./arch/x86/include/asm/bitops.h:195:9: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:237:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:239:9: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:66:1: warning: unreplaced symbol 'return' +./arch/x86/include/asm/bitops.h:92:1: warning: unreplaced symbol 'return' +drivers/gpu/drm/i915/gt/intel_gt.h:112:16: warning: trying to copy expression type 31 +./drivers/gpu/drm/i915/intel_uncore.h:346:1: warning: trying to copy expression type 31 +./drivers/gpu/drm/i915/intel_uncore.h:351:1: warning: trying to copy expression type 31 +./include/asm-generic/bitops/generic-non-atomic.h:100:17: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:100:23: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:100:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:105:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:107:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:108:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:109:9: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:111:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:111:14: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:111:20: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:112:17: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:112:23: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:112:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:121:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:128:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:166:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:168:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:169:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:170:9: warning: unreplaced symbol 'val' +./include/asm-generic/bitops/generic-non-atomic.h:172:19: warning: unreplaced symbol 'val' +./include/asm-generic/bitops/generic-non-atomic.h:172:25: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:172:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:28:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:30:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:31:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:33:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:33:16: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:37:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:39:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:40:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:42:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:42:16: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:55:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:57:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:58:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:60:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:60:15: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:73:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:75:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:76:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:77:9: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:79:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:79:14: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:79:20: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:80:17: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:80:23: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:80:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:93:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/generic-non-atomic.h:95:9: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/generic-non-atomic.h:96:9: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:97:9: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:99:10: warning: unreplaced symbol 'p' +./include/asm-generic/bitops/generic-non-atomic.h:99:14: warning: unreplaced symbol 'old' +./include/asm-generic/bitops/generic-non-atomic.h:99:21: warning: unreplaced symbol 'mask' +./include/asm-generic/bitops/instrumented-non-atomic.h:100:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:112:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:115:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:127:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:130:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:139:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:142:9: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:26:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:42:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:58:1: warning: unreplaced symbol 'return' +./include/asm-generic/bitops/instrumented-non-atomic.h:97:1: warning: unreplaced symbol 'return'

#12 lore raw

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/gt: Do not use stolen on MTL

In reply to Nirmoy Das
== Series Details ==

== Series Details ==

Series: series starting with [1/2] drm/i915/gt: Do not use stolen on MTL
URL : https://patchwork.freedesktop.org/series/120086/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_13340 -> Patchwork_120086v1
====================================================

Summary
-------

**WARNING**

Minor unknown changes coming with Patchwork_120086v1 need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_120086v1, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

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

Participating hosts (42 -> 40)
------------------------------

Missing (2): fi-kbl-soraka fi-snb-2520m

Possible new issues
-------------------

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

### IGT changes ###

#### Warnings ####

* igt@kms_setmode@basic-clone-single-crtc:
- bat-mtlp-6: [SKIP][1] ([i915#4579]) -> [SKIP][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-mtlp-6/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-6/igt@[email protected]
- bat-mtlp-8: [SKIP][3] ([i915#4579]) -> [SKIP][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-mtlp-8/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-8/igt@[email protected]

Known issues
------------

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

### IGT changes ###

#### Issues hit ####

* igt@gem_lmem_swapping@parallel-random-engines:
- bat-mtlp-8: NOTRUN -> [SKIP][5] ([i915#4613]) +3 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-8/igt@[email protected]

* igt@i915_pm_rps@basic-api:
- bat-mtlp-8: NOTRUN -> [SKIP][6] ([i915#6621])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-8/igt@[email protected]

* igt@i915_selftest@live@gt_mocs:
- bat-mtlp-8: NOTRUN -> [DMESG-FAIL][7] ([i915#7059])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-8/igt@i915_selftest@live@gt_mocs.html

* igt@i915_selftest@live@migrate:
- bat-dg2-11: [PASS][8] -> [DMESG-WARN][9] ([i915#7699])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-dg2-11/igt@i915_selftest@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-dg2-11/igt@i915_selftest@[email protected]

* igt@i915_selftest@live@requests:
- bat-rpls-1: [PASS][10] -> [ABORT][11] ([i915#4983] / [i915#7911] / [i915#7920])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-rpls-1/igt@i915_selftest@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-rpls-1/igt@i915_selftest@[email protected]
- bat-mtlp-6: [PASS][12] -> [DMESG-FAIL][13] ([i915#8497])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-mtlp-6/igt@i915_selftest@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-6/igt@i915_selftest@[email protected]

* igt@i915_suspend@basic-s3-without-i915:
- bat-mtlp-8: NOTRUN -> [SKIP][14] ([i915#6645])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-8/igt@[email protected]

* igt@kms_chamelium_hpd@common-hpd-after-suspend:
- bat-mtlp-8: NOTRUN -> [SKIP][15] ([i915#7828])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-8/igt@[email protected]

* igt@prime_vgem@basic-fence-read:
- bat-mtlp-8: NOTRUN -> [SKIP][16] ([i915#3708]) +2 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-8/igt@[email protected]

* igt@prime_vgem@basic-gtt:
- bat-mtlp-8: NOTRUN -> [SKIP][17] ([i915#3708] / [i915#4077]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-8/igt@[email protected]

#### Possible fixes ####

* igt@i915_pm_rpm@basic-pci-d3-state:
- bat-mtlp-8: [ABORT][18] ([i915#7077] / [i915#7977]) -> [PASS][19]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-mtlp-8/igt@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-8/igt@[email protected]

* igt@i915_selftest@live@gt_mocs:
- bat-mtlp-6: [DMESG-FAIL][20] ([i915#7059]) -> [PASS][21]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-mtlp-6/igt@i915_selftest@live@gt_mocs.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-mtlp-6/igt@i915_selftest@live@gt_mocs.html

* igt@i915_selftest@live@gt_pm:
- bat-rpls-2: [DMESG-FAIL][22] ([i915#4258] / [i915#7913]) -> [PASS][23]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-rpls-2/igt@i915_selftest@live@gt_pm.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-rpls-2/igt@i915_selftest@live@gt_pm.html

* igt@i915_selftest@live@hangcheck:
- fi-skl-guc: [DMESG-FAIL][24] ([i915#8723]) -> [PASS][25]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-skl-guc/igt@i915_selftest@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-skl-guc/igt@i915_selftest@[email protected]

#### Warnings ####

* igt@i915_module_load@load:
- bat-adlp-11: [DMESG-WARN][26] ([i915#4423]) -> [ABORT][27] ([i915#4423])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-adlp-11/igt@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-adlp-11/igt@[email protected]

* igt@i915_selftest@live@reset:
- bat-rpls-2: [ABORT][28] ([i915#4983] / [i915#7461] / [i915#7913] / [i915#7981] / [i915#8347]) -> [ABORT][29] ([i915#4983] / [i915#7461] / [i915#7913] / [i915#8347])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-rpls-2/igt@i915_selftest@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-rpls-2/igt@i915_selftest@[email protected]

* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-nv12@pipe-c-hdmi-a-2:
- fi-skl-guc: [SKIP][30] ([fdo#109271] / [i915#4579]) -> [SKIP][31] ([fdo#109271]) +1 similar issue
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-skl-guc/igt@kms_pipe_crc_basic@[email protected]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-skl-guc/igt@kms_pipe_crc_basic@[email protected]
- fi-bsw-n3050: [SKIP][32] ([fdo#109271] / [i915#4579]) -> [SKIP][33] ([fdo#109271]) +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-bsw-n3050/igt@kms_pipe_crc_basic@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-bsw-n3050/igt@kms_pipe_crc_basic@[email protected]

* igt@kms_psr@primary_page_flip:
- bat-rplp-1: [SKIP][34] ([i915#1072]) -> [ABORT][35] ([i915#8442] / [i915#8668])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-rplp-1/igt@kms_psr@primary_page_flip.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-rplp-1/igt@kms_psr@primary_page_flip.html

* igt@kms_setmode@basic-clone-single-crtc:
- bat-adlp-9: [SKIP][36] ([i915#3555] / [i915#4579]) -> [SKIP][37] ([i915#3555])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-adlp-9/igt@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-adlp-9/igt@[email protected]
- fi-rkl-11600: [SKIP][38] ([i915#3555] / [i915#4098] / [i915#4579]) -> [SKIP][39] ([i915#3555] / [i915#4098])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-rkl-11600/igt@[email protected]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-rkl-11600/igt@[email protected]
- bat-adls-5: [SKIP][40] ([i915#3555] / [i915#4579]) -> [SKIP][41] ([i915#3555])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-adls-5/igt@[email protected]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-adls-5/igt@[email protected]
- bat-dg1-5: [SKIP][42] ([i915#3555] / [i915#4579]) -> [SKIP][43] ([i915#3555])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-dg1-5/igt@[email protected]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-dg1-5/igt@[email protected]
- bat-dg2-9: [SKIP][44] ([i915#3555] / [i915#4579]) -> [SKIP][45] ([i915#3555])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-dg2-9/igt@[email protected]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-dg2-9/igt@[email protected]
- fi-kbl-x1275: [SKIP][46] ([fdo#109271] / [i915#4579]) -> [SKIP][47] ([fdo#109271])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-kbl-x1275/igt@[email protected]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-kbl-x1275/igt@[email protected]
- fi-cfl-8109u: [SKIP][48] ([fdo#109271] / [i915#4579]) -> [SKIP][49] ([fdo#109271])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-cfl-8109u/igt@[email protected]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-cfl-8109u/igt@[email protected]
- fi-kbl-7567u: [SKIP][50] ([fdo#109271] / [i915#4579]) -> [SKIP][51] ([fdo#109271])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-kbl-7567u/igt@[email protected]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-kbl-7567u/igt@[email protected]
- fi-kbl-8809g: [SKIP][52] ([fdo#109271] / [i915#4579]) -> [SKIP][53] ([fdo#109271])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-kbl-8809g/igt@[email protected]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-kbl-8809g/igt@[email protected]
- fi-ilk-650: [SKIP][54] ([fdo#109271] / [i915#4579]) -> [SKIP][55] ([fdo#109271])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-ilk-650/igt@[email protected]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-ilk-650/igt@[email protected]
- fi-tgl-1115g4: [SKIP][56] ([i915#3555] / [i915#4579]) -> [SKIP][57] ([i915#3555])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-tgl-1115g4/igt@[email protected]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-tgl-1115g4/igt@[email protected]
- fi-blb-e6850: [SKIP][58] ([fdo#109271] / [i915#4579]) -> [SKIP][59] ([fdo#109271])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-blb-e6850/igt@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-blb-e6850/igt@[email protected]
- fi-cfl-guc: [SKIP][60] ([fdo#109271] / [i915#4579]) -> [SKIP][61] ([fdo#109271])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-cfl-guc/igt@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-cfl-guc/igt@[email protected]
- fi-skl-6600u: [SKIP][62] ([fdo#109271] / [i915#4579]) -> [SKIP][63] ([fdo#109271])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-skl-6600u/igt@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-skl-6600u/igt@[email protected]
- fi-apl-guc: [SKIP][64] ([fdo#109271] / [i915#4579]) -> [SKIP][65] ([fdo#109271])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-apl-guc/igt@[email protected]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-apl-guc/igt@[email protected]
- bat-rpls-2: [SKIP][66] ([i915#3555] / [i915#4579]) -> [SKIP][67] ([i915#3555])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-rpls-2/igt@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-rpls-2/igt@[email protected]
- fi-cfl-8700k: [SKIP][68] ([fdo#109271] / [i915#4579]) -> [SKIP][69] ([fdo#109271])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-cfl-8700k/igt@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-cfl-8700k/igt@[email protected]
- fi-bsw-nick: [SKIP][70] ([fdo#109271] / [i915#4579]) -> [SKIP][71] ([fdo#109271])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-bsw-nick/igt@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-bsw-nick/igt@[email protected]
- bat-jsl-3: [SKIP][72] ([i915#3555] / [i915#4579]) -> [SKIP][73] ([i915#3555])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-jsl-3/igt@[email protected]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-jsl-3/igt@[email protected]
- bat-dg2-11: [SKIP][74] ([i915#3555] / [i915#4579]) -> [SKIP][75] ([i915#3555])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-dg2-11/igt@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-dg2-11/igt@[email protected]
- fi-hsw-4770: [SKIP][76] ([fdo#109271] / [i915#4579]) -> [SKIP][77] ([fdo#109271])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-hsw-4770/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-hsw-4770/igt@[email protected]
- fi-ivb-3770: [SKIP][78] ([fdo#109271] / [i915#4579]) -> [SKIP][79] ([fdo#109271])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-ivb-3770/igt@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-ivb-3770/igt@[email protected]
- fi-elk-e7500: [SKIP][80] ([fdo#109271] / [i915#4579]) -> [SKIP][81] ([fdo#109271])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-elk-e7500/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-elk-e7500/igt@[email protected]
- bat-dg2-8: [SKIP][82] ([i915#3555] / [i915#4579]) -> [SKIP][83] ([i915#3555])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-dg2-8/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-dg2-8/igt@[email protected]
- fi-kbl-guc: [SKIP][84] ([fdo#109271] / [i915#4579]) -> [SKIP][85] ([fdo#109271])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-kbl-guc/igt@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-kbl-guc/igt@[email protected]
- bat-adlm-1: [SKIP][86] ([i915#3555] / [i915#4579]) -> [SKIP][87] ([i915#3555])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-adlm-1/igt@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-adlm-1/igt@[email protected]
- bat-jsl-1: [SKIP][88] ([i915#3555] / [i915#4579]) -> [SKIP][89] ([i915#3555])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-jsl-1/igt@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-jsl-1/igt@[email protected]
- bat-rpls-1: [SKIP][90] ([i915#3555] / [i915#4579]) -> [SKIP][91] ([i915#3555])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-rpls-1/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-rpls-1/igt@[email protected]
- fi-pnv-d510: [SKIP][92] ([fdo#109271] / [i915#4579]) -> [SKIP][93] ([fdo#109271])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-pnv-d510/igt@[email protected]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-pnv-d510/igt@[email protected]
- bat-dg1-7: [SKIP][94] ([i915#3555] / [i915#4579]) -> [SKIP][95] ([i915#3555])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/bat-dg1-7/igt@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/bat-dg1-7/igt@[email protected]
- fi-glk-j4005: [SKIP][96] ([fdo#109271] / [i915#4579]) -> [SKIP][97] ([fdo#109271])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/fi-glk-j4005/igt@[email protected]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/fi-glk-j4005/igt@[email protected]

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4258]: https://gitlab.freedesktop.org/drm/intel/issues/4258
[i915#4423]: https://gitlab.freedesktop.org/drm/intel/issues/4423
[i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#6621]: https://gitlab.freedesktop.org/drm/intel/issues/6621
[i915#6645]: https://gitlab.freedesktop.org/drm/intel/issues/6645
[i915#7059]: https://gitlab.freedesktop.org/drm/intel/issues/7059
[i915#7077]: https://gitlab.freedesktop.org/drm/intel/issues/7077
[i915#7461]: https://gitlab.freedesktop.org/drm/intel/issues/7461
[i915#7699]: https://gitlab.freedesktop.org/drm/intel/issues/7699
[i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
[i915#7911]: https://gitlab.freedesktop.org/drm/intel/issues/7911
[i915#7913]: https://gitlab.freedesktop.org/drm/intel/issues/7913
[i915#7920]: https://gitlab.freedesktop.org/drm/intel/issues/7920
[i915#7977]: https://gitlab.freedesktop.org/drm/intel/issues/7977
[i915#7981]: https://gitlab.freedesktop.org/drm/intel/issues/7981
[i915#8347]: https://gitlab.freedesktop.org/drm/intel/issues/8347
[i915#8442]: https://gitlab.freedesktop.org/drm/intel/issues/8442
[i915#8497]: https://gitlab.freedesktop.org/drm/intel/issues/8497
[i915#8668]: https://gitlab.freedesktop.org/drm/intel/issues/8668
[i915#8723]: https://gitlab.freedesktop.org/drm/intel/issues/8723

Build changes
-------------

* Linux: CI_DRM_13340 -> Patchwork_120086v1

CI-20190529: 20190529
CI_DRM_13340: a3b671a5e12f1fd972ad7046f39a470acbefbbdc @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7357: 790f69303f49066b150fbdff95e471e14d046710 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_120086v1: a3b671a5e12f1fd972ad7046f39a470acbefbbdc @ git://anongit.freedesktop.org/gfx-ci/linux

### Linux commits

00aabe38b06b drm/i915/display: Do not use stolen on MTL 274dfa79a01c drm/i915/gt: Do not use stolen on MTL

== Logs ==

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

#13 lore raw

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/gt: Do not use stolen on MTL

In reply to Nirmoy Das
== Series Details ==

== Series Details ==

Series: series starting with [1/2] drm/i915/gt: Do not use stolen on MTL
URL : https://patchwork.freedesktop.org/series/120086/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_13340_full -> Patchwork_120086v1_full
====================================================

Summary
-------

**SUCCESS**

No regressions found.

Participating hosts (9 -> 9)
------------------------------

No changes in participating hosts

Known issues
------------

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

### IGT changes ###

#### Issues hit ####

* igt@drm_fdinfo@most-busy-check-all@rcs0:
- shard-rkl: [PASS][1] -> [FAIL][2] ([i915#7742])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-rkl-2/igt@drm_fdinfo@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-2/igt@drm_fdinfo@[email protected]

* igt@gem_create@create-ext-set-pat:
- shard-dg2: NOTRUN -> [FAIL][3] ([i915#8621])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-1/igt@[email protected]

* igt@gem_eio@hibernate:
- shard-dg2: [PASS][4] -> [ABORT][5] ([i915#7975] / [i915#8213])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-11/igt@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-7/igt@[email protected]

* igt@gem_exec_balancer@bonded-false-hang:
- shard-dg2: NOTRUN -> [SKIP][6] ([i915#4812])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@gem_exec_fair@basic-deadline:
- shard-glk: [PASS][7] -> [FAIL][8] ([i915#2846])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-glk2/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-glk3/igt@[email protected]

* igt@gem_exec_fair@basic-pace-solo:
- shard-dg2: NOTRUN -> [SKIP][9] ([i915#3539])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-1/igt@[email protected]

* igt@gem_exec_flush@basic-wb-prw-default:
- shard-dg2: NOTRUN -> [SKIP][10] ([i915#3539] / [i915#4852]) +1 similar issue
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@gem_exec_gttfill@multigpu-basic:
- shard-mtlp: NOTRUN -> [SKIP][11] ([i915#7697])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@[email protected]

* igt@gem_exec_reloc@basic-wc-active:
- shard-mtlp: NOTRUN -> [SKIP][12] ([i915#3281])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@[email protected]

* igt@gem_exec_suspend@basic-s4-devices@lmem0:
- shard-dg2: NOTRUN -> [ABORT][13] ([i915#7975] / [i915#8213] / [i915#8682])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@gem_exec_suspend@[email protected]

* igt@gem_exec_whisper@basic-normal:
- shard-mtlp: [PASS][14] -> [FAIL][15] ([i915#6363])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-5/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-4/igt@[email protected]

* igt@gem_lmem_swapping@heavy-verify-random-ccs:
- shard-mtlp: NOTRUN -> [SKIP][16] ([i915#4613])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@[email protected]

* igt@gem_mmap_gtt@basic-small-copy:
- shard-mtlp: NOTRUN -> [SKIP][17] ([i915#4077]) +2 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-5/igt@[email protected]

* igt@gem_mmap_gtt@medium-copy-xy:
- shard-dg2: NOTRUN -> [SKIP][18] ([i915#4077]) +5 similar issues
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@gem_mmap_wc@set-cache-level:
- shard-dg2: NOTRUN -> [SKIP][19] ([i915#4083])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@gem_pwrite_snooped:
- shard-dg2: NOTRUN -> [SKIP][20] ([i915#3282]) +3 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@gem_pwrite_snooped.html

* igt@gem_pxp@create-regular-buffer:
- shard-mtlp: NOTRUN -> [SKIP][21] ([i915#4270])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-8/igt@[email protected]

* igt@gem_readwrite@read-bad-handle:
- shard-mtlp: NOTRUN -> [SKIP][22] ([i915#3282])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-8/igt@[email protected]

* igt@gem_render_copy@y-tiled-ccs-to-y-tiled-mc-ccs:
- shard-dg2: NOTRUN -> [SKIP][23] ([i915#5190]) +3 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@gem_render_copy@yf-tiled-ccs-to-y-tiled:
- shard-mtlp: NOTRUN -> [SKIP][24] ([i915#8428]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-5/igt@[email protected]

* igt@gen7_exec_parse@basic-rejected:
- shard-dg2: NOTRUN -> [SKIP][25] ([fdo#109289]) +2 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@gen9_exec_parse@allowed-single:
- shard-apl: [PASS][26] -> [ABORT][27] ([i915#5566])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-apl7/igt@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-apl4/igt@[email protected]
- shard-glk: [PASS][28] -> [ABORT][29] ([i915#5566])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-glk1/igt@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-glk6/igt@[email protected]

* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-mtlp: NOTRUN -> [SKIP][30] ([i915#6295])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-8/igt@[email protected]

* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-hdmi-a:
- shard-rkl: [PASS][31] -> [SKIP][32] ([i915#1937])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-rkl-7/igt@i915_pm_lpsp@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-6/igt@i915_pm_lpsp@[email protected]

* igt@i915_pm_rpm@modeset-non-lpsp-stress:
- shard-dg2: [PASS][33] -> [SKIP][34] ([i915#1397]) +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-8/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-10/igt@[email protected]
- shard-rkl: [PASS][35] -> [SKIP][36] ([i915#1397]) +2 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-rkl-2/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-7/igt@[email protected]

* igt@i915_selftest@live@slpc:
- shard-mtlp: [PASS][37] -> [DMESG-WARN][38] ([i915#6367])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-1/igt@i915_selftest@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-8/igt@i915_selftest@[email protected]

* igt@i915_suspend@forcewake:
- shard-dg2: [PASS][39] -> [TIMEOUT][40] ([fdo#103375])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-10/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-11/igt@[email protected]

* igt@kms_addfb_basic@addfb25-framebuffer-vs-set-tiling:
- shard-dg2: NOTRUN -> [SKIP][41] ([i915#4212])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@kms_async_flips@async-flip-with-page-flip-events@pipe-b-hdmi-a-1-y-rc_ccs:
- shard-rkl: NOTRUN -> [SKIP][42] ([i915#8502]) +3 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-7/igt@kms_async_flips@async-flip-with-page-flip-events@pipe-b-hdmi-a-1-y-rc_ccs.html

* igt@kms_big_fb@x-tiled-64bpp-rotate-270:
- shard-dg2: NOTRUN -> [SKIP][43] ([fdo#111614]) +2 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-1/igt@[email protected]

* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip:
- shard-mtlp: [PASS][44] -> [FAIL][45] ([i915#3743]) +1 similar issue
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-3/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-7/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html

* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip:
- shard-mtlp: NOTRUN -> [SKIP][46] ([fdo#111615]) +1 similar issue
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html

* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip:
- shard-dg2: NOTRUN -> [SKIP][47] ([i915#4538] / [i915#5190])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs:
- shard-dg2: NOTRUN -> [SKIP][48] ([i915#3689] / [i915#5354]) +4 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs.html

* igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs:
- shard-mtlp: NOTRUN -> [SKIP][49] ([i915#3886] / [i915#6095])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc:
- shard-dg2: NOTRUN -> [SKIP][50] ([i915#3689] / [i915#3886] / [i915#5354]) +3 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-1/igt@kms_ccs@pipe-c-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html

* igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_ccs:
- shard-tglu: NOTRUN -> [SKIP][51] ([i915#3689] / [i915#5354] / [i915#6095])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-tglu-7/igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_ccs.html

* igt@kms_ccs@pipe-d-bad-rotation-90-4_tiled_dg2_rc_ccs_cc:
- shard-mtlp: NOTRUN -> [SKIP][52] ([i915#6095]) +5 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-1/igt@kms_ccs@pipe-d-bad-rotation-90-4_tiled_dg2_rc_ccs_cc.html

* igt@kms_ccs@pipe-d-missing-ccs-buffer-4_tiled_mtl_mc_ccs:
- shard-dg2: NOTRUN -> [SKIP][53] ([i915#5354]) +12 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@kms_ccs@pipe-d-missing-ccs-buffer-4_tiled_mtl_mc_ccs.html

* igt@kms_cdclk@mode-transition@pipe-a-dp-2:
- shard-dg2: NOTRUN -> [SKIP][54] ([i915#4087]) +7 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@kms_cdclk@[email protected]

* igt@kms_chamelium_color@ctm-0-25:
- shard-mtlp: NOTRUN -> [SKIP][55] ([fdo#111827])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@[email protected]

* igt@kms_chamelium_color@ctm-0-75:
- shard-dg2: NOTRUN -> [SKIP][56] ([fdo#111827])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@kms_chamelium_frames@dp-crc-multiple:
- shard-dg2: NOTRUN -> [SKIP][57] ([i915#7828]) +2 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@kms_chamelium_hpd@hdmi-hpd-with-enabled-mode:
- shard-mtlp: NOTRUN -> [SKIP][58] ([i915#7828]) +1 similar issue
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@[email protected]

* igt@kms_content_protection@atomic-dpms@pipe-a-dp-2:
- shard-dg2: NOTRUN -> [TIMEOUT][59] ([i915#8628])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@kms_content_protection@[email protected]

* igt@kms_content_protection@srm:
- shard-dg2: NOTRUN -> [SKIP][60] ([i915#7118])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-1/igt@[email protected]

* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- shard-dg2: NOTRUN -> [SKIP][61] ([i915#4103] / [i915#4213])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@kms_cursor_legacy@cursorb-vs-flipa-atomic-transitions-varying-size:
- shard-mtlp: NOTRUN -> [SKIP][62] ([i915#3546])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-5/igt@kms_cursor_legacy@cursorb-vs-flipa-atomic-transitions-varying-size.html

* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-apl: [PASS][63] -> [FAIL][64] ([i915#2346])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-apl3/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-apl7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html

* igt@kms_dither@fb-8bpc-vs-panel-6bpc@pipe-a-hdmi-a-2:
- shard-rkl: NOTRUN -> [SKIP][65] ([i915#3804])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-6/igt@kms_dither@[email protected]

* igt@kms_fbcon_fbt@psr-suspend:
- shard-mtlp: [PASS][66] -> [FAIL][67] ([i915#4767])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-8/igt@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-4/igt@[email protected]

* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible:
- shard-snb: NOTRUN -> [SKIP][68] ([fdo#109271] / [fdo#111767])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-snb4/igt@[email protected]

* igt@kms_flip@2x-flip-vs-panning-interruptible:
- shard-dg2: NOTRUN -> [SKIP][69] ([fdo#109274])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@kms_flip@2x-nonexisting-fb:
- shard-snb: NOTRUN -> [SKIP][70] ([fdo#109271]) +18 similar issues
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-snb2/igt@[email protected]

* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-hdmi-a2:
- shard-glk: [PASS][71] -> [FAIL][72] ([i915#79])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-glk7/igt@kms_flip@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-glk7/igt@kms_flip@[email protected]

* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-upscaling@pipe-a-valid-mode:
- shard-dg2: NOTRUN -> [SKIP][73] ([i915#2672]) +1 similar issue
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-1/igt@kms_flip_scaled_crc@[email protected]

* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-mmap-gtt:
- shard-mtlp: NOTRUN -> [SKIP][74] ([i915#8708]) +1 similar issue
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-mmap-gtt.html

* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-fullscreen:
- shard-dg2: [PASS][75] -> [FAIL][76] ([i915#6880])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-10/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-fullscreen.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-11/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-fullscreen.html

* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-move:
- shard-tglu: NOTRUN -> [SKIP][77] ([fdo#109280]) +1 similar issue
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-tglu-7/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-mmap-wc:
- shard-mtlp: NOTRUN -> [SKIP][78] ([i915#1825]) +5 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-1/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-mmap-wc.html

* igt@kms_frontbuffer_tracking@fbc-rgb565-draw-mmap-wc:
- shard-dg2: NOTRUN -> [SKIP][79] ([i915#8708]) +3 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-onoff:
- shard-tglu: NOTRUN -> [SKIP][80] ([fdo#110189])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-tglu-7/igt@[email protected]

* igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite:
- shard-dg2: NOTRUN -> [SKIP][81] ([i915#3458]) +2 similar issues
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite.html

* igt@kms_hdr@static-toggle-suspend:
- shard-mtlp: NOTRUN -> [SKIP][82] ([i915#8761]) +1 similar issue
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-7/igt@[email protected]

* igt@kms_multipipe_modeset@basic-max-pipe-crc-check:
- shard-mtlp: NOTRUN -> [SKIP][83] ([i915#4816])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-5/igt@[email protected]

* igt@kms_plane_scaling@intel-max-src-size@pipe-a-dp-4:
- shard-dg2: NOTRUN -> [FAIL][84] ([i915#8292])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-11/igt@kms_plane_scaling@[email protected]

* igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0-25@pipe-d-hdmi-a-3:
- shard-dg2: NOTRUN -> [SKIP][85] ([i915#5176]) +7 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-8/igt@kms_plane_scaling@[email protected]

* igt@kms_plane_scaling@plane-downscale-with-rotation-factor-0-5@pipe-a-hdmi-a-1:
- shard-rkl: NOTRUN -> [SKIP][86] ([i915#5176]) +5 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-7/igt@kms_plane_scaling@[email protected]

* igt@kms_plane_scaling@plane-upscale-with-rotation-factor-0-25@pipe-a-hdmi-a-1:
- shard-tglu: NOTRUN -> [SKIP][87] ([i915#5176]) +3 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-tglu-7/igt@kms_plane_scaling@[email protected]

* igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-20x20@pipe-a-hdmi-a-1:
- shard-rkl: NOTRUN -> [SKIP][88] ([i915#5235]) +5 similar issues
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-7/igt@kms_plane_scaling@[email protected]

* igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-25@pipe-c-dp-4:
- shard-dg2: NOTRUN -> [SKIP][89] ([i915#5235]) +7 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-11/igt@kms_plane_scaling@[email protected]

* igt@kms_psr@psr2_primary_blt:
- shard-dg2: NOTRUN -> [SKIP][90] ([i915#1072]) +2 similar issues
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@kms_psr@psr2_primary_blt.html

* igt@kms_rotation_crc@bad-tiling:
- shard-mtlp: NOTRUN -> [SKIP][91] ([i915#4235])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@[email protected]

* igt@kms_rotation_crc@primary-y-tiled-reflect-x-90:
- shard-dg2: NOTRUN -> [SKIP][92] ([i915#4235] / [i915#5190])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@kms_tv_load_detect@load-detect:
- shard-mtlp: NOTRUN -> [SKIP][93] ([fdo#109309])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@[email protected]

* igt@kms_vblank@pipe-c-ts-continuation-suspend:
- shard-dg2: [PASS][94] -> [FAIL][95] ([fdo#103375])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-7/igt@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-11/igt@[email protected]

* igt@kms_vrr@negative-basic:
- shard-dg2: NOTRUN -> [SKIP][96] ([i915#3555])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-8/igt@[email protected]

* igt@kms_writeback@writeback-invalid-parameters:
- shard-dg2: NOTRUN -> [SKIP][97] ([i915#2437])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@[email protected]

* igt@perf@global-sseu-config-invalid:
- shard-mtlp: NOTRUN -> [SKIP][98] ([i915#7387])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-7/igt@[email protected]

* igt@perf@stress-open-close@0-rcs0:
- shard-glk: [PASS][99] -> [ABORT][100] ([i915#5213] / [i915#7941])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-glk8/igt@perf@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-glk9/igt@perf@[email protected]

* igt@prime_mmap@test_aperture_limit@test_aperture_limit-smem:
- shard-dg2: NOTRUN -> [INCOMPLETE][101] ([i915#5493])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@prime_mmap@test_aperture_limit@test_aperture_limit-smem.html

* igt@prime_vgem@basic-blt:
- shard-mtlp: NOTRUN -> [FAIL][102] ([i915#8445])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-1/igt@[email protected]

* igt@v3d/v3d_submit_cl@bad-extension:
- shard-tglu: NOTRUN -> [SKIP][103] ([fdo#109315] / [i915#2575])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-tglu-7/igt@v3d/[email protected]

* igt@v3d/v3d_submit_cl@bad-multisync-pad:
- shard-mtlp: NOTRUN -> [SKIP][104] ([i915#2575]) +1 similar issue
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@v3d/[email protected]

* igt@v3d/v3d_submit_cl@valid-multisync-submission:
- shard-dg2: NOTRUN -> [SKIP][105] ([i915#2575]) +3 similar issues
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@v3d/[email protected]

* igt@vc4/vc4_wait_bo@used-bo-1ns:
- shard-dg2: NOTRUN -> [SKIP][106] ([i915#7711]) +1 similar issue
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-12/igt@vc4/[email protected]

#### Possible fixes ####

* igt@drm_fdinfo@most-busy-idle-check-all@rcs0:
- shard-rkl: [FAIL][107] ([i915#7742]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-rkl-6/igt@drm_fdinfo@[email protected]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-7/igt@drm_fdinfo@[email protected]

* igt@gem_busy@close-race:
- shard-dg2: [ABORT][109] ([i915#6016] / [i915#7349]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-8/igt@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-1/igt@[email protected]

* igt@gem_create@hog-create@smem0:
- shard-dg2: [FAIL][111] ([i915#5892]) -> [PASS][112]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-1/igt@gem_create@[email protected]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-10/igt@gem_create@[email protected]

* igt@gem_ctx_exec@basic-nohangcheck:
- shard-rkl: [FAIL][113] ([i915#6268]) -> [PASS][114]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-rkl-7/igt@[email protected]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-2/igt@[email protected]

* igt@gem_ctx_isolation@preservation-s3@ccs0:
- shard-mtlp: [FAIL][115] ([fdo#103375]) -> [PASS][116]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-4/igt@gem_ctx_isolation@[email protected]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-7/igt@gem_ctx_isolation@[email protected]

* igt@gem_exec_balancer@hang:
- shard-mtlp: [ABORT][117] ([i915#8104]) -> [PASS][118]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-2/igt@[email protected]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@[email protected]

* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl: [FAIL][119] ([i915#2842]) -> [PASS][120]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-apl1/igt@gem_exec_fair@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-apl2/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-none@vcs0:
- shard-rkl: [FAIL][121] ([i915#2842]) -> [PASS][122] +1 similar issue
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-rkl-7/igt@gem_exec_fair@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-6/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglu: [FAIL][123] ([i915#2842]) -> [PASS][124]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-tglu-9/igt@gem_exec_fair@[email protected]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-tglu-9/igt@gem_exec_fair@[email protected]

* igt@gem_exec_schedule@deep@vcs1:
- shard-mtlp: [FAIL][125] ([i915#8606]) -> [PASS][126]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-1/igt@gem_exec_schedule@[email protected]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-8/igt@gem_exec_schedule@[email protected]

* igt@gem_exec_suspend@basic-s4-devices@smem:
- shard-tglu: [ABORT][127] ([i915#7975] / [i915#8213]) -> [PASS][128]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-tglu-10/igt@gem_exec_suspend@[email protected]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-tglu-7/igt@gem_exec_suspend@[email protected]

* igt@gem_exec_whisper@basic-contexts-forked-all:
- shard-mtlp: [TIMEOUT][129] ([i915#8628]) -> [PASS][130]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-3/igt@[email protected]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-5/igt@[email protected]

* igt@gem_exec_whisper@basic-forked-all:
- shard-mtlp: [FAIL][131] ([i915#6363]) -> [PASS][132]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-5/igt@[email protected]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-8/igt@[email protected]

* igt@gem_lmem_swapping@smem-oom@lmem0:
- {shard-dg1}: [TIMEOUT][133] ([i915#5493]) -> [PASS][134]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg1-14/igt@gem_lmem_swapping@[email protected]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg1-12/igt@gem_lmem_swapping@[email protected]

* igt@i915_pipe_stress@stress-xrgb8888-untiled:
- shard-mtlp: [FAIL][135] ([i915#8691]) -> [PASS][136]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-1/igt@[email protected]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-3/igt@[email protected]

* {igt@i915_pm_freq_api@freq-suspend@gt0}:
- shard-dg2: [FAIL][137] ([fdo#103375]) -> [PASS][138] +1 similar issue
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-10/igt@i915_pm_freq_api@[email protected]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-10/igt@i915_pm_freq_api@[email protected]

* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-hdmi-a:
- {shard-dg1}: [SKIP][139] ([i915#1937]) -> [PASS][140]
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg1-13/igt@i915_pm_lpsp@[email protected]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg1-19/igt@i915_pm_lpsp@[email protected]

* igt@i915_pm_rc6_residency@rc6-idle@vecs0:
- {shard-dg1}: [FAIL][141] ([i915#3591]) -> [PASS][142]
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg1-18/igt@i915_pm_rc6_residency@[email protected]
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg1-16/igt@i915_pm_rc6_residency@[email protected]

* igt@i915_pm_rpm@dpms-lpsp:
- shard-rkl: [SKIP][143] ([i915#1397]) -> [PASS][144]
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-rkl-6/igt@[email protected]
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-7/igt@[email protected]

* igt@i915_pm_rpm@modeset-lpsp-stress-no-wait:
- {shard-dg1}: [SKIP][145] ([i915#1397]) -> [PASS][146] +1 similar issue
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg1-13/igt@[email protected]
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg1-19/igt@[email protected]

* igt@i915_pm_rpm@modeset-non-lpsp-stress-no-wait:
- shard-dg2: [SKIP][147] ([i915#1397]) -> [PASS][148] +2 similar issues
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-12/igt@[email protected]
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-1/igt@[email protected]

* igt@i915_selftest@live@gt_mocs:
- shard-mtlp: [DMESG-FAIL][149] ([i915#7059]) -> [PASS][150]
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-1/igt@i915_selftest@live@gt_mocs.html
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-8/igt@i915_selftest@live@gt_mocs.html

* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-async-flip:
- shard-mtlp: [FAIL][151] ([i915#3743]) -> [PASS][152]
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-2/igt@[email protected]
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@[email protected]

* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-mtlp: [FAIL][153] ([i915#5138]) -> [PASS][154]
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-5/igt@[email protected]
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-8/igt@[email protected]

* igt@kms_flip@flip-vs-expired-vblank@a-hdmi-a1:
- shard-glk: [FAIL][155] ([i915#2122]) -> [PASS][156]
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-glk8/igt@kms_flip@[email protected]
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-glk9/igt@kms_flip@[email protected]

* igt@kms_sysfs_edid_timing:
- shard-dg2: [FAIL][157] ([IGT#2]) -> [PASS][158]
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-7/igt@kms_sysfs_edid_timing.html
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-11/igt@kms_sysfs_edid_timing.html

* igt@perf@non-zero-reason@0-rcs0:
- shard-dg2: [FAIL][159] ([i915#7484]) -> [PASS][160]
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-8/igt@perf@[email protected]
[160]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-10/igt@perf@[email protected]

#### Warnings ####

* igt@kms_async_flips@crc@pipe-d-edp-1:
- shard-mtlp: [DMESG-FAIL][161] ([i915#8561]) -> [FAIL][162] ([i915#8247])
[161]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-7/igt@kms_async_flips@[email protected]
[162]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-3/igt@kms_async_flips@[email protected]

* igt@kms_content_protection@mei_interface:
- shard-dg2: [SKIP][163] ([i915#7118]) -> [SKIP][164] ([i915#7118] / [i915#7162])
[163]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-dg2-10/igt@kms_content_protection@mei_interface.html
[164]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-dg2-11/igt@kms_content_protection@mei_interface.html

* igt@kms_fbcon_fbt@psr:
- shard-rkl: [SKIP][165] ([i915#3955]) -> [SKIP][166] ([fdo#110189] / [i915#3955])
[165]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-rkl-7/igt@[email protected]
[166]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-2/igt@[email protected]

* igt@kms_multipipe_modeset@basic-max-pipe-crc-check:
- shard-rkl: [SKIP][167] ([i915#4816]) -> [SKIP][168] ([i915#4070] / [i915#4816])
[167]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-rkl-7/igt@[email protected]
[168]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-rkl-6/igt@[email protected]

* igt@sysfs_timeslice_duration@timeout@vecs0:
- shard-mtlp: [TIMEOUT][169] ([i915#6950]) -> [ABORT][170] ([i915#8521])
[169]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13340/shard-mtlp-8/igt@sysfs_timeslice_duration@[email protected]
[170]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120086v1/shard-mtlp-2/igt@sysfs_timeslice_duration@[email protected]

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

[IGT#2]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/2
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109309]: https://bugs.freedesktop.org/show_bug.cgi?id=109309
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111767]: https://bugs.freedesktop.org/show_bug.cgi?id=111767
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1937]: https://gitlab.freedesktop.org/drm/intel/issues/1937
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3539]: https://gitlab.freedesktop.org/drm/intel/issues/3539
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3591]: https://gitlab.freedesktop.org/drm/intel/issues/3591
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3743]: https://gitlab.freedesktop.org/drm/intel/issues/3743
[i915#3804]: https://gitlab.freedesktop.org/drm/intel/issues/3804
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4087]: https://gitlab.freedesktop.org/drm/intel/issues/4087
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213
[i915#4235]: https://gitlab.freedesktop.org/drm/intel/issues/4235
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4349]: https://gitlab.freedesktop.org/drm/intel/issues/4349
[i915#4391]: https://gitlab.freedesktop.org/drm/intel/issues/4391
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#4812]: https://gitlab.freedesktop.org/drm/intel/issues/4812
[i915#4816]: https://gitlab.freedesktop.org/drm/intel/issues/4816
[i915#4852]: https://gitlab.freedesktop.org/drm/intel/issues/4852
[i915#5138]: https://gitlab.freedesktop.org/drm/intel/issues/5138
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5190]: https://gitlab.freedesktop.org/drm/intel/issues/5190
[i915#5213]: https://gitlab.freedesktop.org/drm/intel/issues/5213
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5354]: https://gitlab.freedesktop.org/drm/intel/issues/5354
[i915#5493]: https://gitlab.freedesktop.org/drm/intel/issues/5493
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#5784]: https://gitlab.freedesktop.org/drm/intel/issues/5784
[i915#5892]: https://gitlab.freedesktop.org/drm/intel/issues/5892
[i915#6016]: https://gitlab.freedesktop.org/drm/intel/issues/6016
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6295]: https://gitlab.freedesktop.org/drm/intel/issues/6295
[i915#6363]: https://gitlab.freedesktop.org/drm/intel/issues/6363
[i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
[i915#6880]: https://gitlab.freedesktop.org/drm/intel/issues/6880
[i915#6950]: https://gitlab.freedesktop.org/drm/intel/issues/6950
[i915#7059]: https://gitlab.freedesktop.org/drm/intel/issues/7059
[i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118
[i915#7162]: https://gitlab.freedesktop.org/drm/intel/issues/7162
[i915#7349]: https://gitlab.freedesktop.org/drm/intel/issues/7349
[i915#7387]: https://gitlab.freedesktop.org/drm/intel/issues/7387
[i915#7484]: https://gitlab.freedesktop.org/drm/intel/issues/7484
[i915#7697]: https://gitlab.freedesktop.org/drm/intel/issues/7697
[i915#7711]: https://gitlab.freedesktop.org/drm/intel/issues/7711
[i915#7742]: https://gitlab.freedesktop.org/drm/intel/issues/7742
[i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#7941]: https://gitlab.freedesktop.org/drm/intel/issues/7941
[i915#7975]: https://gitlab.freedesktop.org/drm/intel/issues/7975
[i915#8104]: https://gitlab.freedesktop.org/drm/intel/issues/8104
[i915#8213]: https://gitlab.freedesktop.org/drm/intel/issues/8213
[i915#8247]: https://gitlab.freedesktop.org/drm/intel/issues/8247
[i915#8292]: https://gitlab.freedesktop.org/drm/intel/issues/8292
[i915#8428]: https://gitlab.freedesktop.org/drm/intel/issues/8428
[i915#8445]: https://gitlab.freedesktop.org/drm/intel/issues/8445
[i915#8502]: https://gitlab.freedesktop.org/drm/intel/issues/8502
[i915#8521]: https://gitlab.freedesktop.org/drm/intel/issues/8521
[i915#8561]: https://gitlab.freedesktop.org/drm/intel/issues/8561
[i915#8606]: https://gitlab.freedesktop.org/drm/intel/issues/8606
[i915#8621]: https://gitlab.freedesktop.org/drm/intel/issues/8621
[i915#8628]: https://gitlab.freedesktop.org/drm/intel/issues/8628
[i915#8661]: https://gitlab.freedesktop.org/drm/intel/issues/8661
[i915#8682]: https://gitlab.freedesktop.org/drm/intel/issues/8682
[i915#8691]: https://gitlab.freedesktop.org/drm/intel/issues/8691
[i915#8708]: https://gitlab.freedesktop.org/drm/intel/issues/8708
[i915#8709]: https://gitlab.freedesktop.org/drm/intel/issues/8709
[i915#8761]: https://gitlab.freedesktop.org/drm/intel/issues/8761

Build changes
-------------

* Linux: CI_DRM_13340 -> Patchwork_120086v1

CI-20190529: 20190529
CI_DRM_13340: a3b671a5e12f1fd972ad7046f39a470acbefbbdc @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7357: 790f69303f49066b150fbdff95e471e14d046710 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_120086v1: a3b671a5e12f1fd972ad7046f39a470acbefbbdc @ 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_120086v1/index.html

#14 lore raw
In reply to Nirmoy Das

Hi Nirmoy,

The changes in this series make sense to me. I searched my code base, there are a few other places where stolen memory is allocated:

1) intel_dpt_create: I don't know what is dpt. Should we also consider this one? Maybe we never read from cpu?
2) create_ring_vma: I think cpu only write ring buffer but never read it. So should be okay.
3) vlv_rc6_init
4) there are a few places calling i915_gem_object_create_stolen_for_preallocated. I think this is also stolen memory?

For integrated gpu like MTL, do we use stolen memory for ggtt? If yes, does CPU only write ggtt/never read?

Thanks,
Oak

Quoted 40 lines

-----Original Message-----
From: Das, Nirmoy <[email protected]>
Sent: June 30, 2023 1:02 PM
To: [email protected]
Cc: Das, Nirmoy <[email protected]>; Zeng, Oak <[email protected]>; Jani Nikula <[email protected]>; Joonas Lahtinen <[email protected]>; Andi Shyti <[email protected]>; Hajda, Andrzej <[email protected]>
Subject: [PATCH 1/2] drm/i915/gt: Do not use stolen on MTL

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>
---
 drivers/gpu/drm/i915/gt/intel_gt.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/gt/intel_gt.c +1 -1
index 33a61046ba58..9f64d61dd5fc 100644
@@ -466,7 +466,7 @@ static int intel_gt_init_scratch(struct intel_gt *gt, unsigned
 int size)
 	obj = i915_gem_object_create_lmem(i915, size,
 					  I915_BO_ALLOC_VOLATILE |
 					  I915_BO_ALLOC_GPU_ONLY);
-	if (IS_ERR(obj))
+	if (IS_ERR(obj) && !IS_METEORLAKE(i915)) /* Wa_22018444074 */
 		obj = i915_gem_object_create_stolen(i915, size);
 	if (IS_ERR(obj))

obj = i915_gem_object_create_internal(i915, size);
--
2.39.0

#15 lore raw

Hi Oak,

Quoted 3 lines · Oak

Hi Nirmoy,

The changes in this series make sense to me. I searched my code base, there are a few other places where stolen memory is allocated:

Thanks for checking all the places.

Quoted 2 lines

1) intel_dpt_create: I don't know what is dpt. Should we also consider this one? Maybe we never read from cpu?

This expects i915_ggtt_has_aperture() which MTL doesn't have.

Quoted 1 line

2) create_ring_vma: I think cpu only write ring buffer but never read it. So should be okay.

Same as above.

Quoted 1 line

3) vlv_rc6_init

This  seems to be only for IS_VALLEYVIEW().

Quoted 1 line

4) there are a few places calling i915_gem_object_create_stolen_for_preallocated. I think this is also stolen memory?

Where is this from, do you mean I915_BO_PREALLOC ?

Quoted 2 lines

For integrated gpu like MTL, do we use stolen memory for ggtt? If yes, does CPU only write ggtt/never read?

GTT pages only seems to be written.

Thanks,

Nirmoy

Quoted 44 lines

Thanks,
Oak

Quoted 40 lines

-----Original Message-----
From: Das, Nirmoy <[email protected]>
Sent: June 30, 2023 1:02 PM
To: [email protected]
Cc: Das, Nirmoy <[email protected]>; Zeng, Oak <[email protected]>; Jani Nikula <[email protected]>; Joonas Lahtinen <[email protected]>; Andi Shyti <[email protected]>; Hajda, Andrzej <[email protected]>
Subject: [PATCH 1/2] drm/i915/gt: Do not use stolen on MTL

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>
---
  drivers/gpu/drm/i915/gt/intel_gt.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/gt/intel_gt.c +1 -1
index 33a61046ba58..9f64d61dd5fc 100644
@@ -466,7 +466,7 @@ static int intel_gt_init_scratch(struct intel_gt *gt, unsigned
 int size)
  	obj = i915_gem_object_create_lmem(i915, size,
  					  I915_BO_ALLOC_VOLATILE |
  					  I915_BO_ALLOC_GPU_ONLY);
-	if (IS_ERR(obj))
+	if (IS_ERR(obj) && !IS_METEORLAKE(i915)) /* Wa_22018444074 */
  		obj = i915_gem_object_create_stolen(i915, size);
  	if (IS_ERR(obj))

obj = i915_gem_object_create_internal(i915, size);
--
2.39.0

#16 lore raw

Thanks,
Oak

Quoted 23 lines

-----Original Message-----
From: Nirmoy Das <[email protected]>
Sent: July 4, 2023 11:31 AM
To: Zeng, Oak <[email protected]>; Das, Nirmoy <[email protected]>; [email protected]
Cc: Hajda, Andrzej <[email protected]>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/gt: Do not use stolen on MTL

Hi Oak,

Quoted 3 lines · Oak

Hi Nirmoy,

The changes in this series make sense to me. I searched my code base, there

are a few other places where stolen memory is allocated:
Thanks for checking all the places.

Quoted 2 lines

1) intel_dpt_create: I don't know what is dpt. Should we also consider this one?

Maybe we never read from cpu?
This expects i915_ggtt_has_aperture() which MTL doesn't have.

Quoted 1 line

2) create_ring_vma: I think cpu only write ring buffer but never read it. So

should be okay.
Same as above.

Quoted 7 lines
Quoted 1 line

3) vlv_rc6_init

This  seems to be only for IS_VALLEYVIEW().

Quoted 1 line

4) there are a few places calling

i915_gem_object_create_stolen_for_preallocated. I think this is also stolen memory?

Where is this from, do you mean I915_BO_PREALLOC ?

I looked some internal code, and just realized upstream code is different 😊

Quoted 7 lines
Quoted 4 lines

For integrated gpu like MTL, do we use stolen memory for ggtt? If yes, does

CPU only write ggtt/never read?

GTT pages only seems to be written.

Thanks for explaining. Series is Reviewed-by: Oak Zeng <[email protected]>

Quoted 52 lines

Thanks,

Nirmoy

Quoted 9 lines

Thanks,
Oak

Quoted 5 lines

-----Original Message-----
From: Das, Nirmoy <[email protected]>
Sent: June 30, 2023 1:02 PM
To: [email protected]
Cc: Das, Nirmoy <[email protected]>; Zeng, Oak <[email protected]>;

Jani

Quoted 18 lines
Quoted 18 lines

Nikula <[email protected]>; Joonas Lahtinen <[email protected]>; Andi Shyti <[email protected]>; Hajda, Andrzej <[email protected]>
Subject: [PATCH 1/2] drm/i915/gt: Do not use stolen on MTL

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>
---
  drivers/gpu/drm/i915/gt/intel_gt.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 6 lines

drivers/gpu/drm/i915/gt/intel_gt.c static int intel_gt_init_scratch(struct intel_gt *gt,

Quoted 6 lines
drivers/gpu/drm/i915/gt/intel_gt.c +0 -0
index 33a61046ba58..9f64d61dd5fc 100644
@@ -466,7 +466,7 @@ static int intel_gt_init_scratch(struct intel_gt *gt,

unsigned

Quoted 11 lines
Quoted 11 lines
drivers/gpu/drm/i915/gt/intel_gt.c +1 -1
 int size)
  	obj = i915_gem_object_create_lmem(i915, size,
  					  I915_BO_ALLOC_VOLATILE |
  					  I915_BO_ALLOC_GPU_ONLY);
-	if (IS_ERR(obj))
+	if (IS_ERR(obj) && !IS_METEORLAKE(i915)) /* Wa_22018444074 */
  		obj = i915_gem_object_create_stolen(i915, size);
  	if (IS_ERR(obj))

obj = i915_gem_object_create_internal(i915, size);
--
2.39.0

#17 lore raw
In reply to Zeng, Oak

Hi,

Quoted 8 lines · Oak

Hi Nirmoy,

The changes in this series make sense to me. I searched my code base, there are a few other places where stolen memory is allocated:

1) intel_dpt_create: I don't know what is dpt. Should we also consider this one? Maybe we never read from cpu?
2) create_ring_vma: I think cpu only write ring buffer but never read it. So should be okay.
3) vlv_rc6_init
4) there are a few places calling i915_gem_object_create_stolen_for_preallocated. I think this is also stolen memory?

sounds like we need a wrapper?

Andi

Quoted 45 lines

For integrated gpu like MTL, do we use stolen memory for ggtt? If yes, does CPU only write ggtt/never read?

Thanks,
Oak

Quoted 40 lines

-----Original Message-----
From: Das, Nirmoy <[email protected]>
Sent: June 30, 2023 1:02 PM
To: [email protected]
Cc: Das, Nirmoy <[email protected]>; Zeng, Oak <[email protected]>; Jani Nikula <[email protected]>; Joonas Lahtinen <[email protected]>; Andi Shyti <[email protected]>; Hajda, Andrzej <[email protected]>
Subject: [PATCH 1/2] drm/i915/gt: Do not use stolen on MTL

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>
---
 drivers/gpu/drm/i915/gt/intel_gt.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/gt/intel_gt.c +1 -1
index 33a61046ba58..9f64d61dd5fc 100644
@@ -466,7 +466,7 @@ static int intel_gt_init_scratch(struct intel_gt *gt, unsigned
 int size)
 	obj = i915_gem_object_create_lmem(i915, size,
 					  I915_BO_ALLOC_VOLATILE |
 					  I915_BO_ALLOC_GPU_ONLY);
-	if (IS_ERR(obj))
+	if (IS_ERR(obj) && !IS_METEORLAKE(i915)) /* Wa_22018444074 */
 		obj = i915_gem_object_create_stolen(i915, size);
 	if (IS_ERR(obj))

obj = i915_gem_object_create_internal(i915, size);
--
2.39.0

Reviewed-by on v1 1/2
#18 lore raw
In reply to Nirmoy Das
Quoted 9 lines · Nirmoy Das

Use smem on MTL due to a HW bug in MTL that prevents reading from stolen memory using LMEM BAR.

Cc Oak Zeng <[email protected]>
Cc Jani Nikula <[email protected]>
Cc Joonas Lahtinen <[email protected]>
Cc Andi Shyti <[email protected]>
Cc Andrzej Hajda <[email protected]>

Regards
Andrzej

Quoted 17 lines
---
  drivers/gpu/drm/i915/gt/intel_gt.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/gt/intel_gt.c +1 -1
index 33a61046ba58..9f64d61dd5fc 100644
@@ -466,7 +466,7 @@ static int intel_gt_init_scratch(struct intel_gt *gt, unsigned int size)
  	obj = i915_gem_object_create_lmem(i915, size,
  					  I915_BO_ALLOC_VOLATILE |
  					  I915_BO_ALLOC_GPU_ONLY);
-	if (IS_ERR(obj))
+	if (IS_ERR(obj) && !IS_METEORLAKE(i915)) /* Wa_22018444074 */
  		obj = i915_gem_object_create_stolen(i915, size);
  	if (IS_ERR(obj))
  		obj = i915_gem_object_create_internal(i915, size);