* [Intel-gfx] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
@ 2021-02-01 11:57 ` Tvrtko Ursulin
0 siblings, 0 replies; 13+ messages in thread
From: Tvrtko Ursulin @ 2021-02-01 11:57 UTC (permalink / raw)
To: igt-dev; +Cc: Intel-gfx
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Slight improvement with regards to wrapping header components to fit
console width. If a single element is wider than max it can still
overflow but it should now work better for practical console widths.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
tools/intel_gpu_top.c | 84 ++++++++++++++++++++++++++++++++++++-------
1 file changed, 71 insertions(+), 13 deletions(-)
diff --git a/tools/intel_gpu_top.c b/tools/intel_gpu_top.c
index dffc6ebecc57..c43054c3fee8 100644
--- a/tools/intel_gpu_top.c
+++ b/tools/intel_gpu_top.c
@@ -1443,6 +1443,41 @@ static bool print_groups(struct cnt_group **groups)
return print_data;
}
+static int __attribute__ ((format(__printf__, 6, 7)))
+print_header_token(const char *cont, int lines, int con_w, int con_h, int *rem,
+ const char *fmt, ...)
+{
+ const char *indent = "\n ";
+ char buf[256];
+ va_list args;
+ int ret;
+
+ if (lines >= con_h)
+ return lines;
+
+ va_start(args, fmt);
+ ret = vsnprintf(buf, sizeof(buf), fmt, args);
+ assert(ret < sizeof(buf));
+ va_end(args);
+
+ ret = (cont ? strlen(cont) : 0) + strlen(buf);
+ *rem -= ret;
+ if (*rem < 0) {
+ if (++lines >= con_h)
+ return lines;
+
+ *rem = con_w - ret - strlen(indent);
+ cont = indent;
+ }
+
+ if (cont)
+ ret = printf("%s%s", cont, buf);
+ else
+ ret = printf("%s", buf);
+
+ return lines;
+}
+
static int
print_header(const struct igt_device_card *card,
const char *codename,
@@ -1520,22 +1555,45 @@ print_header(const struct igt_device_card *card,
*consumed = print_groups(groups);
if (output_mode == INTERACTIVE) {
+ int rem = con_w;
+
printf("\033[H\033[J");
- if (lines++ < con_h)
- printf("intel-gpu-top: %s @ %s\n",
- codename, card->card);
- if (lines++ < con_h) {
- printf("%s/%s MHz; %s%% RC6; ",
- freq_items[1].buf, freq_items[0].buf,
- rc6_items[0].buf);
- if (engines->r_gpu.present) {
- printf("%s/%s W; ",
- power_items[0].buf,
- power_items[1].buf);
- }
- printf("%s irqs/s\n", irq_items[0].buf);
+ lines = print_header_token(NULL, lines, con_w, con_h, &rem,
+ "intel-gpu-top:");
+
+ lines = print_header_token(" ", lines, con_w, con_h, &rem,
+ "%s", codename);
+
+ lines = print_header_token(" @ ", lines, con_w, con_h, &rem,
+ "%s", card->card);
+
+ lines = print_header_token(" - ", lines, con_w, con_h, &rem,
+ "%s/%s MHz",
+ freq_items[1].buf,
+ freq_items[0].buf);
+
+ lines = print_header_token("; ", lines, con_w, con_h, &rem,
+ "%s%% RC6",
+ rc6_items[0].buf);
+
+ if (engines->r_gpu.present) {
+ lines = print_header_token("; ", lines, con_w, con_h,
+ &rem,
+ "%s/%s W",
+ power_items[0].buf,
+ power_items[1].buf);
}
+
+ lines = print_header_token("; ", lines, con_w, con_h, &rem,
+ "%s irqs/s",
+ irq_items[0].buf);
+
+ if (lines++ < con_h)
+ printf("\n");
+
+ if (lines++ < con_h)
+ printf("\n");
}
return lines;
--
2.27.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 13+ messages in thread
* [igt-dev] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
@ 2021-02-01 11:57 ` Tvrtko Ursulin
0 siblings, 0 replies; 13+ messages in thread
From: Tvrtko Ursulin @ 2021-02-01 11:57 UTC (permalink / raw)
To: igt-dev; +Cc: Intel-gfx, Tvrtko Ursulin
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Slight improvement with regards to wrapping header components to fit
console width. If a single element is wider than max it can still
overflow but it should now work better for practical console widths.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
tools/intel_gpu_top.c | 84 ++++++++++++++++++++++++++++++++++++-------
1 file changed, 71 insertions(+), 13 deletions(-)
diff --git a/tools/intel_gpu_top.c b/tools/intel_gpu_top.c
index dffc6ebecc57..c43054c3fee8 100644
--- a/tools/intel_gpu_top.c
+++ b/tools/intel_gpu_top.c
@@ -1443,6 +1443,41 @@ static bool print_groups(struct cnt_group **groups)
return print_data;
}
+static int __attribute__ ((format(__printf__, 6, 7)))
+print_header_token(const char *cont, int lines, int con_w, int con_h, int *rem,
+ const char *fmt, ...)
+{
+ const char *indent = "\n ";
+ char buf[256];
+ va_list args;
+ int ret;
+
+ if (lines >= con_h)
+ return lines;
+
+ va_start(args, fmt);
+ ret = vsnprintf(buf, sizeof(buf), fmt, args);
+ assert(ret < sizeof(buf));
+ va_end(args);
+
+ ret = (cont ? strlen(cont) : 0) + strlen(buf);
+ *rem -= ret;
+ if (*rem < 0) {
+ if (++lines >= con_h)
+ return lines;
+
+ *rem = con_w - ret - strlen(indent);
+ cont = indent;
+ }
+
+ if (cont)
+ ret = printf("%s%s", cont, buf);
+ else
+ ret = printf("%s", buf);
+
+ return lines;
+}
+
static int
print_header(const struct igt_device_card *card,
const char *codename,
@@ -1520,22 +1555,45 @@ print_header(const struct igt_device_card *card,
*consumed = print_groups(groups);
if (output_mode == INTERACTIVE) {
+ int rem = con_w;
+
printf("\033[H\033[J");
- if (lines++ < con_h)
- printf("intel-gpu-top: %s @ %s\n",
- codename, card->card);
- if (lines++ < con_h) {
- printf("%s/%s MHz; %s%% RC6; ",
- freq_items[1].buf, freq_items[0].buf,
- rc6_items[0].buf);
- if (engines->r_gpu.present) {
- printf("%s/%s W; ",
- power_items[0].buf,
- power_items[1].buf);
- }
- printf("%s irqs/s\n", irq_items[0].buf);
+ lines = print_header_token(NULL, lines, con_w, con_h, &rem,
+ "intel-gpu-top:");
+
+ lines = print_header_token(" ", lines, con_w, con_h, &rem,
+ "%s", codename);
+
+ lines = print_header_token(" @ ", lines, con_w, con_h, &rem,
+ "%s", card->card);
+
+ lines = print_header_token(" - ", lines, con_w, con_h, &rem,
+ "%s/%s MHz",
+ freq_items[1].buf,
+ freq_items[0].buf);
+
+ lines = print_header_token("; ", lines, con_w, con_h, &rem,
+ "%s%% RC6",
+ rc6_items[0].buf);
+
+ if (engines->r_gpu.present) {
+ lines = print_header_token("; ", lines, con_w, con_h,
+ &rem,
+ "%s/%s W",
+ power_items[0].buf,
+ power_items[1].buf);
}
+
+ lines = print_header_token("; ", lines, con_w, con_h, &rem,
+ "%s irqs/s",
+ irq_items[0].buf);
+
+ if (lines++ < con_h)
+ printf("\n");
+
+ if (lines++ < con_h)
+ printf("\n");
}
return lines;
--
2.27.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
2021-02-01 11:57 ` [igt-dev] " Tvrtko Ursulin
@ 2021-02-01 12:07 ` Chris Wilson
-1 siblings, 0 replies; 13+ messages in thread
From: Chris Wilson @ 2021-02-01 12:07 UTC (permalink / raw)
To: Tvrtko Ursulin, igt-dev; +Cc: Intel-gfx
Quoting Tvrtko Ursulin (2021-02-01 11:57:56)
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Slight improvement with regards to wrapping header components to fit
> console width. If a single element is wider than max it can still
> overflow but it should now work better for practical console widths.
<----
intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0
900/ 949 MHz; 0% RC6; 6.97/18.42 W; 2 irqs/s
IMC reads: 6 MiB/s
IMC writes: 0 MiB/s
---->
intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0 - 903/ 954 MHz; 0% RC6
7.16/18.40 W; 14 irqs/s
IMC reads: 80 MiB/s
IMC writes: 0 MiB/s
I thought it looked reasonably tidy, without adding any lines to the
header.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
@ 2021-02-01 12:07 ` Chris Wilson
0 siblings, 0 replies; 13+ messages in thread
From: Chris Wilson @ 2021-02-01 12:07 UTC (permalink / raw)
To: Tvrtko Ursulin, igt-dev; +Cc: Intel-gfx
Quoting Tvrtko Ursulin (2021-02-01 11:57:56)
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Slight improvement with regards to wrapping header components to fit
> console width. If a single element is wider than max it can still
> overflow but it should now work better for practical console widths.
<----
intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0
900/ 949 MHz; 0% RC6; 6.97/18.42 W; 2 irqs/s
IMC reads: 6 MiB/s
IMC writes: 0 MiB/s
---->
intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0 - 903/ 954 MHz; 0% RC6
7.16/18.40 W; 14 irqs/s
IMC reads: 80 MiB/s
IMC writes: 0 MiB/s
I thought it looked reasonably tidy, without adding any lines to the
header.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 13+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for intel_gpu_top: Wrap interactive header
2021-02-01 11:57 ` [igt-dev] " Tvrtko Ursulin
(?)
(?)
@ 2021-02-01 13:36 ` Patchwork
-1 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2021-02-01 13:36 UTC (permalink / raw)
To: Tvrtko Ursulin; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 3400 bytes --]
== Series Details ==
Series: intel_gpu_top: Wrap interactive header
URL : https://patchwork.freedesktop.org/series/86528/
State : success
== Summary ==
CI Bug Log - changes from IGT_5983 -> IGTPW_5461
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/index.html
Known issues
------------
Here are the changes found in IGTPW_5461 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_fence@basic-busy@bcs0:
- fi-kbl-soraka: NOTRUN -> [SKIP][1] ([fdo#109271]) +23 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/fi-kbl-soraka/igt@gem_exec_fence@basic-busy@bcs0.html
* igt@gem_huc_copy@huc-copy:
- fi-kbl-soraka: NOTRUN -> [SKIP][2] ([fdo#109271] / [i915#2190])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/fi-kbl-soraka/igt@gem_huc_copy@huc-copy.html
* igt@i915_selftest@live@gt_pm:
- fi-kbl-soraka: NOTRUN -> [DMESG-FAIL][3] ([i915#1886] / [i915#2291])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html
* igt@kms_addfb_basic@addfb25-y-tiled-small-legacy:
- fi-bdw-5557u: NOTRUN -> [SKIP][4] ([fdo#109271]) +3 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/fi-bdw-5557u/igt@kms_addfb_basic@addfb25-y-tiled-small-legacy.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-soraka: NOTRUN -> [SKIP][5] ([fdo#109271] / [fdo#111827]) +8 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/fi-kbl-soraka/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@dp-crc-fast:
- fi-bdw-5557u: NOTRUN -> [SKIP][6] ([fdo#109271] / [fdo#111827]) +8 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/fi-bdw-5557u/igt@kms_chamelium@dp-crc-fast.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-kbl-soraka: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#533])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/fi-kbl-soraka/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2291]: https://gitlab.freedesktop.org/drm/intel/issues/2291
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
Participating hosts (45 -> 35)
------------------------------
Additional (1): fi-kbl-soraka
Missing (11): fi-jsl-1 fi-ilk-m540 fi-hsw-4200u fi-byt-j1900 fi-bsw-cyan fi-apl-guc fi-ctg-p8600 fi-dg1-1 fi-cml-drallion fi-tgl-y fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5983 -> IGTPW_5461
CI-20190529: 20190529
CI_DRM_9712: 5276d4e84db68c095d7bacc0f3943936b49ef829 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5461: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/index.html
IGT_5983: 536e0c2e9a63721596cdf93e996e7469cadfaaae @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/index.html
[-- Attachment #1.2: Type: text/html, Size: 4552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 13+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for intel_gpu_top: Wrap interactive header
2021-02-01 11:57 ` [igt-dev] " Tvrtko Ursulin
` (2 preceding siblings ...)
(?)
@ 2021-02-01 17:53 ` Patchwork
-1 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2021-02-01 17:53 UTC (permalink / raw)
To: Tvrtko Ursulin; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 30254 bytes --]
== Series Details ==
Series: intel_gpu_top: Wrap interactive header
URL : https://patchwork.freedesktop.org/series/86528/
State : failure
== Summary ==
CI Bug Log - changes from IGT_5983_full -> IGTPW_5461_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_5461_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_5461_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_5461/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_5461_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_exec_balancer@hang:
- shard-iclb: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-iclb3/igt@gem_exec_balancer@hang.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb4/igt@gem_exec_balancer@hang.html
* igt@kms_color@pipe-b-legacy-gamma-reset:
- shard-apl: [PASS][3] -> [FAIL][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl2/igt@kms_color@pipe-b-legacy-gamma-reset.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl7/igt@kms_color@pipe-b-legacy-gamma-reset.html
- shard-kbl: [PASS][5] -> [FAIL][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl7/igt@kms_color@pipe-b-legacy-gamma-reset.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl2/igt@kms_color@pipe-b-legacy-gamma-reset.html
Known issues
------------
Here are the changes found in IGTPW_5461_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-kbl: NOTRUN -> [DMESG-WARN][7] ([i915#180]) +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl7/igt@gem_ctx_isolation@preservation-s3@bcs0.html
* igt@gem_ctx_isolation@preservation-s3@vecs0:
- shard-apl: NOTRUN -> [DMESG-WARN][8] ([i915#180])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl1/igt@gem_ctx_isolation@preservation-s3@vecs0.html
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [PASS][9] -> [FAIL][10] ([i915#2846])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl6/igt@gem_exec_fair@basic-deadline.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl1/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-iclb: NOTRUN -> [FAIL][11] ([i915#2842])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb1/igt@gem_exec_fair@basic-none-rrul@rcs0.html
- shard-glk: NOTRUN -> [FAIL][12] ([i915#2842])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk1/igt@gem_exec_fair@basic-none-rrul@rcs0.html
- shard-tglb: NOTRUN -> [FAIL][13] ([i915#2842])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb7/igt@gem_exec_fair@basic-none-rrul@rcs0.html
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-tglb: [PASS][14] -> [FAIL][15] ([i915#2842]) +2 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-tglb2/igt@gem_exec_fair@basic-none-share@rcs0.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb1/igt@gem_exec_fair@basic-none-share@rcs0.html
- shard-apl: [PASS][16] -> [SKIP][17] ([fdo#109271])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl4/igt@gem_exec_fair@basic-none-share@rcs0.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl2/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_whisper@basic-contexts-priority-all:
- shard-glk: [PASS][18] -> [DMESG-WARN][19] ([i915#118] / [i915#95])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-glk1/igt@gem_exec_whisper@basic-contexts-priority-all.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk8/igt@gem_exec_whisper@basic-contexts-priority-all.html
* igt@gem_render_copy@yf-tiled-to-vebox-linear:
- shard-iclb: NOTRUN -> [SKIP][20] ([i915#768]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@gem_render_copy@yf-tiled-to-vebox-linear.html
* igt@gem_userptr_blits@coherency-unsync:
- shard-tglb: NOTRUN -> [SKIP][21] ([fdo#110542])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb7/igt@gem_userptr_blits@coherency-unsync.html
- shard-iclb: NOTRUN -> [SKIP][22] ([fdo#109290])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb1/igt@gem_userptr_blits@coherency-unsync.html
* igt@gen3_render_mixed_blits:
- shard-hsw: NOTRUN -> [SKIP][23] ([fdo#109271]) +59 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-hsw7/igt@gen3_render_mixed_blits.html
- shard-iclb: NOTRUN -> [SKIP][24] ([fdo#109289]) +2 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@gen3_render_mixed_blits.html
* igt@gen3_render_tiledy_blits:
- shard-tglb: NOTRUN -> [SKIP][25] ([fdo#109289]) +2 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb1/igt@gen3_render_tiledy_blits.html
* igt@gen9_exec_parse@bb-chained:
- shard-iclb: NOTRUN -> [SKIP][26] ([fdo#112306]) +3 similar issues
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb3/igt@gen9_exec_parse@bb-chained.html
* igt@gen9_exec_parse@bb-start-out:
- shard-tglb: NOTRUN -> [SKIP][27] ([fdo#112306]) +3 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb7/igt@gen9_exec_parse@bb-start-out.html
* igt@i915_pm_rpm@dpms-non-lpsp:
- shard-tglb: NOTRUN -> [SKIP][28] ([fdo#111644] / [i915#1397] / [i915#2411]) +1 similar issue
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb1/igt@i915_pm_rpm@dpms-non-lpsp.html
* igt@i915_pm_rpm@modeset-non-lpsp:
- shard-iclb: NOTRUN -> [SKIP][29] ([fdo#110892]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@i915_pm_rpm@modeset-non-lpsp.html
* igt@i915_selftest@live@hangcheck:
- shard-hsw: [PASS][30] -> [INCOMPLETE][31] ([i915#2782])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-hsw6/igt@i915_selftest@live@hangcheck.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-hsw4/igt@i915_selftest@live@hangcheck.html
* igt@kms_async_flips@test-time-stamp:
- shard-tglb: NOTRUN -> [FAIL][32] ([i915#2597])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb2/igt@kms_async_flips@test-time-stamp.html
* igt@kms_atomic_transition@plane-all-modeset-transition-fencing:
- shard-iclb: NOTRUN -> [SKIP][33] ([i915#1769])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html
- shard-tglb: NOTRUN -> [SKIP][34] ([i915#1769])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb1/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html
* igt@kms_big_fb@yf-tiled-32bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][35] ([fdo#111615]) +2 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb2/igt@kms_big_fb@yf-tiled-32bpp-rotate-270.html
* igt@kms_big_joiner@basic:
- shard-tglb: NOTRUN -> [SKIP][36] ([i915#2705])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb7/igt@kms_big_joiner@basic.html
- shard-kbl: NOTRUN -> [SKIP][37] ([fdo#109271] / [i915#2705])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl6/igt@kms_big_joiner@basic.html
- shard-iclb: NOTRUN -> [SKIP][38] ([i915#2705])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb4/igt@kms_big_joiner@basic.html
- shard-glk: NOTRUN -> [SKIP][39] ([fdo#109271] / [i915#2705])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk3/igt@kms_big_joiner@basic.html
* igt@kms_chamelium@dp-audio-edid:
- shard-tglb: NOTRUN -> [SKIP][40] ([fdo#109284] / [fdo#111827]) +7 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb8/igt@kms_chamelium@dp-audio-edid.html
* igt@kms_chamelium@dp-hpd-with-enabled-mode:
- shard-glk: NOTRUN -> [SKIP][41] ([fdo#109271] / [fdo#111827]) +8 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk4/igt@kms_chamelium@dp-hpd-with-enabled-mode.html
- shard-apl: NOTRUN -> [SKIP][42] ([fdo#109271] / [fdo#111827]) +5 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl4/igt@kms_chamelium@dp-hpd-with-enabled-mode.html
* igt@kms_chamelium@hdmi-hpd-storm:
- shard-kbl: NOTRUN -> [SKIP][43] ([fdo#109271] / [fdo#111827]) +10 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl4/igt@kms_chamelium@hdmi-hpd-storm.html
* igt@kms_chamelium@vga-hpd-with-enabled-mode:
- shard-iclb: NOTRUN -> [SKIP][44] ([fdo#109284] / [fdo#111827]) +7 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@kms_chamelium@vga-hpd-with-enabled-mode.html
* igt@kms_color@pipe-a-ctm-max:
- shard-kbl: NOTRUN -> [FAIL][45] ([i915#1292])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl6/igt@kms_color@pipe-a-ctm-max.html
* igt@kms_color@pipe-d-ctm-blue-to-red:
- shard-iclb: NOTRUN -> [SKIP][46] ([fdo#109278] / [i915#1149])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb3/igt@kms_color@pipe-d-ctm-blue-to-red.html
* igt@kms_color_chamelium@pipe-c-ctm-limited-range:
- shard-hsw: NOTRUN -> [SKIP][47] ([fdo#109271] / [fdo#111827]) +6 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-hsw8/igt@kms_color_chamelium@pipe-c-ctm-limited-range.html
- shard-snb: NOTRUN -> [SKIP][48] ([fdo#109271] / [fdo#111827]) +6 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-snb6/igt@kms_color_chamelium@pipe-c-ctm-limited-range.html
* igt@kms_cursor_crc@pipe-a-cursor-512x512-sliding:
- shard-iclb: NOTRUN -> [SKIP][49] ([fdo#109278] / [fdo#109279]) +1 similar issue
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb1/igt@kms_cursor_crc@pipe-a-cursor-512x512-sliding.html
* igt@kms_cursor_crc@pipe-b-cursor-dpms:
- shard-apl: [PASS][50] -> [FAIL][51] ([i915#54])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl3/igt@kms_cursor_crc@pipe-b-cursor-dpms.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl3/igt@kms_cursor_crc@pipe-b-cursor-dpms.html
- shard-kbl: [PASS][52] -> [FAIL][53] ([i915#54])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl4/igt@kms_cursor_crc@pipe-b-cursor-dpms.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl1/igt@kms_cursor_crc@pipe-b-cursor-dpms.html
* igt@kms_cursor_crc@pipe-c-cursor-512x512-sliding:
- shard-tglb: NOTRUN -> [SKIP][54] ([fdo#109279]) +1 similar issue
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb1/igt@kms_cursor_crc@pipe-c-cursor-512x512-sliding.html
* igt@kms_cursor_crc@pipe-d-cursor-256x256-random:
- shard-glk: NOTRUN -> [SKIP][55] ([fdo#109271]) +48 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk3/igt@kms_cursor_crc@pipe-d-cursor-256x256-random.html
* igt@kms_cursor_crc@pipe-d-cursor-256x256-rapid-movement:
- shard-iclb: NOTRUN -> [SKIP][56] ([fdo#109278]) +7 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@kms_cursor_crc@pipe-d-cursor-256x256-rapid-movement.html
* igt@kms_cursor_crc@pipe-d-cursor-alpha-transparent:
- shard-hsw: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#533]) +8 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-hsw6/igt@kms_cursor_crc@pipe-d-cursor-alpha-transparent.html
* igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge:
- shard-snb: NOTRUN -> [SKIP][58] ([fdo#109271]) +89 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-snb7/igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge.html
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy:
- shard-hsw: [PASS][59] -> [FAIL][60] ([i915#96])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-hsw2/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-hsw1/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
* igt@kms_cursor_legacy@cursorb-vs-flipb-toggle:
- shard-iclb: NOTRUN -> [SKIP][61] ([fdo#109274] / [fdo#109278])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb4/igt@kms_cursor_legacy@cursorb-vs-flipb-toggle.html
* igt@kms_cursor_legacy@flip-vs-cursor-varying-size:
- shard-tglb: [PASS][62] -> [FAIL][63] ([i915#2346])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-tglb5/igt@kms_cursor_legacy@flip-vs-cursor-varying-size.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb1/igt@kms_cursor_legacy@flip-vs-cursor-varying-size.html
* igt@kms_flip@2x-blocking-wf_vblank:
- shard-iclb: NOTRUN -> [SKIP][64] ([fdo#109274]) +3 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@kms_flip@2x-blocking-wf_vblank.html
* igt@kms_flip@flip-vs-suspend@a-dp1:
- shard-apl: [PASS][65] -> [DMESG-WARN][66] ([i915#180]) +3 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl3/igt@kms_flip@flip-vs-suspend@a-dp1.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl7/igt@kms_flip@flip-vs-suspend@a-dp1.html
* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: [PASS][67] -> [DMESG-WARN][68] ([i915#180]) +2 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl2/igt@kms_flip@flip-vs-suspend@c-dp1.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl7/igt@kms_flip@flip-vs-suspend@c-dp1.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-pgflip-blt:
- shard-snb: NOTRUN -> [FAIL][69] ([i915#2546]) +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-snb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-pgflip-blt.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move:
- shard-apl: [PASS][70] -> [FAIL][71] ([i915#49])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move.html
- shard-glk: [PASS][72] -> [FAIL][73] ([i915#49]) +1 similar issue
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-glk3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move.html
- shard-kbl: [PASS][74] -> [FAIL][75] ([i915#49])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt:
- shard-kbl: NOTRUN -> [SKIP][76] ([fdo#109271]) +74 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-cur-indfb-onoff:
- shard-tglb: NOTRUN -> [SKIP][77] ([fdo#111825]) +18 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-cur-indfb-onoff.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt:
- shard-apl: NOTRUN -> [SKIP][78] ([fdo#109271]) +50 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-pgflip-blt:
- shard-iclb: NOTRUN -> [SKIP][79] ([fdo#109280]) +13 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb4/igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-pgflip-blt.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- shard-glk: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#533])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk3/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][81] ([fdo#108145] / [i915#265])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl6/igt@kms_plane_alpha_blend@pipe-a-alpha-7efc.html
* igt@kms_prime@basic-crc@first-to-second:
- shard-iclb: NOTRUN -> [SKIP][82] ([i915#1836])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@kms_prime@basic-crc@first-to-second.html
- shard-tglb: NOTRUN -> [SKIP][83] ([i915#1836])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb1/igt@kms_prime@basic-crc@first-to-second.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1:
- shard-kbl: NOTRUN -> [SKIP][84] ([fdo#109271] / [i915#658]) +3 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl4/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
- shard-apl: NOTRUN -> [SKIP][85] ([fdo#109271] / [i915#658]) +1 similar issue
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl3/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4.html
- shard-tglb: NOTRUN -> [SKIP][86] ([i915#2920]) +1 similar issue
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb1/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4.html
- shard-iclb: NOTRUN -> [SKIP][87] ([i915#658]) +1 similar issue
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb1/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-3:
- shard-glk: NOTRUN -> [SKIP][88] ([fdo#109271] / [i915#658]) +1 similar issue
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-3.html
* igt@kms_psr@psr2_primary_mmap_gtt:
- shard-iclb: [PASS][89] -> [SKIP][90] ([fdo#109441]) +1 similar issue
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-iclb2/igt@kms_psr@psr2_primary_mmap_gtt.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb4/igt@kms_psr@psr2_primary_mmap_gtt.html
* igt@kms_psr@psr2_suspend:
- shard-iclb: NOTRUN -> [SKIP][91] ([fdo#109441]) +1 similar issue
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb3/igt@kms_psr@psr2_suspend.html
* igt@kms_psr@sprite_render:
- shard-hsw: NOTRUN -> [SKIP][92] ([fdo#109271] / [i915#1072]) +2 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-hsw7/igt@kms_psr@sprite_render.html
* igt@kms_vblank@pipe-a-query-idle-hang:
- shard-snb: [PASS][93] -> [SKIP][94] ([fdo#109271]) +3 similar issues
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-snb6/igt@kms_vblank@pipe-a-query-idle-hang.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-snb7/igt@kms_vblank@pipe-a-query-idle-hang.html
* igt@kms_vrr@flip-dpms:
- shard-iclb: NOTRUN -> [SKIP][95] ([fdo#109502])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@kms_vrr@flip-dpms.html
- shard-tglb: NOTRUN -> [SKIP][96] ([fdo#109502])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb7/igt@kms_vrr@flip-dpms.html
* igt@kms_writeback@writeback-check-output:
- shard-apl: NOTRUN -> [SKIP][97] ([fdo#109271] / [i915#2437])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl2/igt@kms_writeback@writeback-check-output.html
- shard-kbl: NOTRUN -> [SKIP][98] ([fdo#109271] / [i915#2437])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl7/igt@kms_writeback@writeback-check-output.html
- shard-glk: NOTRUN -> [SKIP][99] ([fdo#109271] / [i915#2437])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk8/igt@kms_writeback@writeback-check-output.html
* igt@nouveau_crc@pipe-a-ctx-flip-detection:
- shard-iclb: NOTRUN -> [SKIP][100] ([i915#2530])
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb6/igt@nouveau_crc@pipe-a-ctx-flip-detection.html
* igt@nouveau_crc@pipe-d-ctx-flip-detection:
- shard-tglb: NOTRUN -> [SKIP][101] ([i915#2530]) +1 similar issue
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb2/igt@nouveau_crc@pipe-d-ctx-flip-detection.html
- shard-iclb: NOTRUN -> [SKIP][102] ([fdo#109278] / [i915#2530])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb5/igt@nouveau_crc@pipe-d-ctx-flip-detection.html
* igt@perf_pmu@event-wait@rcs0:
- shard-iclb: NOTRUN -> [SKIP][103] ([fdo#112283])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb7/igt@perf_pmu@event-wait@rcs0.html
- shard-tglb: NOTRUN -> [SKIP][104] ([fdo#112283])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb7/igt@perf_pmu@event-wait@rcs0.html
* igt@prime_nv_api@i915_nv_double_import:
- shard-tglb: NOTRUN -> [SKIP][105] ([fdo#109291]) +2 similar issues
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-tglb1/igt@prime_nv_api@i915_nv_double_import.html
* igt@prime_udl:
- shard-iclb: NOTRUN -> [SKIP][106] ([fdo#109291]) +2 similar issues
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb8/igt@prime_udl.html
#### Possible fixes ####
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-glk: [FAIL][107] ([i915#2842]) -> [PASS][108] +4 similar issues
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-glk6/igt@gem_exec_fair@basic-none-solo@rcs0.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk6/igt@gem_exec_fair@basic-none-solo@rcs0.html
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-iclb: [FAIL][109] ([i915#2842]) -> [PASS][110] +1 similar issue
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-iclb3/igt@gem_exec_fair@basic-pace@rcs0.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb7/igt@gem_exec_fair@basic-pace@rcs0.html
* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-glk: [FAIL][111] ([i915#2389]) -> [PASS][112]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-glk6/igt@gem_exec_reloc@basic-many-active@rcs0.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk4/igt@gem_exec_reloc@basic-many-active@rcs0.html
* igt@gem_exec_schedule@u-fairslice@vecs0:
- shard-glk: [DMESG-WARN][113] ([i915#1610] / [i915#2803]) -> [PASS][114]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-glk7/igt@gem_exec_schedule@u-fairslice@vecs0.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk1/igt@gem_exec_schedule@u-fairslice@vecs0.html
* igt@i915_suspend@debugfs-reader:
- shard-apl: [DMESG-WARN][115] ([i915#180]) -> [PASS][116]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl8/igt@i915_suspend@debugfs-reader.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl1/igt@i915_suspend@debugfs-reader.html
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-kbl: [DMESG-WARN][117] ([i915#180]) -> [PASS][118]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl7/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl2/igt@kms_cursor_crc@pipe-b-cursor-suspend.html
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ac-hdmi-a1-hdmi-a2:
- shard-glk: [FAIL][119] ([i915#79]) -> [PASS][120]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-glk1/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ac-hdmi-a1-hdmi-a2.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-glk1/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ac-hdmi-a1-hdmi-a2.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-dp1:
- shard-apl: [FAIL][121] ([i915#79]) -> [PASS][122]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl3/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-dp1.html
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl4/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-dp1.html
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [SKIP][123] ([fdo#109441]) -> [PASS][124] +2 similar issues
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-iclb3/igt@kms_psr@psr2_primary_page_flip.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
#### Warnings ####
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: [WARN][125] ([i915#1804] / [i915#2684]) -> [WARN][126] ([i915#2681] / [i915#2684])
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-iclb6/igt@i915_pm_rc6_residency@rc6-fence.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb1/igt@i915_pm_rc6_residency@rc6-fence.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4:
- shard-iclb: [SKIP][127] ([i915#658]) -> [SKIP][128] ([i915#2920])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-iclb3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb2/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-2:
- shard-iclb: [SKIP][129] ([i915#2920]) -> [SKIP][130] ([i915#658])
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-iclb2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-2.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-iclb3/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-2.html
* igt@runner@aborted:
- shard-kbl: ([FAIL][131], [FAIL][132], [FAIL][133], [FAIL][134], [FAIL][135]) ([i915#1814] / [i915#2295] / [i915#2426]) -> ([FAIL][136], [FAIL][137], [FAIL][138], [FAIL][139], [FAIL][140]) ([i915#1436] / [i915#2295] / [i915#2505])
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl7/igt@runner@aborted.html
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl1/igt@runner@aborted.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl1/igt@runner@aborted.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl7/igt@runner@aborted.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-kbl4/igt@runner@aborted.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl4/igt@runner@aborted.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl2/igt@runner@aborted.html
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl7/igt@runner@aborted.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl7/igt@runner@aborted.html
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-kbl6/igt@runner@aborted.html
- shard-apl: ([FAIL][141], [FAIL][142], [FAIL][143], [FAIL][144]) ([i915#2295]) -> ([FAIL][145], [FAIL][146], [FAIL][147], [FAIL][148], [FAIL][149], [FAIL][150]) ([i915#1814] / [i915#2295])
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl8/igt@runner@aborted.html
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl8/igt@runner@aborted.html
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl1/igt@runner@aborted.html
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5983/shard-apl2/igt@runner@aborted.html
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl8/igt@runner@aborted.html
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl4/igt@runner@aborted.html
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl1/igt@runner@aborted.html
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl1/igt@runner@aborted.html
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl1/igt@runner@aborted.html
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/shard-apl7/igt@runner@aborted.html
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5461/index.html
[-- Attachment #1.2: Type: text/html, Size: 34050 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
2021-02-01 12:07 ` [igt-dev] " Chris Wilson
@ 2021-02-03 10:31 ` Tvrtko Ursulin
-1 siblings, 0 replies; 13+ messages in thread
From: Tvrtko Ursulin @ 2021-02-03 10:31 UTC (permalink / raw)
To: Chris Wilson, igt-dev; +Cc: Intel-gfx
On 01/02/2021 12:07, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2021-02-01 11:57:56)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Slight improvement with regards to wrapping header components to fit
>> console width. If a single element is wider than max it can still
>> overflow but it should now work better for practical console widths.
>
> <----
> intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0
> 900/ 949 MHz; 0% RC6; 6.97/18.42 W; 2 irqs/s
> IMC reads: 6 MiB/s
> IMC writes: 0 MiB/s
>
> ---->
> intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0 - 903/ 954 MHz; 0% RC6
> 7.16/18.40 W; 14 irqs/s
>
> IMC reads: 80 MiB/s
> IMC writes: 0 MiB/s
>
> I thought it looked reasonably tidy, without adding any lines to the
> header.
Or on a wider terminal:
<----
intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0
0/ 0 MHz; 100% RC6; 0.00/ 1.29 W; 0 irqs/s
IMC reads: 138 MiB/s
IMC writes: 6 MiB/s
--->
intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0 - 0/ 0 MHz; 100% RC6; 0.00/ 0.00 W; 0 irqs/s
IMC reads: 77 MiB/s
IMC writes: 4 MiB/s
So a "fight" between 80 chars vs 120 (or so). :) It may be a bit of an over-engineered solution but I don't like the wrap on a wide terminal, plus I like an extra blank line.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
@ 2021-02-03 10:31 ` Tvrtko Ursulin
0 siblings, 0 replies; 13+ messages in thread
From: Tvrtko Ursulin @ 2021-02-03 10:31 UTC (permalink / raw)
To: Chris Wilson, igt-dev; +Cc: Intel-gfx
On 01/02/2021 12:07, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2021-02-01 11:57:56)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Slight improvement with regards to wrapping header components to fit
>> console width. If a single element is wider than max it can still
>> overflow but it should now work better for practical console widths.
>
> <----
> intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0
> 900/ 949 MHz; 0% RC6; 6.97/18.42 W; 2 irqs/s
> IMC reads: 6 MiB/s
> IMC writes: 0 MiB/s
>
> ---->
> intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0 - 903/ 954 MHz; 0% RC6
> 7.16/18.40 W; 14 irqs/s
>
> IMC reads: 80 MiB/s
> IMC writes: 0 MiB/s
>
> I thought it looked reasonably tidy, without adding any lines to the
> header.
Or on a wider terminal:
<----
intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0
0/ 0 MHz; 100% RC6; 0.00/ 1.29 W; 0 irqs/s
IMC reads: 138 MiB/s
IMC writes: 6 MiB/s
--->
intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0 - 0/ 0 MHz; 100% RC6; 0.00/ 0.00 W; 0 irqs/s
IMC reads: 77 MiB/s
IMC writes: 4 MiB/s
So a "fight" between 80 chars vs 120 (or so). :) It may be a bit of an over-engineered solution but I don't like the wrap on a wide terminal, plus I like an extra blank line.
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Intel-gfx] [igt-dev] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
2021-02-03 10:31 ` [igt-dev] " Tvrtko Ursulin
@ 2021-02-03 11:00 ` Chris Wilson
-1 siblings, 0 replies; 13+ messages in thread
From: Chris Wilson @ 2021-02-03 11:00 UTC (permalink / raw)
To: Tvrtko Ursulin, igt-dev; +Cc: Intel-gfx
Quoting Tvrtko Ursulin (2021-02-03 10:31:04)
>
> On 01/02/2021 12:07, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2021-02-01 11:57:56)
> >> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >>
> >> Slight improvement with regards to wrapping header components to fit
> >> console width. If a single element is wider than max it can still
> >> overflow but it should now work better for practical console widths.
> >
> > <----
> > intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0
> > 900/ 949 MHz; 0% RC6; 6.97/18.42 W; 2 irqs/s
> > IMC reads: 6 MiB/s
> > IMC writes: 0 MiB/s
> >
> > ---->
> > intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0 - 903/ 954 MHz; 0% RC6
> > 7.16/18.40 W; 14 irqs/s
> >
> > IMC reads: 80 MiB/s
> > IMC writes: 0 MiB/s
> >
> > I thought it looked reasonably tidy, without adding any lines to the
> > header.
>
> Or on a wider terminal:
> <----
> intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0
> 0/ 0 MHz; 100% RC6; 0.00/ 1.29 W; 0 irqs/s
> IMC reads: 138 MiB/s
> IMC writes: 6 MiB/s
> --->
> intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0 - 0/ 0 MHz; 100% RC6; 0.00/ 0.00 W; 0 irqs/s
>
> IMC reads: 77 MiB/s
> IMC writes: 4 MiB/s
>
>
> So a "fight" between 80 chars vs 120 (or so). :) It may be a bit of an over-engineered solution but I don't like the wrap on a wide terminal, plus I like an extra blank line.
But the memory counters are visually similar to the
frequency/rc6/power/interrupts...
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
@ 2021-02-03 11:00 ` Chris Wilson
0 siblings, 0 replies; 13+ messages in thread
From: Chris Wilson @ 2021-02-03 11:00 UTC (permalink / raw)
To: Tvrtko Ursulin, igt-dev; +Cc: Intel-gfx
Quoting Tvrtko Ursulin (2021-02-03 10:31:04)
>
> On 01/02/2021 12:07, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2021-02-01 11:57:56)
> >> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >>
> >> Slight improvement with regards to wrapping header components to fit
> >> console width. If a single element is wider than max it can still
> >> overflow but it should now work better for practical console widths.
> >
> > <----
> > intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0
> > 900/ 949 MHz; 0% RC6; 6.97/18.42 W; 2 irqs/s
> > IMC reads: 6 MiB/s
> > IMC writes: 0 MiB/s
> >
> > ---->
> > intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0 - 903/ 954 MHz; 0% RC6
> > 7.16/18.40 W; 14 irqs/s
> >
> > IMC reads: 80 MiB/s
> > IMC writes: 0 MiB/s
> >
> > I thought it looked reasonably tidy, without adding any lines to the
> > header.
>
> Or on a wider terminal:
> <----
> intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0
> 0/ 0 MHz; 100% RC6; 0.00/ 1.29 W; 0 irqs/s
> IMC reads: 138 MiB/s
> IMC writes: 6 MiB/s
> --->
> intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0 - 0/ 0 MHz; 100% RC6; 0.00/ 0.00 W; 0 irqs/s
>
> IMC reads: 77 MiB/s
> IMC writes: 4 MiB/s
>
>
> So a "fight" between 80 chars vs 120 (or so). :) It may be a bit of an over-engineered solution but I don't like the wrap on a wide terminal, plus I like an extra blank line.
But the memory counters are visually similar to the
frequency/rc6/power/interrupts...
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Intel-gfx] [igt-dev] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
2021-02-03 11:00 ` [igt-dev] [Intel-gfx] " Chris Wilson
(?)
@ 2021-02-03 13:12 ` Tvrtko Ursulin
2021-02-03 17:02 ` [igt-dev] [Intel-gfx] " Chris Wilson
-1 siblings, 1 reply; 13+ messages in thread
From: Tvrtko Ursulin @ 2021-02-03 13:12 UTC (permalink / raw)
To: Chris Wilson, igt-dev; +Cc: Intel-gfx
On 03/02/2021 11:00, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2021-02-03 10:31:04)
>>
>> On 01/02/2021 12:07, Chris Wilson wrote:
>>> Quoting Tvrtko Ursulin (2021-02-01 11:57:56)
>>>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>>>
>>>> Slight improvement with regards to wrapping header components to fit
>>>> console width. If a single element is wider than max it can still
>>>> overflow but it should now work better for practical console widths.
>>>
>>> <----
>>> intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0
>>> 900/ 949 MHz; 0% RC6; 6.97/18.42 W; 2 irqs/s
>>> IMC reads: 6 MiB/s
>>> IMC writes: 0 MiB/s
>>>
>>> ---->
>>> intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0 - 903/ 954 MHz; 0% RC6
>>> 7.16/18.40 W; 14 irqs/s
>>>
>>> IMC reads: 80 MiB/s
>>> IMC writes: 0 MiB/s
>>>
>>> I thought it looked reasonably tidy, without adding any lines to the
>>> header.
>>
>> Or on a wider terminal:
>> <----
>> intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0
>> 0/ 0 MHz; 100% RC6; 0.00/ 1.29 W; 0 irqs/s
>> IMC reads: 138 MiB/s
>> IMC writes: 6 MiB/s
>> --->
>> intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0 - 0/ 0 MHz; 100% RC6; 0.00/ 0.00 W; 0 irqs/s
>>
>> IMC reads: 77 MiB/s
>> IMC writes: 4 MiB/s
>>
>>
>> So a "fight" between 80 chars vs 120 (or so). :) It may be a bit of an over-engineered solution but I don't like the wrap on a wide terminal, plus I like an extra blank line.
>
> But the memory counters are visually similar to the
> frequency/rc6/power/interrupts...
But I broke my layout by accident when rebasing client stats... ;D
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Intel-gfx] [igt-dev] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
2021-02-03 13:12 ` [Intel-gfx] [igt-dev] " Tvrtko Ursulin
@ 2021-02-03 17:02 ` Chris Wilson
0 siblings, 0 replies; 13+ messages in thread
From: Chris Wilson @ 2021-02-03 17:02 UTC (permalink / raw)
To: Tvrtko Ursulin, igt-dev; +Cc: Intel-gfx
Quoting Tvrtko Ursulin (2021-02-03 13:12:05)
>
> On 03/02/2021 11:00, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2021-02-03 10:31:04)
> >>
> >> On 01/02/2021 12:07, Chris Wilson wrote:
> >>> Quoting Tvrtko Ursulin (2021-02-01 11:57:56)
> >>>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >>>>
> >>>> Slight improvement with regards to wrapping header components to fit
> >>>> console width. If a single element is wider than max it can still
> >>>> overflow but it should now work better for practical console widths.
> >>>
> >>> <----
> >>> intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0
> >>> 900/ 949 MHz; 0% RC6; 6.97/18.42 W; 2 irqs/s
> >>> IMC reads: 6 MiB/s
> >>> IMC writes: 0 MiB/s
> >>>
> >>> ---->
> >>> intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0 - 903/ 954 MHz; 0% RC6
> >>> 7.16/18.40 W; 14 irqs/s
> >>>
> >>> IMC reads: 80 MiB/s
> >>> IMC writes: 0 MiB/s
> >>>
> >>> I thought it looked reasonably tidy, without adding any lines to the
> >>> header.
> >>
> >> Or on a wider terminal:
> >> <----
> >> intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0
> >> 0/ 0 MHz; 100% RC6; 0.00/ 1.29 W; 0 irqs/s
> >> IMC reads: 138 MiB/s
> >> IMC writes: 6 MiB/s
> >> --->
> >> intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0 - 0/ 0 MHz; 100% RC6; 0.00/ 0.00 W; 0 irqs/s
> >>
> >> IMC reads: 77 MiB/s
> >> IMC writes: 4 MiB/s
> >>
> >>
> >> So a "fight" between 80 chars vs 120 (or so). :) It may be a bit of an over-engineered solution but I don't like the wrap on a wide terminal, plus I like an extra blank line.
> >
> > But the memory counters are visually similar to the
> > frequency/rc6/power/interrupts...
>
> But I broke my layout by accident when rebasing client stats... ;D
Strange. Did you take a vacation or something ;)
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] intel_gpu_top: Wrap interactive header
@ 2021-02-03 17:02 ` Chris Wilson
0 siblings, 0 replies; 13+ messages in thread
From: Chris Wilson @ 2021-02-03 17:02 UTC (permalink / raw)
To: Tvrtko Ursulin, igt-dev; +Cc: Intel-gfx
Quoting Tvrtko Ursulin (2021-02-03 13:12:05)
>
> On 03/02/2021 11:00, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2021-02-03 10:31:04)
> >>
> >> On 01/02/2021 12:07, Chris Wilson wrote:
> >>> Quoting Tvrtko Ursulin (2021-02-01 11:57:56)
> >>>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >>>>
> >>>> Slight improvement with regards to wrapping header components to fit
> >>>> console width. If a single element is wider than max it can still
> >>>> overflow but it should now work better for practical console widths.
> >>>
> >>> <----
> >>> intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0
> >>> 900/ 949 MHz; 0% RC6; 6.97/18.42 W; 2 irqs/s
> >>> IMC reads: 6 MiB/s
> >>> IMC writes: 0 MiB/s
> >>>
> >>> ---->
> >>> intel-gpu-top: Intel Kabylake (Gen9) @ /dev/dri/card0 - 903/ 954 MHz; 0% RC6
> >>> 7.16/18.40 W; 14 irqs/s
> >>>
> >>> IMC reads: 80 MiB/s
> >>> IMC writes: 0 MiB/s
> >>>
> >>> I thought it looked reasonably tidy, without adding any lines to the
> >>> header.
> >>
> >> Or on a wider terminal:
> >> <----
> >> intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0
> >> 0/ 0 MHz; 100% RC6; 0.00/ 1.29 W; 0 irqs/s
> >> IMC reads: 138 MiB/s
> >> IMC writes: 6 MiB/s
> >> --->
> >> intel-gpu-top: Intel Skylake (Gen9) @ /dev/dri/card0 - 0/ 0 MHz; 100% RC6; 0.00/ 0.00 W; 0 irqs/s
> >>
> >> IMC reads: 77 MiB/s
> >> IMC writes: 4 MiB/s
> >>
> >>
> >> So a "fight" between 80 chars vs 120 (or so). :) It may be a bit of an over-engineered solution but I don't like the wrap on a wide terminal, plus I like an extra blank line.
> >
> > But the memory counters are visually similar to the
> > frequency/rc6/power/interrupts...
>
> But I broke my layout by accident when rebasing client stats... ;D
Strange. Did you take a vacation or something ;)
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2021-02-03 17:02 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-01 11:57 [Intel-gfx] [PATCH i-g-t] intel_gpu_top: Wrap interactive header Tvrtko Ursulin
2021-02-01 11:57 ` [igt-dev] " Tvrtko Ursulin
2021-02-01 12:07 ` [Intel-gfx] " Chris Wilson
2021-02-01 12:07 ` [igt-dev] " Chris Wilson
2021-02-03 10:31 ` Tvrtko Ursulin
2021-02-03 10:31 ` [igt-dev] " Tvrtko Ursulin
2021-02-03 11:00 ` [Intel-gfx] [igt-dev] " Chris Wilson
2021-02-03 11:00 ` [igt-dev] [Intel-gfx] " Chris Wilson
2021-02-03 13:12 ` [Intel-gfx] [igt-dev] " Tvrtko Ursulin
2021-02-03 17:02 ` Chris Wilson
2021-02-03 17:02 ` [igt-dev] [Intel-gfx] " Chris Wilson
2021-02-01 13:36 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-02-01 17:53 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.