Skip to contentSkip to conversation

i915/i915_hwmon: General verification of hwmon attributes

PATCH In review Ashutosh Dixit 3 participants 9 messages Dec 14, 2022 – Dec 15, 2022

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

cover i915/i915_hwmon: General verification of hwmon attributes

Ensure we can read all hwmon attributes. For writable attributes, also ensure the read value approximately matches the written value, taking the clamping of writes into account.

v2: Added new patch "lib/igt_sysfs: Make it easier to extend verification
of clamped sysfs attr". No changes to previous patches.
v3: Identical to v2, failed to copy reviewers
v4: Drop the concept of a 'clamped' sysfs attribute, it is not
necessary. All we need is a writable attribute for which the read values will match the written values for a few points across the range of all possible values.

Ashutosh Dixit (3):
lib/igt_sysfs: Generic verification of writable sysfs attributes i915/i915_hwmon: General verification of hwmon attributes
HAX: Add i915_hwmon* to fast-feedback.testlist

 lib/igt_sysfs.c                       | 119 ++++++++++++++++++++++++++
 lib/igt_sysfs.h                       |  21 +++++
 tests/i915/i915_hwmon.c               |  88 +++++++++++++++++++
 tests/intel-ci/fast-feedback.testlist |   2 +
 tests/meson.build                     |   1 +
 5 files changed, 231 insertions(+)
 create mode 100644 tests/i915/i915_hwmon.c
Signature · 1 line
2.38.0
#1 lore raw

PATCH 1/3 lib/igt_sysfs: Generic verification of writable sysfs attributes

Attempt to verify writable sysfs attributes in a generic way, without going into the specifics of any attribute. The attribute is first written to and then read back and it is verified that the read value matches the written value to a tolerance. However, when we try to do this we run into the issue that a sysfs attribute might have a behavior where the read value is different from the written value for any reason. For example, attributes such as power, voltage, frequency and time typically have a linear region outside which they are clamped (the values saturate). Therefore for such attributes read values match the written value only in the linear region and when writing we don't know if we are writing to the linear or to the clamped region.

Therefore the verification implemented here takes the approach of sweeping across the range of possible values of the attribute (this is done using 'doubling' rather than linearly) and seeing where there are matches. There should be at least one match for the verification to have succeeded.

---
 lib/igt_sysfs.c | 119 ++++++++++++++++++++++++++++++++++++++++++++++++
 lib/igt_sysfs.h |  21 +++++++++
 2 files changed, 140 insertions(+)
lib/igt_sysfs.c +119 -0
index a913be4c8f2..c6cccf6fa1e 100644
@@ -784,3 +784,122 @@ void fbcon_blink_enable(bool enable)
 	write(fd, buffer, r + 1);
 	close(fd);
 }
+
+struct rw_attr_internal {
+	/* we need an uint64_t array of max 64 points */
+	uint64_t points[64];
+	int num_points;
+};
+
+static bool rw_attr_equal_within_epsilon(uint64_t x, uint64_t ref, double tol)
+{
+	return (x <= (1.0 + tol) * ref) && (x >= (1.0 - tol) * ref);
+}
+
+/* Sweep the range of values for an attribute to identify matching reads/writes */
+static int rw_attr_sweep(igt_sysfs_rw_attr_t *rw)
+{
+	struct rw_attr_internal *pts = rw->rsvd;
+	uint64_t get, set = rw->start;
+	bool ret;
+
+	igt_debug("'%s': sweeping range of values\n", rw->attr);
+	while (1) {
+		if (set >= UINT64_MAX / 2) {
+			igt_debug("'%s': done sweeping\n", rw->attr);
+			break;
+		}
+
+		ret = igt_sysfs_set_u64(rw->dir, rw->attr, set);
+		get = igt_sysfs_get_u64(rw->dir, rw->attr);
+		igt_debug("'%s': ret %d set %lu get %lu\n", rw->attr, ret, set, get);
+		if (ret && rw_attr_equal_within_epsilon(get, set, rw->tol)) {
+			pts->points[pts->num_points++] = set;
+			igt_debug("'%s': include %lu\n", rw->attr, set);
+		}
+
+		set *= 2;
+	}
+
+	return pts->num_points ? 0 : -ENOENT;
+}
+
+/* Re-verify that reads following writes are equal within a tolerance */
+static int rw_attr_reverify_points(igt_sysfs_rw_attr_t *rw)
+{
+	struct rw_attr_internal *pts = rw->rsvd;
+	uint64_t get, set;
+	int i;
+
+	igt_debug("'%s': reverifying\n", rw->attr);
+	for (i = pts->num_points - 1; i >= 0; i--) {
+		set = pts->points[i];
+		if (!igt_sysfs_set_u64(rw->dir, rw->attr, set)) {
+			igt_debug("'%s': set %lu failed\n", rw->attr, set);
+			return -EIO;
+		}
+		get = igt_sysfs_get_u64(rw->dir, rw->attr);
+		if (!rw_attr_equal_within_epsilon(get, set, rw->tol)) {
+			igt_debug("'%s': mismatch set %lu get %lu\n", rw->attr, set, get);
+			return -EIO;
+		}
+	}
+	igt_debug("'%s': done reverifying\n", rw->attr);
+
+	return 0;
+}
+
+/**
+ * igt_sysfs_rw_attr_verify:
+ * @rw: 'struct igt_sysfs_rw_attr' describing a rw sysfs attr
+ *
+ * This function attempts to verify writable sysfs attributes, that is the
+ * attribute is first written to and then read back and it is verified that
+ * the read value matches the written value to a tolerance. However, when
+ * we try to do this we run into the issue that a sysfs attribute might
+ * have a behavior where the read value is different from the written value
+ * for any reason. For example, attributes such as power, voltage,
+ * frequency and time typically have a linear region outside which they are
+ * clamped (the values saturate). Therefore for such attributes read values
+ * match the written value only in the linear region and when writing we
+ * don't know if we are writing to the linear or to the clamped region.
+ *
+ * Therefore the verification implemented here takes the approach of
+ * sweeping across the range of possible values of the attribute (this is
+ * done using 'doubling' rather than linearly) and seeing where there are
+ * matches. There should be at least one match (to a tolerance) for the
+ * verification to have succeeded.
+ */
+void igt_sysfs_rw_attr_verify(igt_sysfs_rw_attr_t *rw)
+{
+	uint64_t prev, get;
+	struct stat st;
+	int ret;
+
+	igt_assert(!fstatat(rw->dir, rw->attr, &st, 0));
+	igt_assert(st.st_mode & 0222); /* writable */
+	igt_assert(rw->start);	/* cannot be 0 */
+
+	prev = igt_sysfs_get_u64(rw->dir, rw->attr);
+	igt_debug("'%s': prev %lu\n", rw->attr, prev);
+
+	rw->rsvd = calloc(1, sizeof(struct rw_attr_internal));
+	igt_assert(rw->rsvd);
+
+	ret = rw_attr_sweep(rw);
+	if (ret)
+		goto restore;
+
+	ret = rw_attr_reverify_points(rw);
+
+	/*
+	 * Restore previous value: we don't assert before this point so
+	 * that we can restore the attr before asserting
+	 */
+restore:
+	free(rw->rsvd);
+	igt_assert_eq(1, igt_sysfs_set_u64(rw->dir, rw->attr, prev));
+	get = igt_sysfs_get_u64(rw->dir, rw->attr);
+	igt_assert_eq(get, prev);
+	igt_assert(!ret);
+}
lib/igt_sysfs.h +21 -0
index 1c9791a1bdc..418c800e8c5 100644
@@ -125,4 +125,25 @@ void bind_fbcon(bool enable);
 void kick_snd_hda_intel(void);
 void fbcon_blink_enable(bool enable);
 
+/**
+ * igt_sysfs_rw_attr:
+ * @dir: file descriptor for parent directory
+ * @attr: name of sysfs attribute
+ * @start: start value for searching for matching reads/writes
+ * @tol: tolerance to use to compare written and read values
+ * @rsvd: reserved field used internally
+ *
+ * Structure used to describe the rw sysfs attribute to
+ * igt_sysfs_rw_attr_verify
+ */
+typedef struct igt_sysfs_rw_attr {
+	int dir;
+	char *attr;
+	uint64_t start;
+	double tol;
+	void *rsvd;
+} igt_sysfs_rw_attr_t;
+
+void igt_sysfs_rw_attr_verify(igt_sysfs_rw_attr_t *rw);
+
 #endif /* __IGT_SYSFS_H__ */
Signature · 1 line
2.38.0
#2 lore raw

Re: [igt-dev] [PATCH i-g-t 1/3] lib/igt_sysfs: Generic verification of writable sysfs attributes

Hi Ashutosh

Quoted 42 lines · Ashutosh Dixit

Attempt to verify writable sysfs attributes in a generic way, without going into the specifics of any attribute. The attribute is first written to and then read back and it is verified that the read value matches the written value to a tolerance. However, when we try to do this we run into the issue that a sysfs attribute might have a behavior where the read value is different from the written value for any reason. For example, attributes such as power, voltage, frequency and time typically have a linear region outside which they are clamped (the values saturate). Therefore for such attributes read values match the written value only in the linear region and when writing we don't know if we are writing to the linear or to the clamped region.

Therefore the verification implemented here takes the approach of sweeping across the range of possible values of the attribute (this is done using 'doubling' rather than linearly) and seeing where there are matches. There should be at least one match for the verification to have succeeded.

---
  lib/igt_sysfs.c | 119 ++++++++++++++++++++++++++++++++++++++++++++++++
  lib/igt_sysfs.h |  21 +++++++++
  2 files changed, 140 insertions(+)
lib/igt_sysfs.c +11 -0
index a913be4c8f2..c6cccf6fa1e 100644
@@ -784,3 +784,122 @@ void fbcon_blink_enable(bool enable)
  	write(fd, buffer, r + 1);
  	close(fd);
  }
+
+struct rw_attr_internal {
+	/* we need an uint64_t array of max 64 points */
+	uint64_t points[64];
+	int num_points;
+};
+
+static bool rw_attr_equal_within_epsilon(uint64_t x, uint64_t ref, double tol)
+{
+	return (x <= (1.0 + tol) * ref) && (x >= (1.0 - tol) * ref);
+}

lib/igt_sysfs.c void fbcon_blink_enable(bool enable) · line 807

Quoted 10 lines
lib/igt_sysfs.c +10 -0
+
+/* Sweep the range of values for an attribute to identify matching reads/writes */
+static int rw_attr_sweep(igt_sysfs_rw_attr_t *rw)
+{
+	struct rw_attr_internal *pts = rw->rsvd;
+	uint64_t get, set = rw->start;
+	bool ret;
+
+	igt_debug("'%s': sweeping range of values\n", rw->attr);
+	while (1) {

Can this be replaced with while(set < UINT64_MAX / 2)?

lib/igt_sysfs.c void fbcon_blink_enable(bool enable) · line 811

Quoted 4 lines
lib/igt_sysfs.c +4 -0
+		if (set >= UINT64_MAX / 2) {
+			igt_debug("'%s': done sweeping\n", rw->attr);
+			break;
+		}

If ret is 0 and num_of_points is > 0 does the loop have to continue? Can we break since we have reached the clamped max?

Thanks
Riana

Quoted 124 lines
lib/igt_sysfs.c +94 -0
+
+		ret = igt_sysfs_set_u64(rw->dir, rw->attr, set);
+		get = igt_sysfs_get_u64(rw->dir, rw->attr);
+		igt_debug("'%s': ret %d set %lu get %lu\n", rw->attr, ret, set, get);
+		if (ret && rw_attr_equal_within_epsilon(get, set, rw->tol)) {
+			pts->points[pts->num_points++] = set;
+			igt_debug("'%s': include %lu\n", rw->attr, set);
+		}
+
+		set *= 2;
+	}
+
+	return pts->num_points ? 0 : -ENOENT;
+}
+
+/* Re-verify that reads following writes are equal within a tolerance */
+static int rw_attr_reverify_points(igt_sysfs_rw_attr_t *rw)
+{
+	struct rw_attr_internal *pts = rw->rsvd;
+	uint64_t get, set;
+	int i;
+
+	igt_debug("'%s': reverifying\n", rw->attr);
+	for (i = pts->num_points - 1; i >= 0; i--) {
+		set = pts->points[i];
+		if (!igt_sysfs_set_u64(rw->dir, rw->attr, set)) {
+			igt_debug("'%s': set %lu failed\n", rw->attr, set);
+			return -EIO;
+		}
+		get = igt_sysfs_get_u64(rw->dir, rw->attr);
+		if (!rw_attr_equal_within_epsilon(get, set, rw->tol)) {
+			igt_debug("'%s': mismatch set %lu get %lu\n", rw->attr, set, get);
+			return -EIO;
+		}
+	}
+	igt_debug("'%s': done reverifying\n", rw->attr);
+
+	return 0;
+}
+
+/**
+ * igt_sysfs_rw_attr_verify:
+ * @rw: 'struct igt_sysfs_rw_attr' describing a rw sysfs attr
+ *
+ * This function attempts to verify writable sysfs attributes, that is the
+ * attribute is first written to and then read back and it is verified that
+ * the read value matches the written value to a tolerance. However, when
+ * we try to do this we run into the issue that a sysfs attribute might
+ * have a behavior where the read value is different from the written value
+ * for any reason. For example, attributes such as power, voltage,
+ * frequency and time typically have a linear region outside which they are
+ * clamped (the values saturate). Therefore for such attributes read values
+ * match the written value only in the linear region and when writing we
+ * don't know if we are writing to the linear or to the clamped region.
+ *
+ * Therefore the verification implemented here takes the approach of
+ * sweeping across the range of possible values of the attribute (this is
+ * done using 'doubling' rather than linearly) and seeing where there are
+ * matches. There should be at least one match (to a tolerance) for the
+ * verification to have succeeded.
+ */
+void igt_sysfs_rw_attr_verify(igt_sysfs_rw_attr_t *rw)
+{
+	uint64_t prev, get;
+	struct stat st;
+	int ret;
+
+	igt_assert(!fstatat(rw->dir, rw->attr, &st, 0));
+	igt_assert(st.st_mode & 0222); /* writable */
+	igt_assert(rw->start);	/* cannot be 0 */
+
+	prev = igt_sysfs_get_u64(rw->dir, rw->attr);
+	igt_debug("'%s': prev %lu\n", rw->attr, prev);
+
+	rw->rsvd = calloc(1, sizeof(struct rw_attr_internal));
+	igt_assert(rw->rsvd);
+
+	ret = rw_attr_sweep(rw);
+	if (ret)
+		goto restore;
+
+	ret = rw_attr_reverify_points(rw);
+
+	/*
+	 * Restore previous value: we don't assert before this point so
+	 * that we can restore the attr before asserting
+	 */
+restore:
+	free(rw->rsvd);
+	igt_assert_eq(1, igt_sysfs_set_u64(rw->dir, rw->attr, prev));
+	get = igt_sysfs_get_u64(rw->dir, rw->attr);
+	igt_assert_eq(get, prev);
+	igt_assert(!ret);
+}
lib/igt_sysfs.h +21 -0
index 1c9791a1bdc..418c800e8c5 100644
@@ -125,4 +125,25 @@ void bind_fbcon(bool enable);
  void kick_snd_hda_intel(void);
  void fbcon_blink_enable(bool enable);
 
+/**
+ * igt_sysfs_rw_attr:
+ * @dir: file descriptor for parent directory
+ * @attr: name of sysfs attribute
+ * @start: start value for searching for matching reads/writes
+ * @tol: tolerance to use to compare written and read values
+ * @rsvd: reserved field used internally
+ *
+ * Structure used to describe the rw sysfs attribute to
+ * igt_sysfs_rw_attr_verify
+ */
+typedef struct igt_sysfs_rw_attr {
+	int dir;
+	char *attr;
+	uint64_t start;
+	double tol;
+	void *rsvd;
+} igt_sysfs_rw_attr_t;
+
+void igt_sysfs_rw_attr_verify(igt_sysfs_rw_attr_t *rw);
+
  #endif /* __IGT_SYSFS_H__ */
#3 lore raw

Re: [igt-dev] [PATCH i-g-t 1/3] lib/igt_sysfs: Generic verification of writable sysfs attributes

Quoted 2 lines · Riana

Hi Ashutosh

Hi Riana,

Quoted 46 lines · Ashutosh Dixit
Quoted 45 lines

Attempt to verify writable sysfs attributes in a generic way, without going into the specifics of any attribute. The attribute is first written to and then read back and it is verified that the read value matches the written value to a tolerance. However, when we try to do this we run into the issue that a sysfs attribute might have a behavior where the read value is different from the written value for any reason. For example, attributes such as power, voltage, frequency and time typically have a linear region outside which they are clamped (the values saturate). Therefore for such attributes read values match the written value only in the linear region and when writing we don't know if we are writing to the linear or to the clamped region.

Therefore the verification implemented here takes the approach of sweeping across the range of possible values of the attribute (this is done using 'doubling' rather than linearly) and seeing where there are matches. There should be at least one match for the verification to have succeeded.

---
  lib/igt_sysfs.c | 119 ++++++++++++++++++++++++++++++++++++++++++++++++
  lib/igt_sysfs.h |  21 +++++++++
  2 files changed, 140 insertions(+)
lib/igt_sysfs.c +14 -0
index a913be4c8f2..c6cccf6fa1e 100644
@@ -784,3 +784,122 @@ void fbcon_blink_enable(bool enable)
 	write(fd, buffer, r + 1);
 	close(fd);
  }
+
+struct rw_attr_internal {
+	/* we need an uint64_t array of max 64 points */
+	uint64_t points[64];
+	int num_points;
+};
+
+static bool rw_attr_equal_within_epsilon(uint64_t x, uint64_t ref, double tol)
+{
+	return (x <= (1.0 + tol) * ref) && (x >= (1.0 - tol) * ref);
+}
+
+/* Sweep the range of values for an attribute to identify matching reads/writes */
+static int rw_attr_sweep(igt_sysfs_rw_attr_t *rw)
Quoted 8 lines

lib/igt_sysfs.c void fbcon_blink_enable(bool enable) · line 807

Quoted 7 lines
lib/igt_sysfs.c +7 -0
+{
+	struct rw_attr_internal *pts = rw->rsvd;
+	uint64_t get, set = rw->start;
+	bool ret;
+
+	igt_debug("'%s': sweeping range of values\n", rw->attr);
+	while (1) {

Can this be replaced with while(set < UINT64_MAX / 2)?

I think it is useful to run this with --debug and see the traces (to see the set and get values). So the debug message below (done sweeping) is convenient to see when the sweep finishes. So you are right but to retain the 'done sweeping' debug message I prefer to leave as is.

Quoted 6 lines

lib/igt_sysfs.c void fbcon_blink_enable(bool enable) · line 811

Quoted 4 lines
lib/igt_sysfs.c +4 -0
+		if (set >= UINT64_MAX / 2) {
+			igt_debug("'%s': done sweeping\n", rw->attr);
+			break;
+		}

If ret is 0 and num_of_points is > 0 does the loop have to continue? Can we break since we have reached the clamped max?

Yeah this is how it was in v1 - v3 of this series. But v4 has dropped the concept of clamping. So now basically for any sysfs attr we just write these values and read them back and if they are within epsilon we retain these points and run a reverification on them. So v4 is basically a generalization of clamping, there are now N points and out of those M "match", and it is no longer needed that the M points be in between clamped min and max. To retain clamping for these rw sysfs attributes was looking awkward.

So because of the above reasons I think we should leave this too as is.

Let me know what you think.

Thanks.
--
Ashutosh

Quoted 124 lines
Quoted 124 lines
lib/igt_sysfs.c +94 -0
+
+		ret = igt_sysfs_set_u64(rw->dir, rw->attr, set);
+		get = igt_sysfs_get_u64(rw->dir, rw->attr);
+		igt_debug("'%s': ret %d set %lu get %lu\n", rw->attr, ret, set, get);
+		if (ret && rw_attr_equal_within_epsilon(get, set, rw->tol)) {
+			pts->points[pts->num_points++] = set;
+			igt_debug("'%s': include %lu\n", rw->attr, set);
+		}
+
+		set *= 2;
+	}
+
+	return pts->num_points ? 0 : -ENOENT;
+}
+
+/* Re-verify that reads following writes are equal within a tolerance */
+static int rw_attr_reverify_points(igt_sysfs_rw_attr_t *rw)
+{
+	struct rw_attr_internal *pts = rw->rsvd;
+	uint64_t get, set;
+	int i;
+
+	igt_debug("'%s': reverifying\n", rw->attr);
+	for (i = pts->num_points - 1; i >= 0; i--) {
+		set = pts->points[i];
+		if (!igt_sysfs_set_u64(rw->dir, rw->attr, set)) {
+			igt_debug("'%s': set %lu failed\n", rw->attr, set);
+			return -EIO;
+		}
+		get = igt_sysfs_get_u64(rw->dir, rw->attr);
+		if (!rw_attr_equal_within_epsilon(get, set, rw->tol)) {
+			igt_debug("'%s': mismatch set %lu get %lu\n", rw->attr, set, get);
+			return -EIO;
+		}
+	}
+	igt_debug("'%s': done reverifying\n", rw->attr);
+
+	return 0;
+}
+
+/**
+ * igt_sysfs_rw_attr_verify:
+ * @rw: 'struct igt_sysfs_rw_attr' describing a rw sysfs attr
+ *
+ * This function attempts to verify writable sysfs attributes, that is the
+ * attribute is first written to and then read back and it is verified that
+ * the read value matches the written value to a tolerance. However, when
+ * we try to do this we run into the issue that a sysfs attribute might
+ * have a behavior where the read value is different from the written value
+ * for any reason. For example, attributes such as power, voltage,
+ * frequency and time typically have a linear region outside which they are
+ * clamped (the values saturate). Therefore for such attributes read values
+ * match the written value only in the linear region and when writing we
+ * don't know if we are writing to the linear or to the clamped region.
+ *
+ * Therefore the verification implemented here takes the approach of
+ * sweeping across the range of possible values of the attribute (this is
+ * done using 'doubling' rather than linearly) and seeing where there are
+ * matches. There should be at least one match (to a tolerance) for the
+ * verification to have succeeded.
+ */
+void igt_sysfs_rw_attr_verify(igt_sysfs_rw_attr_t *rw)
+{
+	uint64_t prev, get;
+	struct stat st;
+	int ret;
+
+	igt_assert(!fstatat(rw->dir, rw->attr, &st, 0));
+	igt_assert(st.st_mode & 0222); /* writable */
+	igt_assert(rw->start);	/* cannot be 0 */
+
+	prev = igt_sysfs_get_u64(rw->dir, rw->attr);
+	igt_debug("'%s': prev %lu\n", rw->attr, prev);
+
+	rw->rsvd = calloc(1, sizeof(struct rw_attr_internal));
+	igt_assert(rw->rsvd);
+
+	ret = rw_attr_sweep(rw);
+	if (ret)
+		goto restore;
+
+	ret = rw_attr_reverify_points(rw);
+
+	/*
+	 * Restore previous value: we don't assert before this point so
+	 * that we can restore the attr before asserting
+	 */
+restore:
+	free(rw->rsvd);
+	igt_assert_eq(1, igt_sysfs_set_u64(rw->dir, rw->attr, prev));
+	get = igt_sysfs_get_u64(rw->dir, rw->attr);
+	igt_assert_eq(get, prev);
+	igt_assert(!ret);
+}
lib/igt_sysfs.h +20 -0
index 1c9791a1bdc..418c800e8c5 100644
@@ -125,4 +125,25 @@ void bind_fbcon(bool enable);
  void kick_snd_hda_intel(void);
  void fbcon_blink_enable(bool enable);
  +/**
+ * igt_sysfs_rw_attr:
+ * @dir: file descriptor for parent directory
+ * @attr: name of sysfs attribute
+ * @start: start value for searching for matching reads/writes
+ * @tol: tolerance to use to compare written and read values
+ * @rsvd: reserved field used internally
+ *
+ * Structure used to describe the rw sysfs attribute to
+ * igt_sysfs_rw_attr_verify
+ */
+typedef struct igt_sysfs_rw_attr {
+	int dir;
+	char *attr;
+	uint64_t start;
+	double tol;
+	void *rsvd;
+} igt_sysfs_rw_attr_t;
+
+void igt_sysfs_rw_attr_verify(igt_sysfs_rw_attr_t *rw);
+
  #endif /* __IGT_SYSFS_H__ */
#4 lore raw

Re: [igt-dev] [PATCH i-g-t 1/3] lib/igt_sysfs: Generic verification of writable sysfs attributes

Quoted 6 lines · Ashutosh
Quoted 2 lines · Riana

Hi Ashutosh

Hi Riana,

FYI: I just posted a v5 after dropping the function rw_attr_reverify_points since it was repeating the verification already done during the sweep so I thought had limited utility. This results in simplifying the code even more. Please review.

Thanks.
--
Ashutosh

#5 lore raw

PATCH 2/3 i915/i915_hwmon: General verification of hwmon attributes

In reply to Ashutosh Dixit

Ensure we can read all hwmon attributes. For writable attributes, ensure the read value approximately matches the written value for a subset of all possible values.

---
 tests/i915/i915_hwmon.c | 88 +++++++++++++++++++++++++++++++++++++++++
 tests/meson.build       |  1 +
 2 files changed, 89 insertions(+)
 create mode 100644 tests/i915/i915_hwmon.c
tests/i915/i915_hwmon.c new file +88 -0
new file mode 100644
index 00000000000..6d9937e99dc
@@ -0,0 +1,88 @@
+// SPDX-License-Identifier: MIT
+/*
+ * Copyright © 2022 Intel Corporation
+ */
+
+#include <dirent.h>
+#include <sys/stat.h>
+#include "igt.h"
+#include "igt_hwmon.h"
+#include "igt_sysfs.h"
+
+IGT_TEST_DESCRIPTION("Tests for i915 hwmon");
+
+static void hwmon_read(int hwm)
+{
+	struct dirent *de;
+	char val[128];
+	DIR *dir;
+
+	dir = fdopendir(dup(hwm));
+	igt_assert(dir);
+	rewinddir(dir);
+
+	while ((de = readdir(dir))) {
+		if (de->d_type != DT_REG || !strcmp(de->d_name, "uevent"))
+			continue;
+
+		igt_assert(igt_sysfs_scanf(hwm, de->d_name, "%127s", val) == 1);
+		igt_debug("'%s': %s\n", de->d_name, val);
+
+	}
+	closedir(dir);
+}
+
+static void hwmon_write(int hwm)
+{
+	igt_sysfs_rw_attr_t rw;
+	struct dirent *de;
+	struct stat st;
+	DIR *dir;
+
+	dir = fdopendir(dup(hwm));
+	igt_assert(dir);
+	rewinddir(dir);
+
+	rw.dir = hwm;
+	rw.start = 1;
+	rw.tol = 0.1;
+
+	while ((de = readdir(dir))) {
+		if (de->d_type != DT_REG || !strcmp(de->d_name, "uevent"))
+			continue;
+
+		igt_assert(!fstatat(hwm, de->d_name, &st, 0));
+		if (!(st.st_mode & 0222))
+			continue;
+
+		rw.attr = de->d_name;
+		igt_sysfs_rw_attr_verify(&rw);
+	}
+	closedir(dir);
+}
+
+igt_main
+{
+	int fd, hwm;
+
+	igt_fixture {
+		fd = drm_open_driver_master(DRIVER_INTEL);
+		hwm = igt_hwmon_open(fd);
+		igt_require(hwm >= 0);
+	}
+
+	igt_describe("Verify we can read all hwmon attributes");
+	igt_subtest("hwmon-read") {
+		hwmon_read(hwm);
+	}
+
+	igt_describe("Verify writable hwmon attributes");
+	igt_subtest("hwmon-write") {
+		hwmon_write(hwm);
+	}
+
+	igt_fixture {
+		close(hwm);
+		close(fd);
+	}
+}
tests/meson.build +1 -0
index 619c18b2516..a593055c23a 100644
@@ -211,6 +211,7 @@ i915_progs = [
 	'i915_fb_tiling',
 	'i915_getparams_basic',
 	'i915_hangman',
+	'i915_hwmon',
 	'i915_module_load',
 	'i915_pciid',
 	'i915_pipe_stress',
Signature · 1 line
2.38.0
#6 lore raw

PATCH 3/3 HAX: Add i915_hwmon* to fast-feedback.testlist

In reply to Ashutosh Dixit

For CI.

---
 tests/intel-ci/fast-feedback.testlist | 2 ++
 1 file changed, 2 insertions(+)
tests/intel-ci/fast-feedback.testlist +2 -0
index f57f8ff3be1..7983d3a2236 100644
@@ -53,6 +53,8 @@ igt@gem_wait@wait@all
 igt@i915_getparams_basic@basic-eu-total
 igt@i915_getparams_basic@basic-subslice-total
 igt@i915_hangman@error-state-basic
+igt@i915_hwmon@hwmon-read
+igt@i915_hwmon@hwmon-write
 igt@i915_pciid
 igt@kms_addfb_basic@addfb25-bad-modifier
 igt@kms_addfb_basic@addfb25-framebuffer-vs-set-tiling
Signature · 1 line
2.38.0
#7 lore raw

[igt-dev] ✓ Fi.CI.BAT: success for i915/i915_hwmon: General verification of hwmon attributes (rev4)

In reply to Ashutosh Dixit
== Series Details ==

== Series Details ==

Series: i915/i915_hwmon: General verification of hwmon attributes (rev4)
URL : https://patchwork.freedesktop.org/series/111833/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_12502 -> IGTPW_8227
====================================================

Summary
-------

**SUCCESS**

No regressions found.

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

Participating hosts (39 -> 18)
------------------------------

Missing (21): fi-kbl-soraka fi-rkl-11600 bat-dg1-6 bat-dg1-5 bat-adlp-6 bat-rpls-1 fi-skl-6600u fi-bsw-n3050 bat-dg2-8 bat-adlm-1 bat-dg2-9 bat-adln-1 bat-jsl-3 bat-rplp-1 bat-dg2-11 fi-bsw-nick bat-dg1-7 bat-kbl-2 bat-adlp-9 bat-jsl-1 bat-adlp-4

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

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

### IGT changes ###

#### Possible regressions ####

* {igt@i915_hwmon@hwmon-read} (NEW):
- fi-adl-ddr5: NOTRUN -> [SKIP][1] +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-adl-ddr5/igt@[email protected]
- {fi-ehl-2}: NOTRUN -> [SKIP][2] +1 similar issue
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-ehl-2/igt@[email protected]

* {igt@i915_hwmon@hwmon-write} (NEW):
- {fi-jsl-1}: NOTRUN -> [SKIP][3] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-jsl-1/igt@[email protected]
- fi-icl-u2: NOTRUN -> [SKIP][4] +1 similar issue
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-icl-u2/igt@[email protected]
- fi-rkl-guc: NOTRUN -> [SKIP][5] +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-rkl-guc/igt@[email protected]

New tests
---------

New tests have been introduced between CI_DRM_12502 and IGTPW_8227:

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

* igt@i915_hwmon@hwmon-read:
- Statuses : 18 skip(s)
- Exec time: [0.0] s

* igt@i915_hwmon@hwmon-write:
- Statuses : 18 skip(s)
- Exec time: [0.0] s

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

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

### IGT changes ###

#### Issues hit ####

* igt@core_hotunplug@unbind-rebind:
- fi-icl-u2: [PASS][6] -> [DMESG-WARN][7] ([i915#1982])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/fi-icl-u2/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-icl-u2/igt@[email protected]

* {igt@i915_hwmon@hwmon-read} (NEW):
- fi-elk-e7500: NOTRUN -> [SKIP][8] ([fdo#109271]) +1 similar issue
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-elk-e7500/igt@[email protected]
- fi-bsw-kefka: NOTRUN -> [SKIP][9] ([fdo#109271]) +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-bsw-kefka/igt@[email protected]
- fi-cfl-guc: NOTRUN -> [SKIP][10] ([fdo#109271]) +1 similar issue
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-cfl-guc/igt@[email protected]
- fi-hsw-4770: NOTRUN -> [SKIP][11] ([fdo#109271]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-hsw-4770/igt@[email protected]
- fi-ivb-3770: NOTRUN -> [SKIP][12] ([fdo#109271]) +1 similar issue
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-ivb-3770/igt@[email protected]

* {igt@i915_hwmon@hwmon-write} (NEW):
- fi-snb-2600: NOTRUN -> [SKIP][13] ([fdo#109271]) +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-snb-2600/igt@[email protected]
- fi-bdw-gvtdvm: NOTRUN -> [SKIP][14] ([fdo#109271]) +1 similar issue
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-bdw-gvtdvm/igt@[email protected]
- fi-pnv-d510: NOTRUN -> [SKIP][15] ([fdo#109271]) +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-pnv-d510/igt@[email protected]
- fi-glk-j4005: NOTRUN -> [SKIP][16] ([fdo#109271]) +1 similar issue
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-glk-j4005/igt@[email protected]
- fi-skl-guc: NOTRUN -> [SKIP][17] ([fdo#109271]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-skl-guc/igt@[email protected]
- fi-skl-6700k2: NOTRUN -> [SKIP][18] ([fdo#109271]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-skl-6700k2/igt@[email protected]
- fi-kbl-7567u: NOTRUN -> [SKIP][19] ([fdo#109271]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-kbl-7567u/igt@[email protected]
- fi-kbl-8809g: NOTRUN -> [SKIP][20] ([fdo#109271]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-kbl-8809g/igt@[email protected]

* igt@kms_chamelium@common-hpd-after-suspend:
- fi-hsw-4770: NOTRUN -> [SKIP][21] ([fdo#109271] / [fdo#111827])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-hsw-4770/igt@[email protected]
- fi-rkl-guc: NOTRUN -> [SKIP][22] ([fdo#111827])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-rkl-guc/igt@[email protected]

#### Possible fixes ####

* igt@i915_selftest@live@gt_lrc:
- fi-rkl-guc: [INCOMPLETE][23] ([i915#4983]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/fi-rkl-guc/igt@i915_selftest@live@gt_lrc.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-rkl-guc/igt@i915_selftest@live@gt_lrc.html

* igt@i915_selftest@live@hangcheck:
- fi-hsw-4770: [INCOMPLETE][25] ([i915#4785]) -> [PASS][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/fi-hsw-4770/igt@i915_selftest@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-hsw-4770/igt@i915_selftest@[email protected]

* igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions:
- fi-bsw-kefka: [FAIL][27] ([i915#6298]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/fi-bsw-kefka/igt@kms_cursor_legacy@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/fi-bsw-kefka/igt@kms_cursor_legacy@[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
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#4785]: https://gitlab.freedesktop.org/drm/intel/issues/4785
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#6298]: https://gitlab.freedesktop.org/drm/intel/issues/6298

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

* CI: CI-20190529 -> None
* IGT: IGT_7092 -> IGTPW_8227

CI-20190529: 20190529
CI_DRM_12502: cc44a1e87ea6b788868878295119398966f98a81 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_8227: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/index.html
IGT_7092: 59e3bf83f6bae0918276f880f969a10d279c657a @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git

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

+igt@i915_hwmon@hwmon-read
+igt@i915_hwmon@hwmon-write
+igt@kms_bw@linear-tiling-1-displays-1920x1080p
+igt@kms_bw@linear-tiling-1-displays-2560x1440p
+igt@kms_bw@linear-tiling-1-displays-3840x2160p
+igt@kms_bw@linear-tiling-2-displays-1920x1080p
+igt@kms_bw@linear-tiling-2-displays-2560x1440p
+igt@kms_bw@linear-tiling-2-displays-3840x2160p
+igt@kms_bw@linear-tiling-3-displays-1920x1080p
+igt@kms_bw@linear-tiling-3-displays-2560x1440p
+igt@kms_bw@linear-tiling-3-displays-3840x2160p
+igt@kms_bw@linear-tiling-4-displays-1920x1080p
+igt@kms_bw@linear-tiling-4-displays-2560x1440p
+igt@kms_bw@linear-tiling-4-displays-3840x2160p
+igt@kms_bw@linear-tiling-5-displays-1920x1080p
+igt@kms_bw@linear-tiling-5-displays-2560x1440p
+igt@kms_bw@linear-tiling-5-displays-3840x2160p
+igt@kms_bw@linear-tiling-6-displays-1920x1080p
+igt@kms_bw@linear-tiling-6-displays-2560x1440p
+igt@kms_bw@linear-tiling-6-displays-3840x2160p

== Logs ==

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

#8 lore raw

[igt-dev] ✓ Fi.CI.IGT: success for i915/i915_hwmon: General verification of hwmon attributes (rev4)

In reply to Ashutosh Dixit
== Series Details ==

== Series Details ==

Series: i915/i915_hwmon: General verification of hwmon attributes (rev4)
URL : https://patchwork.freedesktop.org/series/111833/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_12502_full -> IGTPW_8227_full
====================================================

Summary
-------

**SUCCESS**

No regressions found.

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

Participating hosts (14 -> 6)
------------------------------

Missing (8): pig-kbl-iris shard-tglu-9 shard-tglu-10 shard-tglu pig-glk-j5005 pig-skl-6260u shard-rkl shard-dg1

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

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

### IGT changes ###

#### Possible regressions ####

* {igt@i915_hwmon@hwmon-read} (NEW):
- shard-tglb: NOTRUN -> [SKIP][1] +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@[email protected]

* {igt@i915_hwmon@hwmon-write} (NEW):
- shard-iclb: NOTRUN -> [SKIP][2] +1 similar issue
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb8/igt@[email protected]

New tests
---------

New tests have been introduced between CI_DRM_12502_full and IGTPW_8227_full:

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

* igt@i915_hwmon@hwmon-read:
- Statuses : 4 skip(s)
- Exec time: [0.0] s

* igt@i915_hwmon@hwmon-write:
- Statuses : 4 skip(s)
- Exec time: [0.0] s

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

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

### IGT changes ###

#### Issues hit ####

* igt@drm_mm@all:
- shard-tglb: NOTRUN -> [SKIP][3] ([i915#6433])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@[email protected]

* igt@gem_ccs@suspend-resume:
- shard-iclb: NOTRUN -> [SKIP][4] ([i915#5327])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb6/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][5] ([i915#5325])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@[email protected]

* igt@gem_ctx_persistence@legacy-engines-hostile:
- shard-snb: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#1099])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-snb4/igt@[email protected]

* igt@gem_exec_balancer@parallel-balancer:
- shard-iclb: NOTRUN -> [SKIP][7] ([i915#4525])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb7/igt@[email protected]

* igt@gem_exec_balancer@parallel-out-fence:
- shard-iclb: [PASS][8] -> [SKIP][9] ([i915#4525]) +1 similar issue
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-iclb2/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb3/igt@[email protected]

* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-tglb: NOTRUN -> [FAIL][10] ([i915#2842])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl: [PASS][11] -> [FAIL][12] ([i915#2842]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-apl8/igt@gem_exec_fair@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl8/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-none-vip@rcs0:
- shard-tglb: [PASS][13] -> [FAIL][14] ([i915#2842]) +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-tglb6/igt@gem_exec_fair@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@gem_exec_fair@[email protected]

* igt@gem_exec_schedule@thriceslice:
- shard-snb: NOTRUN -> [SKIP][15] ([fdo#109271]) +94 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-snb4/igt@[email protected]

* igt@gem_huc_copy@huc-copy:
- shard-tglb: [PASS][16] -> [SKIP][17] ([i915#2190])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-tglb1/igt@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@[email protected]

* igt@gem_lmem_swapping@heavy-verify-random:
- shard-apl: NOTRUN -> [SKIP][18] ([fdo#109271] / [i915#4613]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl3/igt@[email protected]

* igt@gem_lmem_swapping@parallel-random-engines:
- shard-iclb: NOTRUN -> [SKIP][19] ([i915#4613]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb7/igt@[email protected]

* igt@gem_lmem_swapping@parallel-random-verify-ccs:
- shard-tglb: NOTRUN -> [SKIP][20] ([i915#4613]) +2 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@[email protected]

* igt@gem_pread@exhaustion:
- shard-tglb: NOTRUN -> [WARN][21] ([i915#2658]) +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@[email protected]

* igt@gem_pwrite@basic-exhaustion:
- shard-apl: NOTRUN -> [WARN][22] ([i915#2658])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl1/igt@[email protected]
- shard-snb: NOTRUN -> [WARN][23] ([i915#2658])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-snb7/igt@[email protected]
- shard-iclb: NOTRUN -> [WARN][24] ([i915#2658])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb6/igt@[email protected]

* igt@gem_pxp@display-protected-crc:
- shard-tglb: NOTRUN -> [SKIP][25] ([i915#4270])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@[email protected]

* igt@gem_render_copy@y-tiled-to-vebox-y-tiled:
- shard-iclb: NOTRUN -> [SKIP][26] ([i915#768]) +3 similar issues
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb6/igt@[email protected]

* igt@gem_userptr_blits@coherency-unsync:
- shard-tglb: NOTRUN -> [SKIP][27] ([i915#3297]) +1 similar issue
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@[email protected]

* igt@gem_userptr_blits@unsync-overlap:
- shard-iclb: NOTRUN -> [SKIP][28] ([i915#3297])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb3/igt@[email protected]

* igt@gen7_exec_parse@load-register-reg:
- shard-tglb: NOTRUN -> [SKIP][29] ([fdo#109289]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb2/igt@[email protected]

* igt@gen9_exec_parse@bb-start-far:
- shard-iclb: NOTRUN -> [SKIP][30] ([i915#2856]) +1 similar issue
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb7/igt@[email protected]

* igt@gen9_exec_parse@cmd-crossing-page:
- shard-tglb: NOTRUN -> [SKIP][31] ([i915#2527] / [i915#2856]) +3 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@[email protected]

* igt@i915_pm_dc@dc6-psr:
- shard-tglb: NOTRUN -> [FAIL][32] ([i915#3989] / [i915#454])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@[email protected]

* igt@i915_pm_freq_mult@media-freq@gt0:
- shard-tglb: NOTRUN -> [SKIP][33] ([i915#6590])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@i915_pm_freq_mult@[email protected]

* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-apl: NOTRUN -> [SKIP][34] ([fdo#109271] / [i915#1937])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl8/igt@i915_pm_lpsp@[email protected]

* igt@i915_pm_rpm@modeset-lpsp:
- shard-apl: NOTRUN -> [SKIP][35] ([fdo#109271]) +89 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl8/igt@[email protected]

* igt@i915_query@hwconfig_table:
- shard-tglb: NOTRUN -> [SKIP][36] ([i915#6245])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@i915_query@hwconfig_table.html

* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-iclb: NOTRUN -> [SKIP][37] ([i915#5286]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb8/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][38] ([i915#5286]) +3 similar issues
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@[email protected]

* igt@kms_big_fb@x-tiled-64bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][39] ([fdo#110725] / [fdo#111614])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb8/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][40] ([fdo#111614])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@[email protected]

* igt@kms_big_fb@yf-tiled-32bpp-rotate-0:
- shard-tglb: NOTRUN -> [SKIP][41] ([fdo#111615]) +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@[email protected]

* igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][42] ([fdo#109271] / [i915#3886]) +4 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl3/igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_gen12_mc_ccs.html

* igt@kms_ccs@pipe-a-bad-pixel-format-4_tiled_dg2_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][43] ([i915#6095]) +1 similar issue
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@kms_ccs@pipe-a-bad-pixel-format-4_tiled_dg2_mc_ccs.html

* igt@kms_ccs@pipe-a-ccs-on-another-bo-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][44] ([fdo#111615] / [i915#3689]) +4 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@kms_ccs@pipe-a-ccs-on-another-bo-yf_tiled_ccs.html

* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs:
- shard-iclb: NOTRUN -> [SKIP][45] ([fdo#109278]) +6 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb2/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs.html

* igt@kms_ccs@pipe-a-random-ccs-data-4_tiled_dg2_rc_ccs:
- shard-tglb: NOTRUN -> [SKIP][46] ([i915#3689] / [i915#6095]) +2 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@kms_ccs@pipe-a-random-ccs-data-4_tiled_dg2_rc_ccs.html

* igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][47] ([i915#3689]) +8 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_ccs.html

* igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][48] ([fdo#109278] / [i915#3886])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb2/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html
- shard-tglb: NOTRUN -> [SKIP][49] ([i915#3689] / [i915#3886])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html

* igt@kms_cdclk@mode-transition:
- shard-iclb: NOTRUN -> [SKIP][50] ([i915#3742])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb3/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][51] ([i915#3742])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@[email protected]

* igt@kms_chamelium@hdmi-aspect-ratio:
- shard-snb: NOTRUN -> [SKIP][52] ([fdo#109271] / [fdo#111827]) +2 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-snb5/igt@[email protected]
- shard-apl: NOTRUN -> [SKIP][53] ([fdo#109271] / [fdo#111827]) +2 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl8/igt@[email protected]

* igt@kms_color_chamelium@ctm-max:
- shard-tglb: NOTRUN -> [SKIP][54] ([fdo#109284] / [fdo#111827]) +7 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@[email protected]

* igt@kms_color_chamelium@degamma:
- shard-iclb: NOTRUN -> [SKIP][55] ([fdo#109284] / [fdo#111827]) +2 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb6/igt@[email protected]

* igt@kms_content_protection@type1:
- shard-tglb: NOTRUN -> [SKIP][56] ([i915#7118])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@[email protected]

* igt@kms_content_protection@uevent@pipe-a-dp-1:
- shard-apl: NOTRUN -> [FAIL][57] ([i915#1339])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl1/igt@kms_content_protection@[email protected]

* igt@kms_cursor_crc@cursor-random-32x10:
- shard-tglb: NOTRUN -> [SKIP][58] ([i915#3555]) +3 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@[email protected]

* igt@kms_cursor_legacy@flip-vs-cursor@varying-size:
- shard-iclb: [PASS][59] -> [FAIL][60] ([i915#2346]) +2 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-iclb8/igt@kms_cursor_legacy@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb7/igt@kms_cursor_legacy@[email protected]

* igt@kms_cursor_legacy@short-busy-flip-before-cursor:
- shard-tglb: NOTRUN -> [SKIP][61] ([i915#4103])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][62] ([i915#4103])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb2/igt@[email protected]

* igt@kms_dp_tiled_display@basic-test-pattern:
- shard-tglb: NOTRUN -> [SKIP][63] ([i915#426])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@[email protected]

* igt@kms_fbcon_fbt@fbc:
- shard-tglb: NOTRUN -> [FAIL][64] ([i915#4767])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@[email protected]

* igt@kms_fbcon_fbt@fbc-suspend:
- shard-tglb: NOTRUN -> [FAIL][65] ([i915#2411] / [i915#4767])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@[email protected]

* igt@kms_flip@2x-single-buffer-flip-vs-dpms-off-vs-modeset-interruptible:
- shard-iclb: NOTRUN -> [SKIP][66] ([fdo#109274]) +1 similar issue
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb7/igt@kms_flip@2x-single-buffer-flip-vs-dpms-off-vs-modeset-interruptible.html
- shard-tglb: NOTRUN -> [SKIP][67] ([fdo#109274] / [fdo#111825] / [i915#3637]) +1 similar issue
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@kms_flip@2x-single-buffer-flip-vs-dpms-off-vs-modeset-interruptible.html

* igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-downscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][68] ([i915#2587] / [i915#2672]) +4 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb5/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-downscaling@pipe-a-valid-mode.html
- shard-tglb: NOTRUN -> [SKIP][69] ([i915#2587] / [i915#2672]) +2 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-downscaling@pipe-a-valid-mode.html

* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][70] ([i915#2672] / [i915#3555])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb3/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-default-mode.html

* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][71] ([i915#2672]) +5 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling@pipe-a-default-mode.html

* igt@kms_force_connector_basic@force-load-detect:
- shard-tglb: NOTRUN -> [SKIP][72] ([fdo#109285])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-shrfb-pgflip-blt:
- shard-tglb: NOTRUN -> [SKIP][73] ([i915#6497]) +9 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-shrfb-pgflip-blt.html

* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-msflip-blt:
- shard-iclb: NOTRUN -> [SKIP][74] ([fdo#109280]) +10 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-msflip-blt.html

* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-pwrite:
- shard-tglb: NOTRUN -> [SKIP][75] ([fdo#109280] / [fdo#111825]) +26 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-indfb-draw-pwrite.html

* igt@kms_plane_lowres@tiling-x@pipe-b-edp-1:
- shard-iclb: NOTRUN -> [SKIP][76] ([i915#3536]) +2 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb3/igt@kms_plane_lowres@[email protected]

* igt@kms_plane_lowres@tiling-x@pipe-c-edp-1:
- shard-tglb: NOTRUN -> [SKIP][77] ([i915#3536]) +3 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@kms_plane_lowres@[email protected]

* igt@kms_plane_scaling@2x-scaler-multi-pipe:
- shard-tglb: NOTRUN -> [SKIP][78] ([fdo#109274] / [fdo#111825]) +1 similar issue
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb6/igt@[email protected]

* igt@kms_plane_scaling@plane-downscale-with-pixel-format-factor-0-5@pipe-b-edp-1:
- shard-iclb: [PASS][79] -> [SKIP][80] ([i915#5176]) +2 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-iclb3/igt@kms_plane_scaling@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb2/igt@kms_plane_scaling@[email protected]

* igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-b-edp-1:
- shard-iclb: NOTRUN -> [SKIP][81] ([i915#5235]) +2 similar issues
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb3/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-b-edp-1.html

* igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-c-edp-1:
- shard-tglb: NOTRUN -> [SKIP][82] ([i915#5235]) +3 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-c-edp-1.html

* igt@kms_psr2_sf@overlay-plane-move-continuous-sf:
- shard-apl: NOTRUN -> [SKIP][83] ([fdo#109271] / [i915#658]) +1 similar issue
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl3/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][84] ([i915#2920]) +1 similar issue
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][85] ([i915#658]) +1 similar issue
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb8/igt@[email protected]

* igt@kms_psr@psr2_basic:
- shard-tglb: NOTRUN -> [FAIL][86] ([i915#132] / [i915#3467]) +2 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb2/igt@kms_psr@psr2_basic.html

* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [PASS][87] -> [SKIP][88] ([fdo#109441]) +1 similar issue
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb6/igt@kms_psr@psr2_sprite_mmap_gtt.html

* igt@kms_psr@psr2_sprite_render:
- shard-iclb: NOTRUN -> [SKIP][89] ([fdo#109441])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb7/igt@kms_psr@psr2_sprite_render.html

* igt@kms_rotation_crc@primary-yf-tiled-reflect-x-270:
- shard-tglb: NOTRUN -> [SKIP][90] ([fdo#111615] / [i915#5289])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@[email protected]

* igt@kms_setmode@invalid-clone-exclusive-crtc:
- shard-iclb: NOTRUN -> [SKIP][91] ([i915#3555]) +3 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb2/igt@[email protected]

* igt@kms_writeback@writeback-invalid-parameters:
- shard-apl: NOTRUN -> [SKIP][92] ([fdo#109271] / [i915#2437])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl1/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][93] ([i915#2437])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][94] ([i915#2437])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb7/igt@[email protected]

* igt@perf@gen12-mi-rpc:
- shard-iclb: NOTRUN -> [SKIP][95] ([fdo#109289]) +1 similar issue
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb7/igt@[email protected]

* igt@sysfs_clients@fair-3:
- shard-tglb: NOTRUN -> [SKIP][96] ([i915#2994]) +1 similar issue
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@[email protected]

* igt@sysfs_clients@recycle-many:
- shard-iclb: NOTRUN -> [SKIP][97] ([i915#2994])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb8/igt@[email protected]
- shard-apl: NOTRUN -> [SKIP][98] ([fdo#109271] / [i915#2994])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl6/igt@[email protected]

#### Possible fixes ####

* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [FAIL][99] ([i915#2842]) -> [PASS][100]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-tglb1/igt@gem_exec_fair@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb5/igt@gem_exec_fair@[email protected]

* igt@i915_selftest@live@gt_heartbeat:
- shard-apl: [DMESG-FAIL][101] ([i915#5334]) -> [PASS][102]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-apl2/igt@i915_selftest@live@gt_heartbeat.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl2/igt@i915_selftest@live@gt_heartbeat.html

* igt@kms_hdmi_inject@inject-audio:
- shard-tglb: [SKIP][103] ([i915#433]) -> [PASS][104]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-tglb5/igt@[email protected]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb1/igt@[email protected]

* igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes:
- shard-tglb: [INCOMPLETE][105] -> [PASS][106]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-tglb5/igt@kms_plane@[email protected]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-tglb7/igt@kms_plane@[email protected]

* igt@kms_psr@psr2_sprite_plane_onoff:
- shard-iclb: [SKIP][107] ([fdo#109441]) -> [PASS][108] +2 similar issues
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-iclb6/igt@kms_psr@psr2_sprite_plane_onoff.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb2/igt@kms_psr@psr2_sprite_plane_onoff.html

* igt@kms_psr_stress_test@invalidate-primary-flip-overlay:
- shard-iclb: [SKIP][109] ([i915#5519]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-iclb1/igt@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb3/igt@[email protected]

* igt@kms_vblank@pipe-b-ts-continuation-suspend:
- shard-apl: [DMESG-WARN][111] ([i915#180]) -> [PASS][112]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-apl8/igt@[email protected]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl6/igt@[email protected]

#### Warnings ####

* igt@kms_plane_alpha_blend@alpha-basic@pipe-c-dp-1:
- shard-apl: [DMESG-FAIL][113] ([IGT#6]) -> [FAIL][114] ([i915#4573]) +1 similar issue
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-apl2/igt@kms_plane_alpha_blend@[email protected]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-apl1/igt@kms_plane_alpha_blend@[email protected]

* igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-sf:
- shard-iclb: [SKIP][115] ([i915#658]) -> [SKIP][116] ([i915#2920])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-iclb5/igt@[email protected]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb2/igt@[email protected]

* igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-fully-sf:
- shard-iclb: [SKIP][117] ([i915#2920]) -> [SKIP][118] ([i915#658])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-iclb2/igt@[email protected]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb8/igt@[email protected]

* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area:
- shard-iclb: [SKIP][119] ([fdo#111068] / [i915#658]) -> [SKIP][120] ([i915#2920])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-iclb1/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb2/igt@[email protected]

* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area:
- shard-iclb: [SKIP][121] ([i915#2920]) -> [SKIP][122] ([fdo#111068] / [i915#658]) +1 similar issue
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12502/shard-iclb2/igt@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/shard-iclb1/igt@[email protected]

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

[IGT#6]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/6
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110725]: https://bugs.freedesktop.org/show_bug.cgi?id=110725
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1339]: https://gitlab.freedesktop.org/drm/intel/issues/1339
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1937]: https://gitlab.freedesktop.org/drm/intel/issues/1937
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3467]: https://gitlab.freedesktop.org/drm/intel/issues/3467
[i915#3536]: https://gitlab.freedesktop.org/drm/intel/issues/3536
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3742]: https://gitlab.freedesktop.org/drm/intel/issues/3742
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3989]: https://gitlab.freedesktop.org/drm/intel/issues/3989
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#426]: https://gitlab.freedesktop.org/drm/intel/issues/426
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#433]: https://gitlab.freedesktop.org/drm/intel/issues/433
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#4573]: https://gitlab.freedesktop.org/drm/intel/issues/4573
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5289]: https://gitlab.freedesktop.org/drm/intel/issues/5289
[i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325
[i915#5327]: https://gitlab.freedesktop.org/drm/intel/issues/5327
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#5519]: https://gitlab.freedesktop.org/drm/intel/issues/5519
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6245]: https://gitlab.freedesktop.org/drm/intel/issues/6245
[i915#6433]: https://gitlab.freedesktop.org/drm/intel/issues/6433
[i915#6497]: https://gitlab.freedesktop.org/drm/intel/issues/6497
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6590]: https://gitlab.freedesktop.org/drm/intel/issues/6590
[i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118
[i915#768]: https://gitlab.freedesktop.org/drm/intel/issues/768

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

* CI: CI-20190529 -> None
* IGT: IGT_7092 -> IGTPW_8227
* Piglit: piglit_4509 -> None

CI-20190529: 20190529
CI_DRM_12502: cc44a1e87ea6b788868878295119398966f98a81 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_8227: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8227/index.html
IGT_7092: 59e3bf83f6bae0918276f880f969a10d279c657a @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit

== Logs ==

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