Add atomic DRM cursor hotspot test

PATCH Superseded Albert Esteve 5 participants 16 messages Jul 21, 2023 – Jul 28, 2023 Library code

lore

Share & tools

lore

Albert Esteve

author

2023-07-21 13:05 UTC #0 lore raw

cover Add atomic DRM cursor hotspot test

Add test to verify the kernel patch at [1].

The test modifies the hotspot x and y properties and checks that they get properly updated after every display commit.

The first git commit updating the drm header shall be removed, and update the header properly after the kernel patch has landed.

[1] - https://lists.freedesktop.org/archives/dri-devel/2023-July/414509.html

Albert Esteve (3):
drm header update: temp commit
igt_kms: add hotspot plane property
kms_cursor_legacy: modeset-atomic-cursor-hotspot

 include/drm-uapi/drm.h    | 54 +++++++++++++++++++++++++++-
 lib/igt_kms.c             |  9 +++++
 lib/igt_kms.h             |  4 ++-
 tests/kms_cursor_legacy.c | 75 +++++++++++++++++++++++++++++++++++++++
 4 files changed, 140 insertions(+), 2 deletions(-)

Signature · 1 line

2.40.0

Albert Esteve

author

2023-07-21 13:05 UTC #1 lore raw

PATCH 1/3 drm header update: temp commit

Update the drm included header to obtain VIRTUAL_CURSOR_PLANE capability and be able to test cursor hotspot setting.

This commit should be removed once the kernel patch is applied and update the headers as appropiate.

Signed-off-by Albert Esteve <[email protected]>

---
 include/drm-uapi/drm.h | 54 +++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 53 insertions(+), 1 deletion(-)

include/drm-uapi/drm.h +53 -1

index 5e54c3aa4..57b261a45 100644
@@ -35,7 +35,13 @@
 #ifndef _DRM_H_
 #define _DRM_H_
 
-#if   defined(__linux__)
+#if defined(__KERNEL__)
+
+#include <linux/types.h>
+#include <asm/ioctl.h>
+typedef unsigned int drm_handle_t;
+
+#elif defined(__linux__)
 
 #include <linux/types.h>
 #include <asm/ioctl.h>

@@ -830,6 +836,32 @@ struct drm_get_cap {
  */
 #define DRM_CLIENT_CAP_WRITEBACK_CONNECTORS	5
 
+/**
+ * DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT
+ *
+ * Drivers for para-virtualized hardware (e.g. vmwgfx, qxl, virtio and
+ * virtualbox) have additional restrictions for cursor planes (thus
+ * making cursor planes on those drivers not truly universal,) e.g.
+ * they need cursor planes to act like one would expect from a mouse
+ * cursor and have correctly set hotspot properties.
+ * If this client cap is not set the DRM core will hide cursor plane on
+ * those virtualized drivers because not setting it implies that the
+ * client is not capable of dealing with those extra restictions.
+ * Clients which do set cursor hotspot and treat the cursor plane
+ * like a mouse cursor should set this property.
+ * The client must enable &DRM_CLIENT_CAP_ATOMIC first.
+ *
+ * Setting this property on drivers which do not special case
+ * cursor planes (i.e. non-virtualized drivers) will return
+ * EOPNOTSUPP, which can be used by userspace to gauge
+ * requirements of the hardware/drivers they're running on.
+ *
+ * This capability is always supported for atomic-capable virtualized
+ * drivers starting from kernel version 6.6.
+ */
+#define DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT	6
+
+
 /* DRM_IOCTL_SET_CLIENT_CAP ioctl argument type */
 struct drm_set_client_cap {
 	__u64 capability;

@@ -1090,6 +1122,24 @@ extern "C" {
 #define DRM_IOCTL_SYNCOBJ_TRANSFER	DRM_IOWR(0xCC, struct drm_syncobj_transfer)
 #define DRM_IOCTL_SYNCOBJ_TIMELINE_SIGNAL	DRM_IOWR(0xCD, struct drm_syncobj_timeline_array)
 
+/**
+ * DRM_IOCTL_MODE_GETFB2 - Get framebuffer metadata.
+ *
+ * This queries metadata about a framebuffer. User-space fills
+ * &drm_mode_fb_cmd2.fb_id as the input, and the kernels fills the rest of the
+ * struct as the output.
+ *
+ * If the client is DRM master or has &CAP_SYS_ADMIN, &drm_mode_fb_cmd2.handles
+ * will be filled with GEM buffer handles. Planes are valid until one has a
+ * zero handle -- this can be used to compute the number of planes.
+ *
+ * Otherwise, &drm_mode_fb_cmd2.handles will be zeroed and planes are valid
+ * until one has a zero &drm_mode_fb_cmd2.pitches.
+ *
+ * If the framebuffer has a format modifier, &DRM_MODE_FB_MODIFIERS will be set
+ * in &drm_mode_fb_cmd2.flags and &drm_mode_fb_cmd2.modifier will contain the
+ * modifier. Otherwise, user-space must ignore &drm_mode_fb_cmd2.modifier.
+ */
 #define DRM_IOCTL_MODE_GETFB2		DRM_IOWR(0xCE, struct drm_mode_fb_cmd2)
 
 /*

@@ -1144,6 +1194,7 @@ struct drm_event_crtc_sequence {
 };
 
 /* typedef area */
+#ifndef __KERNEL__
 typedef struct drm_clip_rect drm_clip_rect_t;
 typedef struct drm_drawable_info drm_drawable_info_t;
 typedef struct drm_tex_region drm_tex_region_t;

@@ -1185,6 +1236,7 @@ typedef struct drm_agp_binding drm_agp_binding_t;
 typedef struct drm_agp_info drm_agp_info_t;
 typedef struct drm_scatter_gather drm_scatter_gather_t;
 typedef struct drm_set_version drm_set_version_t;
+#endif
 
 #if defined(__cplusplus)
 }

Signature · 1 line

2.40.0

Zbigniew Kempczyński

2023-07-28 07:41 UTC #2 lore raw

Re: [igt-dev] [PATCH 1/3] drm header update: temp commit

Quoted 4 lines · Albert Esteve

Update the drm included header to obtain VIRTUAL_CURSOR_PLANE capability and be able to test cursor hotspot setting.

Quoted 9 lines

This commit should be removed once the kernel patch is applied and update the headers as appropiate.
Signed-off-by Albert Esteve <[email protected]>
---
 include/drm-uapi/drm.h | 54 +++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 53 insertions(+), 1 deletion(-)

I'm sorry Albert but we don't allow to add not accepted changes upstream regarding uapi headers. Only verbatim copy of uapi headers may land in igt.

In patch [PATCH 2/3] igt_kms: add hotspot plane property you're unconditionally using definition which doesn't exists upstream yet. Likely it will just return from ioctl but I got doubts it should be written this way.

I would suggest to introduce:

#define LOCAL_DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT▸ 6

in igt_kms.h instead drm.h. And when drm.h will land in igt remove this localized definition replacing with official one.

--
Zbigniew

Quoted 96 lines

include/drm-uapi/drm.h +53 -1

index 5e54c3aa4..57b261a45 100644
@@ -35,7 +35,13 @@
 #ifndef _DRM_H_
 #define _DRM_H_
 
-#if   defined(__linux__)
+#if defined(__KERNEL__)
+
+#include <linux/types.h>
+#include <asm/ioctl.h>
+typedef unsigned int drm_handle_t;
+
+#elif defined(__linux__)
 
 #include <linux/types.h>
 #include <asm/ioctl.h>

@@ -830,6 +836,32 @@ struct drm_get_cap {
  */
 #define DRM_CLIENT_CAP_WRITEBACK_CONNECTORS	5
 
+/**
+ * DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT
+ *
+ * Drivers for para-virtualized hardware (e.g. vmwgfx, qxl, virtio and
+ * virtualbox) have additional restrictions for cursor planes (thus
+ * making cursor planes on those drivers not truly universal,) e.g.
+ * they need cursor planes to act like one would expect from a mouse
+ * cursor and have correctly set hotspot properties.
+ * If this client cap is not set the DRM core will hide cursor plane on
+ * those virtualized drivers because not setting it implies that the
+ * client is not capable of dealing with those extra restictions.
+ * Clients which do set cursor hotspot and treat the cursor plane
+ * like a mouse cursor should set this property.
+ * The client must enable &DRM_CLIENT_CAP_ATOMIC first.
+ *
+ * Setting this property on drivers which do not special case
+ * cursor planes (i.e. non-virtualized drivers) will return
+ * EOPNOTSUPP, which can be used by userspace to gauge
+ * requirements of the hardware/drivers they're running on.
+ *
+ * This capability is always supported for atomic-capable virtualized
+ * drivers starting from kernel version 6.6.
+ */
+#define DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT	6
+
+
 /* DRM_IOCTL_SET_CLIENT_CAP ioctl argument type */
 struct drm_set_client_cap {
 	__u64 capability;

@@ -1090,6 +1122,24 @@ extern "C" {
 #define DRM_IOCTL_SYNCOBJ_TRANSFER	DRM_IOWR(0xCC, struct drm_syncobj_transfer)
 #define DRM_IOCTL_SYNCOBJ_TIMELINE_SIGNAL	DRM_IOWR(0xCD, struct drm_syncobj_timeline_array)
 
+/**
+ * DRM_IOCTL_MODE_GETFB2 - Get framebuffer metadata.
+ *
+ * This queries metadata about a framebuffer. User-space fills
+ * &drm_mode_fb_cmd2.fb_id as the input, and the kernels fills the rest of the
+ * struct as the output.
+ *
+ * If the client is DRM master or has &CAP_SYS_ADMIN, &drm_mode_fb_cmd2.handles
+ * will be filled with GEM buffer handles. Planes are valid until one has a
+ * zero handle -- this can be used to compute the number of planes.
+ *
+ * Otherwise, &drm_mode_fb_cmd2.handles will be zeroed and planes are valid
+ * until one has a zero &drm_mode_fb_cmd2.pitches.
+ *
+ * If the framebuffer has a format modifier, &DRM_MODE_FB_MODIFIERS will be set
+ * in &drm_mode_fb_cmd2.flags and &drm_mode_fb_cmd2.modifier will contain the
+ * modifier. Otherwise, user-space must ignore &drm_mode_fb_cmd2.modifier.
+ */
 #define DRM_IOCTL_MODE_GETFB2		DRM_IOWR(0xCE, struct drm_mode_fb_cmd2)
 
 /*

@@ -1144,6 +1194,7 @@ struct drm_event_crtc_sequence {
 };
 
 /* typedef area */
+#ifndef __KERNEL__
 typedef struct drm_clip_rect drm_clip_rect_t;
 typedef struct drm_drawable_info drm_drawable_info_t;
 typedef struct drm_tex_region drm_tex_region_t;

@@ -1185,6 +1236,7 @@ typedef struct drm_agp_binding drm_agp_binding_t;
 typedef struct drm_agp_info drm_agp_info_t;
 typedef struct drm_scatter_gather drm_scatter_gather_t;
 typedef struct drm_set_version drm_set_version_t;
+#endif
 
 #if defined(__cplusplus)
 }

Signature · 1 line

2.40.0

Albert Esteve

author

2023-07-28 07:57 UTC #3 lore raw

Re: [igt-dev] [PATCH 1/3] drm header update: temp commit

Quoted 24 lines · Zbigniew Kempczyński

Quoted 4 lines · Albert Esteve
Update the drm included header to obtain VIRTUAL_CURSOR_PLANE capability and be able to test cursor hotspot setting.
Quoted 9 lines
This commit should be removed once the kernel patch is applied and update the headers as appropiate.
Signed-off-by Albert Esteve <[email protected]>
---
 include/drm-uapi/drm.h | 54 +++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 53 insertions(+), 1 deletion(-)
I'm sorry Albert but we don't allow to add not accepted changes upstream regarding uapi headers. Only verbatim copy of uapi headers may land in igt.
In patch [PATCH 2/3] igt_kms: add hotspot plane property you're unconditionally using definition which doesn't exists upstream yet. Likely it will just return from ioctl but I got doubts it should be written this way.

Quoted 7 lines

I would suggest to introduce:
#define LOCAL_DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT▸ 6
in igt_kms.h instead drm.h. And when drm.h will land in igt remove this localized definition replacing with official one.

Hi Zbigniew,

Sure, that is why I mention in the commit that it should be removed once the kernel patch lands.

There is a dependency, and I was not expecting this patch to be upstreamed before the kernel patch lands.

But I'm ok with your suggestion. It will result in a cleaner patch to review :)

Thanks!

Quoted 112 lines

--
Zbigniew

Quoted 53 lines

include/drm-uapi/drm.h +33 -1

index 5e54c3aa4..57b261a45 100644
@@ -35,7 +35,13 @@
 #ifndef _DRM_H_
 #define _DRM_H_
 
-#if   defined(__linux__)
+#if defined(__KERNEL__)
+
+#include <linux/types.h>
+#include <asm/ioctl.h>
+typedef unsigned int drm_handle_t;
+
+#elif defined(__linux__)
 
 #include <linux/types.h>
 #include <asm/ioctl.h>

@@ -830,6 +836,32 @@ struct drm_get_cap {
  */
 #define DRM_CLIENT_CAP_WRITEBACK_CONNECTORS  5
 
+/**
+ * DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT
+ *
+ * Drivers for para-virtualized hardware (e.g. vmwgfx, qxl, virtio and
+ * virtualbox) have additional restrictions for cursor planes (thus
+ * making cursor planes on those drivers not truly universal,) e.g.
+ * they need cursor planes to act like one would expect from a mouse
+ * cursor and have correctly set hotspot properties.
+ * If this client cap is not set the DRM core will hide cursor plane on
+ * those virtualized drivers because not setting it implies that the
+ * client is not capable of dealing with those extra restictions.
+ * Clients which do set cursor hotspot and treat the cursor plane
+ * like a mouse cursor should set this property.
+ * The client must enable &DRM_CLIENT_CAP_ATOMIC first.
+ *
+ * Setting this property on drivers which do not special case
+ * cursor planes (i.e. non-virtualized drivers) will return
+ * EOPNOTSUPP, which can be used by userspace to gauge
+ * requirements of the hardware/drivers they're running on.
+ *
+ * This capability is always supported for atomic-capable virtualized
+ * drivers starting from kernel version 6.6.
+ */
+#define DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT  6
+
+
 /* DRM_IOCTL_SET_CLIENT_CAP ioctl argument type */
 struct drm_set_client_cap {
      __u64 capability;

include/drm-uapi/drm.h extern "C" { · line 1122

Quoted 1 line

include/drm-uapi/drm.h +0 -0

@@ -1090,6 +1122,24 @@ extern "C" {
 #define DRM_IOCTL_SYNCOBJ_TRANSFER   DRM_IOWR(0xCC, struct

drm_syncobj_transfer)

include/drm-uapi/drm.h extern "C" { · line 1123

Quoted 1 line

include/drm-uapi/drm.h +0 -0

 #define DRM_IOCTL_SYNCOBJ_TIMELINE_SIGNAL    DRM_IOWR(0xCD, struct

drm_syncobj_timeline_array)

include/drm-uapi/drm.h extern "C" {

Quoted 6 lines

include/drm-uapi/drm.h +5 -0

+/**
+ * DRM_IOCTL_MODE_GETFB2 - Get framebuffer metadata.
+ *
+ * This queries metadata about a framebuffer. User-space fills
+ * &drm_mode_fb_cmd2.fb_id as the input, and the kernels fills the rest

of the

include/drm-uapi/drm.h extern "C" {

Quoted 3 lines

include/drm-uapi/drm.h +3 -0

+ * struct as the output.
+ *
+ * If the client is DRM master or has &CAP_SYS_ADMIN,

&drm_mode_fb_cmd2.handles

include/drm-uapi/drm.h extern "C" { · line 1132

Quoted 1 line

include/drm-uapi/drm.h +1 -0

+ * will be filled with GEM buffer handles. Planes are valid until one

has a

include/drm-uapi/drm.h extern "C" {

Quoted 3 lines

include/drm-uapi/drm.h +3 -0

+ * zero handle -- this can be used to compute the number of planes.
+ *
+ * Otherwise, &drm_mode_fb_cmd2.handles will be zeroed and planes are

valid

include/drm-uapi/drm.h extern "C" {

Quoted 3 lines

include/drm-uapi/drm.h +3 -0

+ * until one has a zero &drm_mode_fb_cmd2.pitches.
+ *
+ * If the framebuffer has a format modifier, &DRM_MODE_FB_MODIFIERS

will be set

include/drm-uapi/drm.h extern "C" { · line 1139

Quoted 1 line

include/drm-uapi/drm.h +1 -0

+ * in &drm_mode_fb_cmd2.flags and &drm_mode_fb_cmd2.modifier will

contain the

include/drm-uapi/drm.h extern "C" { · line 1140

Quoted 1 line

include/drm-uapi/drm.h +1 -0
+ * modifier. Otherwise, user-space must ignore

&drm_mode_fb_cmd2.modifier.

include/drm-uapi/drm.h extern "C" { · line 1142

Quoted 2 lines

include/drm-uapi/drm.h +1 -0

+ */
 #define DRM_IOCTL_MODE_GETFB2                DRM_IOWR(0xCE, struct

drm_mode_fb_cmd2)

Quoted 21 lines

include/drm-uapi/drm.h +2 -1

/*

@@ -1144,6 +1194,7 @@ struct drm_event_crtc_sequence {
 };
 
 /* typedef area */
+#ifndef __KERNEL__
 typedef struct drm_clip_rect drm_clip_rect_t;
 typedef struct drm_drawable_info drm_drawable_info_t;
 typedef struct drm_tex_region drm_tex_region_t;

@@ -1185,6 +1236,7 @@ typedef struct drm_agp_binding drm_agp_binding_t;
 typedef struct drm_agp_info drm_agp_info_t;
 typedef struct drm_scatter_gather drm_scatter_gather_t;
 typedef struct drm_set_version drm_set_version_t;
+#endif
 
 #if defined(__cplusplus)
 }
--

2.40.0

Zbigniew Kempczyński

2023-07-28 08:31 UTC #4 lore raw

Re: [igt-dev] [PATCH 1/3] drm header update: temp commit

Quoted 35 lines · Albert Esteve

On Fri, Jul 28, 2023 at 9:42 AM Zbigniew Kempczyński <[email protected]> wrote:
On Fri, Jul 21, 2023 at 03:04:56PM +0200, Albert Esteve wrote:
> Update the drm included header to obtain
> VIRTUAL_CURSOR_PLANE capability and be
> able to test cursor hotspot setting.
>
> This commit should be removed once the kernel
> patch is applied and update the headers
> as appropiate.
>
> Signed-off-by: Albert Esteve <[email protected]> > ---
> include/drm-uapi/drm.h | 54
+++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 53 insertions(+), 1 deletion(-) >
I'm sorry Albert but we don't allow to add not accepted changes upstream regarding uapi headers. Only verbatim copy of uapi headers may land in igt.
In patch [PATCH 2/3] igt_kms: add hotspot plane property you're unconditionally using definition which doesn't exists upstream yet. Likely it will just return from ioctl but I got doubts it should be written this way.
I would suggest to introduce:
#define LOCAL_DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT▸ 6
in igt_kms.h instead drm.h. And when drm.h will land in igt remove this localized definition replacing with official one.

Quoted 8 lines

Hi Zbigniew,
Sure, that is why I mention in the commit that it should be removed once the kernel patch lands.
There is a dependency, and I was not expecting this patch to be upstreamed before the kernel patch lands.
But I'm ok with your suggestion. It will result in a cleaner patch to review :)
Thanks!

In the meantime I've just verified I'm not talking nonsense and it seems I'm talking. At the moment doing verbatim copy of kernel uapi headers conflicts due to missing __user definition and unresolved __packed in single place in i915_drm.h. I'm thinking how to solve this with minimal effort as I would like to avoid changes in uapi headers or have as minimum changes as possible.

--
Zbigniew

Albert Esteve

author

2023-07-21 13:05 UTC #5 lore raw

PATCH 2/3 igt_kms: add hotspot plane property

In reply to Albert Esteve

Add HOTSPOT_X and HOTSPOT_Y properties
to the atomic_plane_properties struct.

Signed-off-by Albert Esteve <[email protected]>

---
 lib/igt_kms.c | 9 +++++++++
 lib/igt_kms.h | 4 +++-
 2 files changed, 12 insertions(+), 1 deletion(-)

lib/igt_kms.c +9 -0

index f2b0eed57..0bda9ab15 100644
@@ -601,6 +601,8 @@ const char * const igt_plane_prop_names[IGT_NUM_PLANE_PROPS] = {
 	[IGT_PLANE_CRTC_Y] = "CRTC_Y",
 	[IGT_PLANE_CRTC_W] = "CRTC_W",
 	[IGT_PLANE_CRTC_H] = "CRTC_H",
+	[IGT_PLANE_HOTSPOT_X] = "HOTSPOT_X",
+	[IGT_PLANE_HOTSPOT_Y] = "HOTSPOT_Y",
 	[IGT_PLANE_FB_ID] = "FB_ID",
 	[IGT_PLANE_CRTC_ID] = "CRTC_ID",
 	[IGT_PLANE_IN_FENCE_FD] = "IN_FENCE_FD",

@@ -2296,6 +2298,11 @@ static void igt_plane_reset(igt_plane_t *plane)
 	if (igt_plane_has_prop(plane, IGT_PLANE_SCALING_FILTER))
 		igt_plane_set_prop_enum(plane, IGT_PLANE_SCALING_FILTER, "Default");
 
+	if (igt_plane_has_prop(plane, IGT_PLANE_HOTSPOT_X))
+		igt_plane_set_prop_value(plane, IGT_PLANE_HOTSPOT_X, 0);
+	if (igt_plane_has_prop(plane, IGT_PLANE_HOTSPOT_Y))
+		igt_plane_set_prop_value(plane, IGT_PLANE_HOTSPOT_Y, 0);
+
 	igt_plane_clear_prop_changed(plane, IGT_PLANE_IN_FENCE_FD);
 	plane->values[IGT_PLANE_IN_FENCE_FD] = ~0ULL;
 	plane->gem_handle = 0;

@@ -2679,6 +2686,8 @@ void igt_display_require(igt_display_t *display, int drm_fd)
 	drmSetClientCap(drm_fd, DRM_CLIENT_CAP_UNIVERSAL_PLANES, 1);
 	if (drmSetClientCap(drm_fd, DRM_CLIENT_CAP_ATOMIC, 1) == 0)
 		display->is_atomic = 1;
+	
+	drmSetClientCap(drm_fd, DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT, 1);
 
 	plane_resources = drmModeGetPlaneResources(display->drm_fd);
 	igt_assert(plane_resources);

lib/igt_kms.h +3 -1

index 1b6988c17..b64be84b3 100644
@@ -318,7 +318,9 @@ enum igt_atomic_plane_properties {
        IGT_PLANE_ZPOS,
        IGT_PLANE_FB_DAMAGE_CLIPS,
        IGT_PLANE_SCALING_FILTER,
-       IGT_NUM_PLANE_PROPS
+       IGT_PLANE_HOTSPOT_X,
+       IGT_PLANE_HOTSPOT_Y,
+       IGT_NUM_PLANE_PROPS      
 };
 
 /**

Signature · 1 line

2.40.0

Javier Martinez Canillas

Acked-by on v1 2/3

2023-07-25 13:40 UTC #6 lore raw

Re: [igt-dev] [PATCH 2/3] igt_kms: add hotspot plane property

Hello Albert,

Patch looks good to me. But I'm not really familiar with the IGT codebase.

Acked-by Javier Martinez Canillas <[email protected]>

I've one question below though:

Albert Esteve <[email protected]> writes:

[...]

lib/igt_kms.c void igt_display_require(igt_display_t *display, int drm_fd) · line 2691

Quoted 7 lines

lib/igt_kms.c +2 -0

@@ -2679,6 +2686,8 @@ void igt_display_require(igt_display_t *display, int drm_fd)
 	drmSetClientCap(drm_fd, DRM_CLIENT_CAP_UNIVERSAL_PLANES, 1);
 	if (drmSetClientCap(drm_fd, DRM_CLIENT_CAP_ATOMIC, 1) == 0)
 		display->is_atomic = 1;
+	
+	drmSetClientCap(drm_fd, DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT, 1);

Should this capability be set unconditionally?

Do we want to also test the case when user-space doesn't opt-in and does not know how to handle the hostpost properties ?

Signature · 5 lines

Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat

Albert Esteve

author

2023-07-26 14:43 UTC #7 lore raw

Re: [igt-dev] [PATCH 2/3] igt_kms: add hotspot plane property

Quoted 15 lines · Javier Martinez Canillas

Hello Albert,
Patch looks good to me. But I'm not really familiar with the IGT codebase.
Acked-by Javier Martinez Canillas <[email protected]>
I've one question below though:
Albert Esteve <[email protected]> writes:
[...]
Review void igt_display_require(igt_display_t *display,
Quoted 1 line
(quoted diff) +0 -0
@@ -2679,6 +2686,8 @@ void igt_display_require(igt_display_t *display,
int drm_fd)

Quoted 10 lines

lib/igt_kms.c void igt_display_require(igt_display_t *display, int drm_fd) · line 2691
Quoted 6 lines
lib/igt_kms.c +2 -0
      drmSetClientCap(drm_fd, DRM_CLIENT_CAP_UNIVERSAL_PLANES, 1);
      if (drmSetClientCap(drm_fd, DRM_CLIENT_CAP_ATOMIC, 1) == 0)
              display->is_atomic = 1;
+
+     drmSetClientCap(drm_fd, DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT, 1);
 
Should this capability be set unconditionally?

Probably could be set similarly to how the atomic capability is set, track the property in the display
structure, and run the hotspot test only in cases where client understands hotspot properties.
I can change this in the next drop.

Quoted 3 lines

Do we want to also test the case when user-space doesn't opt-in and does not know how to handle the hostpost properties ?

In those cases, if setting the capability fails, it is probably better to just skip the test.

Quoted 9 lines

--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat

Albert Esteve

author

2023-07-21 13:05 UTC #8 lore raw

PATCH 3/3 kms_cursor_legacy: modeset-atomic-cursor-hotspot

In reply to Albert Esteve

Add a test for modesetting an atomic cursor plane hotspot property. The test first checks if the plane is atomic and has the hotspot property. and if it does, it sets different random hot_x and hot_y values and checks that it is updated correctly after an atomic commit.

Signed-off-by Albert Esteve <[email protected]>

---
 tests/kms_cursor_legacy.c | 75 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 75 insertions(+)

tests/kms_cursor_legacy.c +75 -0

index 1ebac9d31..38258ed8d 100644
@@ -1607,6 +1607,70 @@ static void flip_vs_cursor_busy_crc(igt_display_t *display, bool atomic)
 	put_ahnd(ahnd);
 }
 
+static void modeset_atomic_cursot_hotspot(igt_display_t *display)
+{
+	struct igt_fb cursor_fb;
+	igt_output_t *output;
+	enum pipe pipe;
+	igt_plane_t *cursor = NULL;
+	bool has_hotspot_prop;
+	uint64_t width, height;
+	uint32_t hot_x, hot_y, prev_hot_x, prev_hot_y;
+
+	igt_require(display->is_atomic);
+	pipe = find_connected_pipe(display, false, &output);
+	igt_require(output);
+
+	igt_info("Using pipe %s & %s\n",
+		 kmstest_pipe_name(pipe), igt_output_name(output));
+
+	width = height = 64;
+	igt_create_color_fb(display->drm_fd, width, height, DRM_FORMAT_ARGB8888,
+			    DRM_FORMAT_MOD_LINEAR, 1., 1., 1., &cursor_fb);
+
+	igt_display_commit2(display, COMMIT_ATOMIC);
+
+	cursor = set_cursor_on_pipe(display, pipe, &cursor_fb);
+
+	has_hotspot_prop = cursor->props[IGT_PLANE_HOTSPOT_X] ||
+		cursor->props[IGT_PLANE_HOTSPOT_Y];
+	igt_require_f(has_hotspot_prop, "Cursor plane lacks the hotspot property");
+
+	/*
+	 * Change the hotspot coordinates randomly and check that the property
+	 * is updated accordingly.
+	 */
+	srand(time(NULL));
+	for (int i = 0; i < 20; i++) {
+		hot_x = rand() % width;
+		hot_y = rand() % height;
+		prev_hot_x = igt_plane_get_prop(cursor, IGT_PLANE_HOTSPOT_X);
+		prev_hot_y = igt_plane_get_prop(cursor, IGT_PLANE_HOTSPOT_Y);
+		igt_debug("Update cursor hotspot: (%d, %d)\n", hot_x, hot_y);
+		
+		/* Set cursor hotspot property values */
+		igt_output_set_prop_value(cursor, IGT_PLANE_HOTSPOT_X, hot_x);
+		igt_output_set_prop_value(cursor, IGT_PLANE_HOTSPOT_Y, hot_y);
+
+		/* Properties are not updated until the commit */
+		igt_assert_eq(igt_plane_get_prop(cursor, IGT_PLANE_HOTSPOT_X), prev_hot_x);
+		igt_assert_eq(igt_plane_get_prop(cursor, IGT_PLANE_HOTSPOT_Y), prev_hot_y);
+
+		igt_display_commit2(display, COMMIT_ATOMIC);
+
+		/* After the commit, the cursor hotspot property values are updated */
+		igt_assert_eq(igt_plane_get_prop(cursor, IGT_PLANE_HOTSPOT_X), hot_x);
+		igt_assert_eq(igt_plane_get_prop(cursor, IGT_PLANE_HOTSPOT_Y), hot_y);
+	}
+
+	/* Clean-up */
+	igt_plane_set_fb(cursor, NULL);
+	igt_output_set_pipe(output, PIPE_NONE);
+	igt_display_commit2(display, COMMIT_ATOMIC);
+
+	igt_remove_fb(display->drm_fd, &cursor_fb);
+}
+
 igt_main
 {
 	const int ncpus = sysconf(_SC_NPROCESSORS_ONLN);

@@ -1681,6 +1745,17 @@ igt_main
 			nonblocking_modeset_vs_cursor(&display, 16);
 	}
 
+	igt_describe("Test changes the cursor hotspot and checks that the "
+		      "property is updated accordignly");
+	igt_subtest_group {
+		igt_fixture {
+			igt_display_require_output(&display);
+		}
+
+		igt_subtest("modeset-atomic-cursor-hotspot")
+			modeset_atomic_cursot_hotspot(&display);
+	}
+
 	igt_describe("This test executes flips on both CRTCs "
 		     "while running cursor updates in parallel");
 	igt_subtest_group {

Signature · 1 line

2.40.0

Javier Martinez Canillas

Acked-by on v1 3/3

2023-07-25 14:26 UTC #9 lore raw

Re: [igt-dev] [PATCH 3/3] kms_cursor_legacy: modeset-atomic-cursor-hotspot

Albert Esteve <[email protected]> writes:

The patch looks good to me as well.

Acked-by Javier Martinez Canillas <[email protected]>

Some comments below though:

tests/kms_cursor_legacy.c

Quoted 16 lines

Add a test for modesetting an atomic cursor plane hotspot property. The test first checks if the plane is atomic and has the hotspot property. and if it does, it sets different random hot_x and hot_y values and checks that it is updated correctly after an atomic commit.
Signed-off-by Albert Esteve <[email protected]>
---
 tests/kms_cursor_legacy.c | 75 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 75 insertions(+)
tests/kms_cursor_legacy.c +0 -0
index 1ebac9d31..38258ed8d 100644

This file is called kms_cursor_legacy.c but it seems there are tests for both legacy KMS and atomic KMS? That confused me :)

tests/kms_cursor_legacy.c static void flip_vs_cursor_busy_crc(igt_display_t *display, bool atomic) · line 1611

Quoted 6 lines

tests/kms_cursor_legacy.c +2 -0

@@ -1607,6 +1607,70 @@ static void flip_vs_cursor_busy_crc(igt_display_t *display, bool atomic)
 	put_ahnd(ahnd);
 }
 
+static void modeset_atomic_cursot_hotspot(igt_display_t *display)
+{

I think you meant this to be "cursor_hotspot" instead ?

[...]

tests/kms_cursor_legacy.c static void flip_vs_cursor_busy_crc(igt_display_t *display, bool atomic) · line 1613

Quoted 2 lines

tests/kms_cursor_legacy.c +2 -0
+
+	width = height = 64;

maybe you can rename these to cursor_{width,height} ?

Also, there's https://docs.kernel.org/gpu/drm-uapi.html#c.DRM_CAP_CURSOR_WIDTH
and DRM_CAP_CURSOR_HEIGHT to query the hardware cursor size. Maybe you should use that instead of assume a 64x64 cursor size ?

Signature · 5 lines

Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat

Albert Esteve

author

2023-07-26 14:50 UTC #10 lore raw

Re: [igt-dev] [PATCH 3/3] kms_cursor_legacy: modeset-atomic-cursor-hotspot

Quoted 20 lines · Javier Martinez Canillas

Albert Esteve <[email protected]> writes:
The patch looks good to me as well.
Acked-by Javier Martinez Canillas <[email protected]>
Some comments below though:
Quoted 12 lines
Add a test for modesetting an atomic cursor plane hotspot property. The test first checks if the plane is atomic and has the hotspot property. and if it does, it sets different random hot_x and hot_y values and checks that it is updated correctly after an atomic commit.
Signed-off-by Albert Esteve <[email protected]>
---
 tests/kms_cursor_legacy.c | 75 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 75 insertions(+)

Quoted 8 lines

tests/kms_cursor_legacy.c
Quoted 4 lines
tests/kms_cursor_legacy.c +0 -0
index 1ebac9d31..38258ed8d 100644
This file is called kms_cursor_legacy.c but it seems there are tests for both legacy KMS and atomic KMS? That confused me :)

+1 :)

Quoted 12 lines

tests/kms_cursor_legacy.c static void flip_vs_cursor_busy_crc(igt_display_t
Quoted 2 lines
tests/kms_cursor_legacy.c +0 -0
@@ -1607,6 +1607,70 @@ static void flip_vs_cursor_busy_crc(igt_display_t
*display, bool atomic)
tests/kms_cursor_legacy.c static void flip_vs_cursor_busy_crc(igt_display_t *display, bool atomic) · line 1611
Quoted 5 lines
tests/kms_cursor_legacy.c +2 -0
      put_ahnd(ahnd);
 }
 
+static void modeset_atomic_cursot_hotspot(igt_display_t *display)
+{
I think you meant this to be "cursor_hotspot" instead ?

Oh, the typo, yes. Nice catch!

Quoted 8 lines

[...]
tests/kms_cursor_legacy.c
Quoted 2 lines
tests/kms_cursor_legacy.c +2 -0
+
+     width = height = 64;
maybe you can rename these to cursor_{width,height} ?

Ok.

Quoted 6 lines

Also, there's
https://docs.kernel.org/gpu/drm-uapi.html#c.DRM_CAP_CURSOR_WIDTH
and DRM_CAP_CURSOR_HEIGHT to query the hardware cursor size. Maybe you should
use that instead of assume a 64x64 cursor size ?

In many other tests in the same file the size of the cursor is hardcoded to 64, same as here.
So I kept it consistent.
Could be a nice refactor, but I guess it is outside the scope of this patch.

Quoted 9 lines

--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat

Javier Martinez Canillas

2023-07-26 14:53 UTC #11 lore raw

Re: [igt-dev] [PATCH 3/3] kms_cursor_legacy: modeset-atomic-cursor-hotspot

Quoted 3 lines · Albert Esteve

On Tue, Jul 25, 2023 at 4:26 PM Javier Martinez Canillas <[email protected]> wrote:

[...]

Quoted 7 lines

Quoted 6 lines
Also, there's
https://docs.kernel.org/gpu/drm-uapi.html#c.DRM_CAP_CURSOR_WIDTH
and DRM_CAP_CURSOR_HEIGHT to query the hardware cursor size. Maybe you should
use that instead of assume a 64x64 cursor size ?

Quoted 5 lines

In many other tests in the same file the size of the cursor is hardcoded to 64, same as here.
So I kept it consistent.
Could be a nice refactor, but I guess it is outside the scope of this patch.

Ah, didn't look at the rest of the file but yes, agreed that is better to keep it consistent and in any case the whole file could be cleaned up in a separate patch.

Signature · 5 lines

Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat

Patchwork

2023-07-24 12:22 UTC #12 lore raw

[igt-dev] ✓ Fi.CI.BAT: success for Add atomic DRM cursor hotspot test

In reply to Albert Esteve

== Series Details ==

Series: Add atomic DRM cursor hotspot test
URL : https://patchwork.freedesktop.org/series/121225/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_13413 -> IGTPW_9450
====================================================

Summary
-------

**SUCCESS**

No regressions found.

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

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

No changes in participating hosts

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

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

### IGT changes ###

#### Issues hit ####

* igt@i915_pm_rpm@module-reload:
- fi-kbl-7567u: [PASS][1] -> [FAIL][2] ([i915#7940])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/fi-kbl-7567u/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/fi-kbl-7567u/igt@[email protected]

* igt@i915_selftest@live@requests:
- bat-mtlp-6: [PASS][3] -> [DMESG-FAIL][4] ([i915#8497])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/bat-mtlp-6/igt@i915_selftest@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/bat-mtlp-6/igt@i915_selftest@[email protected]

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

* igt@kms_psr@primary_page_flip:
- bat-rplp-1: NOTRUN -> [SKIP][7] ([i915#1072]) +3 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/bat-rplp-1/igt@kms_psr@primary_page_flip.html

* igt@kms_setmode@basic-clone-single-crtc:
- bat-rplp-1: NOTRUN -> [ABORT][8] ([i915#8260] / [i915#8668])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/bat-rplp-1/igt@[email protected]

#### Possible fixes ####

* igt@gem_close_race@basic-threads:
- fi-kbl-soraka: [INCOMPLETE][9] -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/fi-kbl-soraka/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/fi-kbl-soraka/igt@[email protected]

* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-tgl-1115g4: [FAIL][11] ([i915#7940]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/fi-tgl-1115g4/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/fi-tgl-1115g4/igt@[email protected]
- bat-adlp-9: [FAIL][13] ([i915#7940]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/bat-adlp-9/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/bat-adlp-9/igt@[email protected]

* igt@i915_pm_rpm@basic-rte:
- fi-skl-guc: [FAIL][15] ([i915#7940]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/fi-skl-guc/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/fi-skl-guc/igt@[email protected]

* igt@i915_selftest@live@requests:
- bat-mtlp-8: [DMESG-FAIL][17] ([i915#8497]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/bat-mtlp-8/igt@i915_selftest@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/bat-mtlp-8/igt@i915_selftest@[email protected]

* igt@i915_selftest@live@slpc:
- bat-mtlp-8: [DMESG-WARN][19] ([i915#6367]) -> [PASS][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/bat-mtlp-8/igt@i915_selftest@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/bat-mtlp-8/igt@i915_selftest@[email protected]

* igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-edp-1:
- bat-rplp-1: [ABORT][21] ([i915#8442] / [i915#8668]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/bat-rplp-1/igt@kms_pipe_crc_basic@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/bat-rplp-1/igt@kms_pipe_crc_basic@[email protected]

#### Warnings ####

* igt@i915_module_load@load:
- bat-adlp-11: [DMESG-WARN][23] ([i915#4423] / [i915#8189]) -> [ABORT][24] ([i915#4423])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/bat-adlp-11/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/bat-adlp-11/igt@[email protected]

* igt@i915_pm_rpm@basic-rte:
- fi-kbl-guc: [FAIL][25] ([i915#8843]) -> [FAIL][26] ([i915#7940])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/fi-kbl-guc/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/fi-kbl-guc/igt@[email protected]

* igt@i915_selftest@live@gt_pm:
- fi-kbl-soraka: [DMESG-FAIL][27] ([i915#1886] / [i915#7913] / [i915#8189]) -> [DMESG-FAIL][28] ([i915#1886] / [i915#7913])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html

* igt@i915_suspend@basic-s2idle-without-i915:
- bat-atsm-1: [DMESG-WARN][29] ([i915#8189] / [i915#8841]) -> [DMESG-WARN][30] ([i915#8841])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/bat-atsm-1/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/bat-atsm-1/igt@[email protected]
- fi-hsw-4770: [DMESG-WARN][31] ([i915#8189] / [i915#8841]) -> [DMESG-WARN][32] ([i915#8841])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/fi-hsw-4770/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/fi-hsw-4770/igt@[email protected]

* igt@i915_suspend@basic-s3-without-i915:
- fi-tgl-1115g4: [INCOMPLETE][33] ([i915#7443] / [i915#8102] / [i915#8189]) -> [INCOMPLETE][34] ([i915#7443] / [i915#8102])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/fi-tgl-1115g4/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/fi-tgl-1115g4/igt@[email protected]
- fi-hsw-4770: [ABORT][35] ([i915#8189] / [i915#8841] / [i915#8844]) -> [ABORT][36] ([i915#8841] / [i915#8844])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/fi-hsw-4770/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/fi-hsw-4770/igt@[email protected]

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

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

* CI: CI-20190529 -> None
* IGT: IGT_7400 -> IGTPW_9450

CI-20190529: 20190529
CI_DRM_13413: 481eff06a3b94ba5295ed83255fb5a4492ed0809 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_9450: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/index.html
IGT_7400: 86fa0e885f8d020eeb046f27fae5729d5962ebd7 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git

Testlist changes
----------------

+igt@kms_cursor_legacy@modeset-atomic-cursor-hotspot

== Logs ==

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

Patchwork

2023-07-24 17:02 UTC #13 lore raw

[igt-dev] ✗ Fi.CI.IGT: failure for Add atomic DRM cursor hotspot test

In reply to Albert Esteve

== Series Details ==

Series: Add atomic DRM cursor hotspot test
URL : https://patchwork.freedesktop.org/series/121225/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_13413_full -> IGTPW_9450_full
====================================================

Summary
-------

**FAILURE**

Serious unknown changes coming with IGTPW_9450_full absolutely need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in IGTPW_9450_full, 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/IGTPW_9450/index.html

Participating hosts (10 -> 10)
------------------------------

Additional (1): shard-rkl0
Missing (1): pig-kbl-iris

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

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

### IGT changes ###

#### Possible regressions ####

* igt@kms_cursor_crc@cursor-random-128x42@pipe-d-edp-1:
- shard-mtlp: [PASS][1] -> [FAIL][2] +3 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-6/igt@kms_cursor_crc@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-7/igt@kms_cursor_crc@[email protected]

* {igt@kms_cursor_legacy@modeset-atomic-cursor-hotspot} (NEW):
- shard-dg2: NOTRUN -> [SKIP][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-12/igt@[email protected]
- shard-rkl: NOTRUN -> [SKIP][4]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-4/igt@[email protected]
- {shard-dg1}: NOTRUN -> [SKIP][5]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg1-13/igt@[email protected]
- shard-tglu: NOTRUN -> [SKIP][6]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-tglu-10/igt@[email protected]
- shard-mtlp: NOTRUN -> [SKIP][7]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-2/igt@[email protected]

#### Warnings ####

* igt@kms_big_fb@linear-64bpp-rotate-270:
- shard-snb: [SKIP][8] ([fdo#109271]) -> [ABORT][9]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-snb5/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-snb7/igt@[email protected]

New tests
---------

New tests have been introduced between CI_DRM_13413_full and IGTPW_9450_full:

### New IGT tests (1) ###

* igt@kms_cursor_legacy@modeset-atomic-cursor-hotspot:
- Statuses : 8 skip(s)
- Exec time: [0.0] s

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

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

### IGT changes ###

#### Issues hit ####

* igt@api_intel_bb@blit-reloc-purge-cache:
- shard-dg2: NOTRUN -> [SKIP][10] ([i915#8411])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-1/igt@[email protected]

* igt@drm_fdinfo@busy-hang@rcs0:
- shard-mtlp: NOTRUN -> [SKIP][11] ([i915#8414]) +11 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-8/igt@drm_fdinfo@[email protected]

* igt@drm_fdinfo@busy-idle@bcs0:
- shard-dg2: NOTRUN -> [SKIP][12] ([i915#8414]) +20 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-12/igt@drm_fdinfo@[email protected]

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

* igt@gem_basic@multigpu-create-close:
- shard-dg2: NOTRUN -> [SKIP][15] ([i915#7697])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-11/igt@[email protected]

* igt@gem_ctx_persistence@engines-hang@vcs0:
- shard-mtlp: [PASS][16] -> [FAIL][17] ([i915#2410])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-5/igt@gem_ctx_persistence@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-7/igt@gem_ctx_persistence@[email protected]

* igt@gem_ctx_persistence@file:
- shard-snb: NOTRUN -> [SKIP][18] ([fdo#109271] / [i915#1099]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-snb1/igt@[email protected]

* igt@gem_eio@hibernate:
- shard-dg2: NOTRUN -> [ABORT][19] ([i915#7975] / [i915#8213])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-5/igt@[email protected]

* igt@gem_eio@in-flight-contexts-1us:
- shard-mtlp: [PASS][20] -> [ABORT][21] ([i915#8503])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-5/igt@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-3/igt@[email protected]

* igt@gem_exec_balancer@bonded-semaphore:
- shard-dg2: NOTRUN -> [SKIP][22] ([i915#4812]) +1 similar issue
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-2/igt@[email protected]

* igt@gem_exec_balancer@full-pulse:
- shard-dg2: [PASS][23] -> [FAIL][24] ([i915#6032])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg2-1/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-8/igt@[email protected]

* igt@gem_exec_fair@basic-none@bcs0:
- shard-rkl: [PASS][25] -> [FAIL][26] ([i915#2842]) +3 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-rkl-4/igt@gem_exec_fair@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-4/igt@gem_exec_fair@[email protected]

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

* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [PASS][28] -> [FAIL][29] ([i915#2842]) +2 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-glk6/igt@gem_exec_fair@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-glk8/igt@gem_exec_fair@[email protected]

* igt@gem_exec_flush@basic-wb-ro-default:
- shard-dg2: NOTRUN -> [SKIP][30] ([i915#3539] / [i915#4852])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@[email protected]

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

* igt@gem_exec_params@secure-non-master:
- shard-mtlp: NOTRUN -> [SKIP][32] ([fdo#112283])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-4/igt@[email protected]

* igt@gem_exec_reloc@basic-cpu-read-noreloc:
- shard-mtlp: NOTRUN -> [SKIP][33] ([i915#3281]) +2 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-1/igt@[email protected]

* igt@gem_exec_reloc@basic-wc-read:
- shard-dg2: NOTRUN -> [SKIP][34] ([i915#3281]) +4 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@[email protected]
- shard-rkl: NOTRUN -> [SKIP][35] ([i915#3281])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-2/igt@[email protected]

* igt@gem_exec_schedule@preemptive-hang@vcs0:
- shard-mtlp: [PASS][36] -> [FAIL][37] ([i915#7327])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-4/igt@gem_exec_schedule@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-8/igt@gem_exec_schedule@[email protected]

* igt@gem_fence_thrash@bo-write-verify-y:
- shard-dg2: NOTRUN -> [SKIP][38] ([i915#4860]) +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-1/igt@[email protected]

* igt@gem_lmem_swapping@parallel-random-engines:
- shard-glk: NOTRUN -> [SKIP][39] ([fdo#109271] / [i915#4613])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-glk8/igt@[email protected]
- shard-mtlp: NOTRUN -> [SKIP][40] ([i915#4613])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-3/igt@[email protected]

* igt@gem_mmap_gtt@cpuset-big-copy:
- shard-dg2: NOTRUN -> [SKIP][41] ([i915#4077]) +6 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-10/igt@[email protected]

* igt@gem_mmap_gtt@fault-concurrent:
- shard-mtlp: NOTRUN -> [SKIP][42] ([i915#4077]) +1 similar issue
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-7/igt@[email protected]

* igt@gem_mmap_wc@write:
- shard-mtlp: NOTRUN -> [SKIP][43] ([i915#4083])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-6/igt@[email protected]

* igt@gem_mmap_wc@write-prefaulted:
- shard-dg2: NOTRUN -> [SKIP][44] ([i915#4083]) +4 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-10/igt@[email protected]

* igt@gem_partial_pwrite_pread@write-uncached:
- shard-mtlp: NOTRUN -> [SKIP][45] ([i915#3282])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-1/igt@[email protected]

* igt@gem_pwrite@basic-exhaustion:
- shard-dg2: NOTRUN -> [SKIP][46] ([i915#3282]) +1 similar issue
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-1/igt@[email protected]

* igt@gem_pxp@protected-raw-src-copy-not-readible:
- shard-dg2: NOTRUN -> [SKIP][47] ([i915#4270]) +1 similar issue
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@[email protected]
- shard-mtlp: NOTRUN -> [SKIP][48] ([i915#4270])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-1/igt@[email protected]

* igt@gem_set_tiling_vs_blt@untiled-to-tiled:
- shard-dg2: NOTRUN -> [SKIP][49] ([i915#4079])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@[email protected]

* igt@gem_userptr_blits@coherency-sync:
- shard-dg2: NOTRUN -> [SKIP][50] ([i915#3297]) +3 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-3/igt@[email protected]

* igt@gem_userptr_blits@vma-merge:
- shard-snb: NOTRUN -> [FAIL][51] ([i915#2724])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-snb1/igt@[email protected]

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

* igt@gen9_exec_parse@allowed-all:
- shard-dg2: NOTRUN -> [SKIP][53] ([i915#2856]) +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-8/igt@[email protected]

* igt@gen9_exec_parse@basic-rejected-ctx-param:
- shard-snb: NOTRUN -> [SKIP][54] ([fdo#109271]) +189 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-snb1/igt@[email protected]

* igt@gen9_exec_parse@batch-zero-length:
- shard-rkl: NOTRUN -> [SKIP][55] ([i915#2527])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-7/igt@[email protected]

* igt@i915_hangman@detector@vcs0:
- shard-mtlp: [PASS][56] -> [FAIL][57] ([i915#8456]) +2 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-4/igt@i915_hangman@[email protected]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-5/igt@i915_hangman@[email protected]

* igt@i915_hangman@gt-engine-error@vcs0:
- shard-mtlp: [PASS][58] -> [FAIL][59] ([i915#7069])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-1/igt@i915_hangman@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-3/igt@i915_hangman@[email protected]

* igt@i915_module_load@reload-with-fault-injection:
- shard-dg2: NOTRUN -> [DMESG-WARN][60] ([i915#7061])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-3/igt@[email protected]

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

* igt@i915_pipe_stress@stress-xrgb8888-ytiled:
- shard-dg2: NOTRUN -> [SKIP][63] ([i915#7091])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-12/igt@[email protected]
- shard-mtlp: NOTRUN -> [SKIP][64] ([i915#8436])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-2/igt@[email protected]

* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-hdmi-a:
- shard-dg2: NOTRUN -> [SKIP][65] ([i915#1937])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@i915_pm_lpsp@[email protected]

* igt@i915_pm_rpm@dpms-lpsp:
- shard-rkl: [PASS][66] -> [SKIP][67] ([i915#1397]) +3 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-rkl-7/igt@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-4/igt@[email protected]

* igt@i915_pm_rpm@modeset-lpsp-stress:
- shard-dg2: [PASS][68] -> [SKIP][69] ([i915#1397])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg2-12/igt@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-3/igt@[email protected]

* igt@i915_pm_rps@min-max-config-idle:
- shard-dg2: NOTRUN -> [SKIP][70] ([i915#6621])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-1/igt@[email protected]

* igt@i915_suspend@basic-s3-without-i915:
- shard-rkl: [PASS][71] -> [FAIL][72] ([fdo#103375]) +2 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-rkl-6/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-4/igt@[email protected]

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

* igt@kms_async_flips@alternate-sync-async-flip@pipe-c-hdmi-a-2:
- shard-glk: [PASS][75] -> [FAIL][76] ([i915#2521])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-glk2/igt@kms_async_flips@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-glk4/igt@kms_async_flips@[email protected]

* igt@kms_async_flips@crc@pipe-a-hdmi-a-3:
- shard-dg2: NOTRUN -> [FAIL][77] ([i915#8247]) +3 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-3/igt@kms_async_flips@[email protected]

* igt@kms_atomic_transition@plane-all-modeset-transition:
- shard-mtlp: NOTRUN -> [SKIP][78] ([i915#1769])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-5/igt@[email protected]

* igt@kms_big_fb@4-tiled-16bpp-rotate-90:
- shard-mtlp: NOTRUN -> [SKIP][79] ([fdo#111614])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-2/igt@[email protected]

* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-mtlp: [PASS][80] -> [FAIL][81] ([i915#5138])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-2/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-3/igt@[email protected]

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

* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-mtlp: NOTRUN -> [SKIP][83] ([fdo#111615])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-3/igt@[email protected]

* igt@kms_big_fb@yf-tiled-64bpp-rotate-180:
- shard-dg2: NOTRUN -> [SKIP][84] ([i915#4538] / [i915#5190]) +1 similar issue
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-1/igt@[email protected]
- shard-rkl: NOTRUN -> [SKIP][85] ([fdo#110723])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-7/igt@[email protected]

* igt@kms_big_fb@yf-tiled-addfb:
- shard-mtlp: NOTRUN -> [SKIP][86] ([i915#6187])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-5/igt@[email protected]

* igt@kms_big_fb@yf-tiled-addfb-size-overflow:
- shard-dg2: NOTRUN -> [SKIP][87] ([i915#5190]) +4 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@[email protected]

* igt@kms_ccs@pipe-a-bad-pixel-format-4_tiled_mtl_mc_ccs:
- shard-dg2: NOTRUN -> [SKIP][88] ([i915#5354]) +24 similar issues
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-6/igt@kms_ccs@pipe-a-bad-pixel-format-4_tiled_mtl_mc_ccs.html

* igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs:
- shard-glk: NOTRUN -> [SKIP][89] ([fdo#109271]) +25 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-glk5/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs.html

* igt@kms_ccs@pipe-a-missing-ccs-buffer-4_tiled_mtl_rc_ccs:
- shard-tglu: NOTRUN -> [SKIP][90] ([i915#5354] / [i915#6095])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-tglu-8/igt@kms_ccs@pipe-a-missing-ccs-buffer-4_tiled_mtl_rc_ccs.html

* igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][91] ([fdo#109271] / [i915#3886])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-glk3/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-dg2: NOTRUN -> [SKIP][92] ([i915#3689] / [i915#3886] / [i915#5354]) +5 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-10/igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html
- shard-rkl: NOTRUN -> [SKIP][93] ([i915#5354]) +1 similar issue
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-7/igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-d-crc-primary-rotation-180-4_tiled_dg2_mc_ccs:
- shard-mtlp: NOTRUN -> [SKIP][94] ([i915#6095]) +7 similar issues
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-1/igt@kms_ccs@pipe-d-crc-primary-rotation-180-4_tiled_dg2_mc_ccs.html

* igt@kms_ccs@pipe-d-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
- shard-dg2: NOTRUN -> [SKIP][95] ([i915#3689] / [i915#5354]) +13 similar issues
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-2/igt@kms_ccs@pipe-d-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html

* igt@kms_cdclk@mode-transition@pipe-d-hdmi-a-3:
- shard-dg2: NOTRUN -> [SKIP][96] ([i915#4087] / [i915#7213]) +3 similar issues
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-8/igt@kms_cdclk@[email protected]

* igt@kms_cdclk@plane-scaling@pipe-c-hdmi-a-3:
- shard-dg2: NOTRUN -> [SKIP][97] ([i915#4087]) +3 similar issues
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-5/igt@kms_cdclk@[email protected]

* igt@kms_chamelium_edid@vga-edid-read:
- shard-mtlp: NOTRUN -> [SKIP][98] ([i915#7828]) +1 similar issue
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-5/igt@[email protected]

* igt@kms_chamelium_frames@hdmi-crc-multiple:
- shard-dg2: NOTRUN -> [SKIP][99] ([i915#7828]) +5 similar issues
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@[email protected]

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

* igt@kms_content_protection@mei_interface:
- shard-dg2: NOTRUN -> [SKIP][101] ([i915#7118] / [i915#7162])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-12/igt@kms_content_protection@mei_interface.html

* igt@kms_content_protection@srm@pipe-a-dp-4:
- shard-dg2: NOTRUN -> [TIMEOUT][102] ([i915#7173])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-11/igt@kms_content_protection@[email protected]

* igt@kms_cursor_crc@cursor-offscreen-512x170:
- shard-dg2: NOTRUN -> [SKIP][103] ([i915#3359]) +1 similar issue
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-8/igt@[email protected]

* igt@kms_cursor_crc@cursor-sliding-32x32:
- shard-mtlp: NOTRUN -> [SKIP][104] ([i915#8814])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-1/igt@[email protected]
- shard-dg2: NOTRUN -> [SKIP][105] ([i915#3555])
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-12/igt@[email protected]

* igt@kms_cursor_legacy@cursorb-vs-flipa-toggle:
- shard-dg2: NOTRUN -> [SKIP][106] ([fdo#109274] / [i915#5354]) +3 similar issues
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-11/igt@[email protected]

* igt@kms_cursor_legacy@cursorb-vs-flipb-toggle:
- shard-snb: NOTRUN -> [SKIP][107] ([fdo#109271] / [fdo#111767])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-snb6/igt@[email protected]

* igt@kms_cursor_legacy@flip-vs-cursor-legacy:
- shard-tglu: [PASS][108] -> [FAIL][109] ([i915#2346])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-tglu-6/igt@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-tglu-10/igt@[email protected]

* {igt@kms_cursor_legacy@modeset-atomic-cursor-hotspot} (NEW):
- shard-apl: NOTRUN -> [SKIP][110] ([fdo#109271])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-apl3/igt@[email protected]

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

* igt@kms_draw_crc@draw-method-mmap-gtt:
- shard-mtlp: NOTRUN -> [SKIP][112] ([i915#8812])
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-4/igt@[email protected]
- shard-dg2: NOTRUN -> [SKIP][113] ([i915#8812])
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-5/igt@[email protected]

* igt@kms_dsc@dsc-with-bpc-formats:
- shard-dg2: NOTRUN -> [SKIP][114] ([i915#3555] / [i915#3840])
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-6/igt@[email protected]

* igt@kms_flip@2x-blocking-wf_vblank:
- shard-mtlp: NOTRUN -> [SKIP][115] ([i915#3637])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-6/igt@kms_flip@2x-blocking-wf_vblank.html

* igt@kms_flip@2x-flip-vs-suspend-interruptible:
- shard-tglu: NOTRUN -> [SKIP][116] ([fdo#109274] / [i915#3637])
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-tglu-10/igt@[email protected]

* igt@kms_flip@2x-nonexisting-fb:
- shard-rkl: NOTRUN -> [SKIP][117] ([fdo#111825])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-2/igt@[email protected]

* igt@kms_flip@2x-plain-flip-ts-check-interruptible:
- shard-dg2: NOTRUN -> [SKIP][118] ([fdo#109274]) +2 similar issues
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@[email protected]

* igt@kms_flip@dpms-vs-vblank-race-interruptible@a-edp1:
- shard-mtlp: [PASS][119] -> [DMESG-WARN][120] ([i915#1982])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-1/igt@kms_flip@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-3/igt@kms_flip@[email protected]

* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-valid-mode:
- shard-dg2: NOTRUN -> [SKIP][121] ([i915#2672])
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-5/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-valid-mode.html

* igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-32bpp-xtile-downscaling@pipe-a-default-mode:
- shard-mtlp: NOTRUN -> [SKIP][122] ([i915#8810])
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-5/igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-32bpp-xtile-downscaling@pipe-a-default-mode.html

* igt@kms_force_connector_basic@prune-stale-modes:
- shard-dg2: NOTRUN -> [SKIP][123] ([i915#5274])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-3/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-gtt:
- shard-dg2: NOTRUN -> [SKIP][124] ([i915#8708]) +10 similar issues
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-10/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-gtt.html

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

* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-pwrite:
- shard-rkl: NOTRUN -> [SKIP][126] ([i915#3023])
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-pwrite.html

* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-gtt:
- shard-rkl: NOTRUN -> [SKIP][127] ([fdo#111825] / [i915#1825])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-1/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-gtt.html

* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-onoff:
- shard-mtlp: NOTRUN -> [SKIP][128] ([i915#1825]) +6 similar issues
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-1/igt@[email protected]

* igt@kms_frontbuffer_tracking@psr-1p-pri-indfb-multidraw:
- shard-dg2: NOTRUN -> [SKIP][129] ([i915#3458]) +12 similar issues
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-12/igt@[email protected]

* igt@kms_hdmi_inject@inject-audio:
- shard-tglu: [PASS][130] -> [SKIP][131] ([i915#433])
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-tglu-5/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-tglu-5/igt@[email protected]

* igt@kms_hdr@bpc-switch-dpms:
- shard-rkl: NOTRUN -> [SKIP][132] ([i915#3555] / [i915#8228]) +1 similar issue
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-7/igt@[email protected]

* igt@kms_plane_scaling@intel-max-src-size@pipe-a-hdmi-a-1:
- shard-rkl: NOTRUN -> [FAIL][133] ([i915#8292])
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-7/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][134] ([i915#5176]) +3 similar issues
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@kms_plane_scaling@[email protected]

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

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

* igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-25@pipe-d-edp-1:
- shard-mtlp: NOTRUN -> [SKIP][137] ([i915#5235]) +7 similar issues
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-3/igt@kms_plane_scaling@[email protected]

* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-big-fb:
- shard-dg2: NOTRUN -> [SKIP][138] ([i915#658])
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-3/igt@[email protected]

* igt@kms_psr@psr2_primary_blt:
- shard-mtlp: [PASS][139] -> [DMESG-WARN][140] ([i915#2017])
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-4/igt@kms_psr@psr2_primary_blt.html
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-8/igt@kms_psr@psr2_primary_blt.html

* igt@kms_psr@psr2_sprite_plane_move:
- shard-dg2: NOTRUN -> [SKIP][141] ([i915#1072]) +4 similar issues
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-1/igt@kms_psr@psr2_sprite_plane_move.html

* igt@kms_rotation_crc@sprite-rotation-270:
- shard-dg2: NOTRUN -> [SKIP][142] ([i915#4235]) +1 similar issue
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-2/igt@[email protected]

* igt@kms_vblank@pipe-c-ts-continuation-dpms-rpm:
- shard-rkl: NOTRUN -> [SKIP][143] ([i915#4070] / [i915#6768])
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-7/igt@[email protected]

* igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
- shard-dg2: [PASS][144] -> [FAIL][145] ([fdo#103375])
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg2-2/igt@[email protected]
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-5/igt@[email protected]

* igt@kms_vrr@flip-dpms:
- shard-mtlp: NOTRUN -> [SKIP][146] ([i915#8808])
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-6/igt@[email protected]

* igt@perf@unprivileged-single-ctx-counters:
- shard-mtlp: NOTRUN -> [SKIP][147] ([fdo#109289]) +1 similar issue
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-7/igt@[email protected]

* igt@perf_pmu@busy-idle@bcs0:
- shard-mtlp: [PASS][148] -> [FAIL][149] ([i915#4349]) +3 similar issues
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-4/igt@perf_pmu@[email protected]
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-6/igt@perf_pmu@[email protected]

* igt@perf_pmu@busy-idle@vcs0:
- shard-dg2: [PASS][150] -> [FAIL][151] ([i915#4349]) +7 similar issues
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg2-1/igt@perf_pmu@[email protected]
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-10/igt@perf_pmu@[email protected]

* igt@perf_pmu@rc6-all-gts:
- shard-mtlp: NOTRUN -> [FAIL][152] ([i915#8553])
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-2/igt@[email protected]

* igt@perf_pmu@rc6-suspend:
- shard-snb: NOTRUN -> [DMESG-WARN][153] ([i915#8841]) +3 similar issues
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-snb7/igt@[email protected]

* igt@prime_mmap@test_aperture_limit@test_aperture_limit-smem:
- shard-dg2: NOTRUN -> [CRASH][154] ([i915#7331])
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@prime_mmap@test_aperture_limit@test_aperture_limit-smem.html

* igt@prime_vgem@basic-gtt:
- shard-mtlp: NOTRUN -> [SKIP][155] ([i915#3708] / [i915#4077])
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-8/igt@[email protected]
- shard-dg2: NOTRUN -> [SKIP][156] ([i915#3708] / [i915#4077])
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-11/igt@[email protected]

* igt@prime_vgem@fence-flip-hang:
- shard-dg2: NOTRUN -> [SKIP][157] ([i915#3708])
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-1/igt@[email protected]

* igt@sysfs_heartbeat_interval@nopreempt@vcs0:
- shard-mtlp: NOTRUN -> [FAIL][158] ([i915#6015]) +5 similar issues
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-5/igt@sysfs_heartbeat_interval@[email protected]

* igt@v3d/v3d_job_submission@array-job-submission:
- shard-dg2: NOTRUN -> [SKIP][159] ([i915#2575]) +5 similar issues
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-1/igt@v3d/[email protected]

* igt@v3d/v3d_perfmon@get-values-invalid-perfmon:
- shard-mtlp: NOTRUN -> [SKIP][160] ([i915#2575]) +3 similar issues
[160]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-4/igt@v3d/[email protected]

* igt@vc4/vc4_tiling@get-bad-modifier:
- shard-dg2: NOTRUN -> [SKIP][161] ([i915#7711]) +4 similar issues
[161]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-1/igt@vc4/[email protected]

* igt@vc4/vc4_tiling@set-bad-handle:
- shard-mtlp: NOTRUN -> [SKIP][162] ([i915#7711])
[162]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-8/igt@vc4/[email protected]

#### Possible fixes ####

* igt@gem_barrier_race@remote-request@rcs0:
- shard-mtlp: [ABORT][163] ([i915#8234]) -> [PASS][164]
[163]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-7/igt@gem_barrier_race@[email protected]
[164]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-3/igt@gem_barrier_race@[email protected]

* igt@gem_ctx_exec@basic-nohangcheck:
- shard-rkl: [FAIL][165] ([i915#6268]) -> [PASS][166]
[165]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-rkl-4/igt@[email protected]
[166]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-2/igt@[email protected]

* igt@gem_ctx_persistence@legacy-engines-hang@bsd1:
- shard-mtlp: [FAIL][167] ([i915#2410]) -> [PASS][168]
[167]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-6/igt@gem_ctx_persistence@[email protected]
[168]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-8/igt@gem_ctx_persistence@[email protected]

* igt@gem_ctx_persistence@saturated-hostile@vecs0:
- shard-mtlp: [FAIL][169] ([i915#7816]) -> [PASS][170] +2 similar issues
[169]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-6/igt@gem_ctx_persistence@[email protected]
[170]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-2/igt@gem_ctx_persistence@[email protected]

* igt@gem_eio@kms:
- shard-dg2: [INCOMPLETE][171] ([i915#1982] / [i915#7892]) -> [PASS][172]
[171]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg2-10/igt@[email protected]
[172]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-7/igt@[email protected]
- {shard-dg1}: [FAIL][173] ([i915#5784]) -> [PASS][174]
[173]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg1-12/igt@[email protected]
[174]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg1-15/igt@[email protected]

* igt@gem_exec_capture@pi@vcs0:
- shard-mtlp: [FAIL][175] ([i915#4475]) -> [PASS][176]
[175]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-6/igt@gem_exec_capture@[email protected]
[176]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-7/igt@gem_exec_capture@[email protected]

* igt@gem_exec_endless@dispatch@rcs0:
- shard-rkl: [TIMEOUT][177] ([i915#3778]) -> [PASS][178]
[177]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-rkl-4/igt@gem_exec_endless@[email protected]
[178]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-4/igt@gem_exec_endless@[email protected]

* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglu: [FAIL][179] ([i915#2842]) -> [PASS][180]
[179]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-tglu-4/igt@gem_exec_fair@[email protected]
[180]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-tglu-7/igt@gem_exec_fair@[email protected]

* igt@gem_exec_whisper@basic-contexts-forked-all:
- shard-mtlp: [TIMEOUT][181] ([i915#8628]) -> [PASS][182]
[181]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-4/igt@[email protected]
[182]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-8/igt@[email protected]

* igt@gem_userptr_blits@nohangcheck:
- shard-mtlp: [FAIL][183] ([i915#7916]) -> [PASS][184]
[183]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-7/igt@[email protected]
[184]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-3/igt@[email protected]

* igt@gen9_exec_parse@allowed-all:
- shard-glk: [ABORT][185] ([i915#5566]) -> [PASS][186]
[185]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-glk5/igt@[email protected]
[186]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-glk6/igt@[email protected]

* igt@i915_hangman@engine-engine-hang@vcs0:
- shard-mtlp: [FAIL][187] ([i915#7069]) -> [PASS][188]
[187]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-1/igt@i915_hangman@[email protected]
[188]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-6/igt@i915_hangman@[email protected]

* igt@i915_pm_dc@dc9-dpms:
- shard-apl: [SKIP][189] ([fdo#109271]) -> [PASS][190]
[189]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-apl1/igt@[email protected]
[190]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-apl2/igt@[email protected]

* igt@i915_pm_rc6_residency@rc6-idle@rcs0:
- {shard-dg1}: [FAIL][191] ([i915#3591]) -> [PASS][192] +1 similar issue
[191]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg1-18/igt@i915_pm_rc6_residency@[email protected]
[192]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg1-12/igt@i915_pm_rc6_residency@[email protected]

* igt@i915_pm_rpm@dpms-non-lpsp:
- {shard-dg1}: [SKIP][193] ([i915#1397]) -> [PASS][194] +1 similar issue
[193]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg1-19/igt@[email protected]
[194]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg1-18/igt@[email protected]

* igt@i915_pm_rpm@gem-execbuf@smem0:
- {shard-dg1}: [FAIL][195] ([i915#7940]) -> [PASS][196] +1 similar issue
[195]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg1-17/igt@i915_pm_rpm@[email protected]
[196]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg1-19/igt@i915_pm_rpm@[email protected]

* igt@i915_pm_rpm@modeset-lpsp-stress-no-wait:
- shard-dg2: [SKIP][197] ([i915#1397]) -> [PASS][198] +1 similar issue
[197]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg2-8/igt@[email protected]
[198]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-10/igt@[email protected]
- shard-rkl: [SKIP][199] ([i915#1397]) -> [PASS][200]
[199]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-rkl-6/igt@[email protected]
[200]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-7/igt@[email protected]

* igt@i915_selftest@live@gt_mocs:
- shard-mtlp: [DMESG-FAIL][201] ([i915#7059]) -> [PASS][202]
[201]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-6/igt@i915_selftest@live@gt_mocs.html
[202]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-5/igt@i915_selftest@live@gt_mocs.html

* igt@i915_selftest@live@workarounds:
- shard-mtlp: [DMESG-FAIL][203] ([i915#6763]) -> [PASS][204]
[203]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-6/igt@i915_selftest@[email protected]
[204]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-5/igt@i915_selftest@[email protected]

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

* igt@kms_vblank@pipe-a-accuracy-idle:
- shard-glk: [FAIL][207] -> [PASS][208]
[207]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-glk6/igt@[email protected]
[208]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-glk4/igt@[email protected]

* igt@perf_pmu@all-busy-idle-check-all:
- shard-mtlp: [FAIL][209] ([i915#5234]) -> [PASS][210]
[209]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-3/igt@[email protected]
[210]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-4/igt@[email protected]

* {igt@perf_pmu@rc6@runtime-pm-long-gt1}:
- shard-mtlp: [SKIP][211] ([i915#8537]) -> [PASS][212] +2 similar issues
[211]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-2/igt@perf_pmu@[email protected]
[212]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-8/igt@perf_pmu@[email protected]

* igt@sysfs_timeslice_duration@timeout@vecs0:
- shard-mtlp: [TIMEOUT][213] ([i915#6950]) -> [PASS][214]
[213]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-7/igt@sysfs_timeslice_duration@[email protected]
[214]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-7/igt@sysfs_timeslice_duration@[email protected]

#### Warnings ####

* igt@gem_eio@in-flight-suspend:
- shard-snb: [DMESG-FAIL][215] ([fdo#103375]) -> [DMESG-WARN][216] ([i915#8841])
[215]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-snb7/igt@[email protected]
[216]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-snb4/igt@[email protected]

* igt@i915_pm_rc6_residency@rc6-idle@vecs0:
- shard-tglu: [WARN][217] ([i915#2681]) -> [FAIL][218] ([i915#2681] / [i915#3591])
[217]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-tglu-6/igt@i915_pm_rc6_residency@[email protected]
[218]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-tglu-10/igt@i915_pm_rc6_residency@[email protected]

* igt@kms_async_flips@crc@pipe-a-edp-1:
- shard-mtlp: [DMESG-FAIL][219] ([i915#8561]) -> [DMESG-FAIL][220] ([i915#1982] / [i915#8561])
[219]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-7/igt@kms_async_flips@[email protected]
[220]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-3/igt@kms_async_flips@[email protected]

* igt@kms_content_protection@content_type_change:
- shard-dg2: [SKIP][221] ([i915#7118] / [i915#7162]) -> [SKIP][222] ([i915#7118])
[221]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-dg2-12/igt@kms_content_protection@content_type_change.html
[222]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-dg2-8/igt@kms_content_protection@content_type_change.html

* igt@kms_cursor_crc@cursor-suspend@pipe-b-vga-1:
- shard-snb: [DMESG-WARN][223] ([i915#8841]) -> [INCOMPLETE][224] ([i915#7882])
[223]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-snb4/igt@kms_cursor_crc@[email protected]
[224]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-snb7/igt@kms_cursor_crc@[email protected]

* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-mtlp: [FAIL][225] ([i915#2346]) -> [DMESG-FAIL][226] ([i915#2017] / [i915#5954])
[225]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-mtlp-2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[226]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-mtlp-2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html

* igt@kms_force_connector_basic@force-load-detect:
- shard-rkl: [SKIP][227] ([fdo#109285] / [i915#4098]) -> [SKIP][228] ([fdo#109285])
[227]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-rkl-2/igt@[email protected]
[228]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-6/igt@[email protected]

* igt@kms_multipipe_modeset@basic-max-pipe-crc-check:
- shard-rkl: [SKIP][229] ([i915#4816]) -> [SKIP][230] ([i915#4070] / [i915#4816])
[229]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13413/shard-rkl-4/igt@[email protected]
[230]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9450/shard-rkl-2/igt@[email protected]

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

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

* CI: CI-20190529 -> None
* IGT: IGT_7400 -> IGTPW_9450
* Piglit: piglit_4509 -> None

== Logs ==

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

Kamil Konieczny

2023-07-25 15:51 UTC #14 lore raw

In reply to Albert Esteve

Hi Albert,

please subscribe to igt-dev mailinglist.

Quoted 11 lines · Albert Esteve

Add test to verify the kernel patch at [1].
The test modifies the hotspot x and y properties and checks that they get properly updated after every display commit.
The first git commit updating the drm header shall be removed, and update the header properly after the kernel patch has landed.
[1] - https://lists.freedesktop.org/archives/dri-devel/2023-July/414509.html

Add this to your 3rd patch with commit message (subject), as links tends to rot.

Regards,
Kamil

Quoted 15 lines

Albert Esteve (3):
drm header update: temp commit
igt_kms: add hotspot plane property
kms_cursor_legacy: modeset-atomic-cursor-hotspot
 include/drm-uapi/drm.h    | 54 +++++++++++++++++++++++++++-
 lib/igt_kms.c             |  9 +++++
 lib/igt_kms.h             |  4 ++-
 tests/kms_cursor_legacy.c | 75 +++++++++++++++++++++++++++++++++++++++
 4 files changed, 140 insertions(+), 2 deletions(-)
Signature · 1 line
2.40.0

Albert Esteve

author

2023-07-26 14:52 UTC #15 lore raw

Quoted 4 lines · Kamil Konieczny

Hi Albert,
please subscribe to igt-dev mailinglist.

Done :)

Quoted 12 lines · Albert Esteve

Quoted 10 lines
Add test to verify the kernel patch at [1].
The test modifies the hotspot x and y properties and checks that they get properly updated after every display commit.
The first git commit updating the drm header shall be removed, and update the header properly after the kernel patch has landed.

Quoted 6 lines

Quoted 1 line
[1] -
https://lists.freedesktop.org/archives/dri-devel/2023-July/414509.html
Add this to your 3rd patch with commit message (subject), as links tends to rot.

Sure! I'll prepare a next drop soon.

Quoted 21 lines

Regards,
Kamil
Quoted 15 lines
Albert Esteve (3):
drm header update: temp commit
igt_kms: add hotspot plane property
kms_cursor_legacy: modeset-atomic-cursor-hotspot
 include/drm-uapi/drm.h    | 54 +++++++++++++++++++++++++++-
 lib/igt_kms.c             |  9 +++++
 lib/igt_kms.h             |  4 ++-
 tests/kms_cursor_legacy.c | 75 +++++++++++++++++++++++++++++++++++++++
 4 files changed, 140 insertions(+), 2 deletions(-)
--
2.40.0