* [igt-dev] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest
@ 2023-06-12 19:42 Vinay Belgaumkar
2023-06-12 20:50 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915_pm_freq_api: Add a suspend subtest (rev2) Patchwork
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Vinay Belgaumkar @ 2023-06-12 19:42 UTC (permalink / raw)
To: intel-gfx, igt-dev
Verify that SLPC API works as expected after a suspend. Added
another subtest that does multiple GT resets and checks freq api
works as expected after each one.
We now check requested frequency instead of soft min/max after a
reset or suspend. That ensures the soft limits got applied
correctly at init. Also, disable efficient freq before starting the
test which allows current freq to be consistent with SLPC min freq.
v2: Restore freq in exit handler (Ashutosh)
Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
---
tests/i915/i915_pm_freq_api.c | 89 +++++++++++++++++++++++++++--------
1 file changed, 69 insertions(+), 20 deletions(-)
diff --git a/tests/i915/i915_pm_freq_api.c b/tests/i915/i915_pm_freq_api.c
index 9005cd220..4e1d4edca 100644
--- a/tests/i915/i915_pm_freq_api.c
+++ b/tests/i915/i915_pm_freq_api.c
@@ -18,6 +18,12 @@
*
* SUBTEST: freq-reset
* Description: Test basic freq API works after a reset
+ *
+ * SUBTEST: freq-reset-multiple
+ * Description: Test basic freq API works after multiple resets
+ *
+ * SUBTEST: freq-suspend
+ * Description: Test basic freq API works after a runtime suspend
*/
IGT_TEST_DESCRIPTION("Test SLPC freq API");
@@ -79,31 +85,64 @@ static void test_freq_basic_api(int dirfd, int gt)
}
-static void test_reset(int i915, int dirfd, int gt)
+static void test_reset(int i915, int dirfd, int gt, int count)
{
uint32_t rpn = get_freq(dirfd, RPS_RPn_FREQ_MHZ);
int fd;
+ for (int i = 0; i < count; i++) {
+ igt_assert_f(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0,
+ "Failed after %d good cycles\n", i);
+ igt_assert_f(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0,
+ "Failed after %d good cycles\n", i);
+ usleep(ACT_FREQ_LATENCY_US);
+ igt_assert_f(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn,
+ "Failed after %d good cycles\n", i);
+
+ /* Manually trigger a GT reset */
+ fd = igt_debugfs_gt_open(i915, gt, "reset", O_WRONLY);
+ igt_require(fd >= 0);
+ igt_ignore_warn(write(fd, "1\n", 2));
+
+ igt_assert_f(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn,
+ "Failed after %d good cycles\n", i);
+ }
+ close(fd);
+}
+
+static void test_suspend(int i915, int dirfd, int gt)
+{
+ uint32_t rpn = get_freq(dirfd, RPS_RPn_FREQ_MHZ);
+
igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0);
igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0);
usleep(ACT_FREQ_LATENCY_US);
- igt_assert(get_freq(dirfd, RPS_MIN_FREQ_MHZ) == rpn);
+ igt_assert(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn);
- /* Manually trigger a GT reset */
- fd = igt_debugfs_gt_open(i915, gt, "reset", O_WRONLY);
- igt_require(fd >= 0);
- igt_ignore_warn(write(fd, "1\n", 2));
- close(fd);
+ /* Manually trigger a suspend */
+ igt_system_suspend_autoresume(SUSPEND_STATE_S3,
+ SUSPEND_TEST_NONE);
- igt_assert(get_freq(dirfd, RPS_MIN_FREQ_MHZ) == rpn);
- igt_assert(get_freq(dirfd, RPS_MAX_FREQ_MHZ) == rpn);
+ igt_assert(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn);
}
-igt_main
+int i915 = -1;
+uint32_t *stash_min, *stash_max;
+
+static void restore_sysfs_freq(int sig)
{
- int i915 = -1;
- uint32_t *stash_min, *stash_max;
+ int dirfd, gt;
+ /* Restore frequencies */
+ for_each_sysfs_gt_dirfd(i915, dirfd, gt) {
+ igt_pm_ignore_slpc_efficient_freq(i915, dirfd, false);
+ igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, stash_max[gt]) > 0);
+ igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, stash_min[gt]) > 0);
+ }
+ close(i915);
+}
+igt_main
+{
igt_fixture {
int num_gts, dirfd, gt;
@@ -122,7 +161,9 @@ igt_main
for_each_sysfs_gt_dirfd(i915, dirfd, gt) {
stash_min[gt] = get_freq(dirfd, RPS_MIN_FREQ_MHZ);
stash_max[gt] = get_freq(dirfd, RPS_MAX_FREQ_MHZ);
+ igt_pm_ignore_slpc_efficient_freq(i915, dirfd, true);
}
+ igt_install_exit_handler(restore_sysfs_freq);
}
igt_describe("Test basic API for controlling min/max GT frequency");
@@ -140,16 +181,24 @@ igt_main
for_each_sysfs_gt_dirfd(i915, dirfd, gt)
igt_dynamic_f("gt%u", gt)
- test_reset(i915, dirfd, gt);
+ test_reset(i915, dirfd, gt, 1);
}
- igt_fixture {
+ igt_describe("Test basic freq API works after multiple resets");
+ igt_subtest_with_dynamic_f("freq-reset-multiple") {
int dirfd, gt;
- /* Restore frequencies */
- for_each_sysfs_gt_dirfd(i915, dirfd, gt) {
- igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, stash_max[gt]) > 0);
- igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, stash_min[gt]) > 0);
- }
- close(i915);
+
+ for_each_sysfs_gt_dirfd(i915, dirfd, gt)
+ igt_dynamic_f("gt%u", gt)
+ test_reset(i915, dirfd, gt, 50);
+ }
+
+ igt_describe("Test basic freq API works after suspend");
+ igt_subtest_with_dynamic_f("freq-suspend") {
+ int dirfd, gt;
+
+ for_each_sysfs_gt_dirfd(i915, dirfd, gt)
+ igt_dynamic_f("gt%u", gt)
+ test_suspend(i915, dirfd, gt);
}
}
--
2.38.1
^ permalink raw reply related [flat|nested] 5+ messages in thread* [igt-dev] ✓ Fi.CI.BAT: success for tests/i915_pm_freq_api: Add a suspend subtest (rev2) 2023-06-12 19:42 [igt-dev] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest Vinay Belgaumkar @ 2023-06-12 20:50 ` Patchwork 2023-06-13 6:35 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork 2023-06-13 21:25 ` [igt-dev] [Intel-gfx] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest Dixit, Ashutosh 2 siblings, 0 replies; 5+ messages in thread From: Patchwork @ 2023-06-12 20:50 UTC (permalink / raw) To: Vinay Belgaumkar; +Cc: igt-dev [-- Attachment #1: Type: text/plain, Size: 3830 bytes --] == Series Details == Series: tests/i915_pm_freq_api: Add a suspend subtest (rev2) URL : https://patchwork.freedesktop.org/series/118969/ State : success == Summary == CI Bug Log - changes from CI_DRM_13263 -> IGTPW_9154 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/index.html Participating hosts (41 -> 41) ------------------------------ Additional (1): fi-pnv-d510 Missing (1): fi-snb-2520m Known issues ------------ Here are the changes found in IGTPW_9154 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@i915_selftest@live@gt_lrc: - bat-rpls-1: [PASS][1] -> [INCOMPLETE][2] ([i915#4983]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/bat-rpls-1/igt@i915_selftest@live@gt_lrc.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/bat-rpls-1/igt@i915_selftest@live@gt_lrc.html * igt@i915_selftest@live@migrate: - bat-dg2-11: [PASS][3] -> [DMESG-WARN][4] ([i915#7699]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/bat-dg2-11/igt@i915_selftest@live@migrate.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/bat-dg2-11/igt@i915_selftest@live@migrate.html * igt@kms_pipe_crc_basic@nonblocking-crc@pipe-d-dp-1: - bat-dg2-8: [PASS][5] -> [FAIL][6] ([i915#7932]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/bat-dg2-8/igt@kms_pipe_crc_basic@nonblocking-crc@pipe-d-dp-1.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/bat-dg2-8/igt@kms_pipe_crc_basic@nonblocking-crc@pipe-d-dp-1.html * igt@kms_psr@primary_page_flip: - fi-pnv-d510: NOTRUN -> [SKIP][7] ([fdo#109271]) +37 similar issues [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/fi-pnv-d510/igt@kms_psr@primary_page_flip.html * igt@kms_setmode@basic-clone-single-crtc: - fi-pnv-d510: NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#4579]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/fi-pnv-d510/igt@kms_setmode@basic-clone-single-crtc.html #### Possible fixes #### * igt@i915_selftest@live@requests: - {bat-mtlp-8}: [DMESG-FAIL][9] ([i915#7269]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/bat-mtlp-8/igt@i915_selftest@live@requests.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/bat-mtlp-8/igt@i915_selftest@live@requests.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579 [i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983 [i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367 [i915#6763]: https://gitlab.freedesktop.org/drm/intel/issues/6763 [i915#7269]: https://gitlab.freedesktop.org/drm/intel/issues/7269 [i915#7699]: https://gitlab.freedesktop.org/drm/intel/issues/7699 [i915#7932]: https://gitlab.freedesktop.org/drm/intel/issues/7932 Build changes ------------- * CI: CI-20190529 -> None * IGT: IGT_7326 -> IGTPW_9154 CI-20190529: 20190529 CI_DRM_13263: b6601e67405b0d81a1ddd8fb70a99b71ef2e1378 @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_9154: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/index.html IGT_7326: 02c2cf17628b6203d6105d4a91dfe8a101d482ce @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Testlist changes ---------------- +igt@i915_pm_freq_api@freq-reset-multiple +igt@i915_pm_freq_api@freq-suspend == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/index.html [-- Attachment #2: Type: text/html, Size: 4508 bytes --] ^ permalink raw reply [flat|nested] 5+ messages in thread
* [igt-dev] ✓ Fi.CI.IGT: success for tests/i915_pm_freq_api: Add a suspend subtest (rev2) 2023-06-12 19:42 [igt-dev] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest Vinay Belgaumkar 2023-06-12 20:50 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915_pm_freq_api: Add a suspend subtest (rev2) Patchwork @ 2023-06-13 6:35 ` Patchwork 2023-06-13 21:25 ` [igt-dev] [Intel-gfx] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest Dixit, Ashutosh 2 siblings, 0 replies; 5+ messages in thread From: Patchwork @ 2023-06-13 6:35 UTC (permalink / raw) To: Vinay Belgaumkar; +Cc: igt-dev [-- Attachment #1: Type: text/plain, Size: 17704 bytes --] == Series Details == Series: tests/i915_pm_freq_api: Add a suspend subtest (rev2) URL : https://patchwork.freedesktop.org/series/118969/ State : success == Summary == CI Bug Log - changes from CI_DRM_13263_full -> IGTPW_9154_full ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/index.html Participating hosts (7 -> 8) ------------------------------ Additional (1): shard-tglu0 Possible new issues ------------------- Here are the unknown changes that may have been introduced in IGTPW_9154_full: ### IGT changes ### #### Possible regressions #### * {igt@i915_pm_freq_api@freq-reset-multiple@gt0} (NEW): - {shard-dg1}: NOTRUN -> [FAIL][1] +1 similar issue [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-dg1-18/igt@i915_pm_freq_api@freq-reset-multiple@gt0.html * {igt@i915_pm_freq_api@freq-suspend} (NEW): - {shard-rkl}: NOTRUN -> [SKIP][2] +1 similar issue [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-rkl-1/igt@i915_pm_freq_api@freq-suspend.html - {shard-tglu}: NOTRUN -> [SKIP][3] +1 similar issue [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-tglu-3/igt@i915_pm_freq_api@freq-suspend.html #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * igt@i915_pm_freq_api@freq-reset@gt0: - {shard-dg1}: [PASS][4] -> [FAIL][5] [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-dg1-12/igt@i915_pm_freq_api@freq-reset@gt0.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-dg1-19/igt@i915_pm_freq_api@freq-reset@gt0.html New tests --------- New tests have been introduced between CI_DRM_13263_full and IGTPW_9154_full: ### New IGT tests (4) ### * igt@i915_pm_freq_api@freq-reset-multiple: - Statuses : 5 skip(s) - Exec time: [0.0] s * igt@i915_pm_freq_api@freq-reset-multiple@gt0: - Statuses : 1 fail(s) - Exec time: [0.0] s * igt@i915_pm_freq_api@freq-suspend: - Statuses : 5 skip(s) - Exec time: [0.0] s * igt@i915_pm_freq_api@freq-suspend@gt0: - Statuses : 1 fail(s) - Exec time: [0.0] s Known issues ------------ Here are the changes found in IGTPW_9154_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_ppgtt@blt-vs-render-ctx0: - shard-snb: [PASS][6] -> [DMESG-FAIL][7] ([i915#8295]) [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-snb2/igt@gem_ppgtt@blt-vs-render-ctx0.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-snb6/igt@gem_ppgtt@blt-vs-render-ctx0.html * igt@i915_pm_dc@dc9-dpms: - shard-apl: [PASS][8] -> [SKIP][9] ([fdo#109271]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-apl2/igt@i915_pm_dc@dc9-dpms.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-apl6/igt@i915_pm_dc@dc9-dpms.html * igt@i915_pm_rpm@gem-execbuf-stress-pc8: - shard-glk: NOTRUN -> [SKIP][10] ([fdo#109271]) +22 similar issues [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-glk2/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html * igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_mc_ccs: - shard-apl: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#3886]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-apl3/igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_mc_ccs.html * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size: - shard-apl: [PASS][12] -> [FAIL][13] ([i915#2346]) [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-apl1/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-apl6/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html * igt@kms_draw_crc@draw-method-blt@xrgb2101010-ytiled: - shard-glk: [PASS][14] -> [DMESG-WARN][15] ([i915#7936]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-glk7/igt@kms_draw_crc@draw-method-blt@xrgb2101010-ytiled.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-glk7/igt@kms_draw_crc@draw-method-blt@xrgb2101010-ytiled.html * igt@kms_flip@2x-plain-flip-fb-recreate: - shard-snb: NOTRUN -> [SKIP][16] ([fdo#109271]) +16 similar issues [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-snb4/igt@kms_flip@2x-plain-flip-fb-recreate.html * igt@kms_flip@flip-vs-expired-vblank-interruptible@a-dp1: - shard-apl: [PASS][17] -> [FAIL][18] ([i915#79]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-apl4/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-dp1.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-apl6/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-dp1.html * igt@kms_hdr@invalid-hdr: - shard-glk: NOTRUN -> [SKIP][19] ([fdo#109271] / [i915#4579]) +1 similar issue [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-glk1/igt@kms_hdr@invalid-hdr.html * igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes: - shard-snb: [PASS][20] -> [DMESG-WARN][21] ([i915#5090]) [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-snb7/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes.html [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-snb2/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes.html * igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0-5@pipe-b-vga-1: - shard-snb: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#4579]) +12 similar issues [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-snb6/igt@kms_plane_scaling@plane-downscale-with-modifiers-factor-0-5@pipe-b-vga-1.html * igt@kms_plane_scaling@plane-downscale-with-pixel-format-factor-0-25@pipe-c-dp-1: - shard-apl: NOTRUN -> [SKIP][23] ([fdo#109271] / [i915#4579]) +2 similar issues [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-apl2/igt@kms_plane_scaling@plane-downscale-with-pixel-format-factor-0-25@pipe-c-dp-1.html * igt@kms_psr@psr2_sprite_plane_onoff: - shard-apl: NOTRUN -> [SKIP][24] ([fdo#109271]) +77 similar issues [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-apl2/igt@kms_psr@psr2_sprite_plane_onoff.html * igt@kms_setmode@basic@pipe-a-vga-1: - shard-snb: NOTRUN -> [FAIL][25] ([i915#5465]) +1 similar issue [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-snb5/igt@kms_setmode@basic@pipe-a-vga-1.html * igt@perf@stress-open-close@0-rcs0: - shard-glk: [PASS][26] -> [ABORT][27] ([i915#5213] / [i915#7941]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-glk3/igt@perf@stress-open-close@0-rcs0.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-glk5/igt@perf@stress-open-close@0-rcs0.html #### Possible fixes #### * igt@device_reset@unbind-reset-rebind: - {shard-rkl}: [ABORT][28] ([i915#5507]) -> [PASS][29] [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-rkl-2/igt@device_reset@unbind-reset-rebind.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-rkl-4/igt@device_reset@unbind-reset-rebind.html - shard-apl: [ABORT][30] ([i915#5507]) -> [PASS][31] [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-apl3/igt@device_reset@unbind-reset-rebind.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-apl1/igt@device_reset@unbind-reset-rebind.html - {shard-tglu}: [ABORT][32] ([i915#5507]) -> [PASS][33] [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-tglu-8/igt@device_reset@unbind-reset-rebind.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-tglu-6/igt@device_reset@unbind-reset-rebind.html - shard-glk: [ABORT][34] ([i915#5507]) -> [PASS][35] [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-glk4/igt@device_reset@unbind-reset-rebind.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-glk2/igt@device_reset@unbind-reset-rebind.html * igt@gem_ctx_exec@basic-nohangcheck: - {shard-tglu}: [FAIL][36] ([i915#6268]) -> [PASS][37] [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-tglu-7/igt@gem_ctx_exec@basic-nohangcheck.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-tglu-8/igt@gem_ctx_exec@basic-nohangcheck.html * igt@gem_exec_fair@basic-none-solo@rcs0: - shard-apl: [FAIL][38] ([i915#2842]) -> [PASS][39] [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-apl1/igt@gem_exec_fair@basic-none-solo@rcs0.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-apl1/igt@gem_exec_fair@basic-none-solo@rcs0.html * igt@i915_pm_rc6_residency@rc6-idle@rcs0: - {shard-dg1}: [FAIL][40] ([i915#3591]) -> [PASS][41] [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-dg1-18/igt@i915_pm_rc6_residency@rc6-idle@rcs0.html [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-dg1-12/igt@i915_pm_rc6_residency@rc6-idle@rcs0.html * igt@i915_pm_rpm@modeset-lpsp-stress: - {shard-rkl}: [SKIP][42] ([i915#1397]) -> [PASS][43] [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-rkl-6/igt@i915_pm_rpm@modeset-lpsp-stress.html [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-rkl-7/igt@i915_pm_rpm@modeset-lpsp-stress.html * igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-180-hflip-async-flip: - {shard-rkl}: [FAIL][44] ([i915#3743]) -> [PASS][45] [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-rkl-7/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-180-hflip-async-flip.html [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-rkl-2/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-180-hflip-async-flip.html * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions: - shard-glk: [FAIL][46] ([i915#2346]) -> [PASS][47] [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-glk3/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-glk7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html * igt@kms_cursor_legacy@forked-move@pipe-b: - {shard-rkl}: [INCOMPLETE][48] ([i915#8011]) -> [PASS][49] [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-rkl-7/igt@kms_cursor_legacy@forked-move@pipe-b.html [49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-rkl-4/igt@kms_cursor_legacy@forked-move@pipe-b.html * igt@kms_fbcon_fbt@fbc-suspend: - shard-apl: [ABORT][50] ([i915#180]) -> [PASS][51] +1 similar issue [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13263/shard-apl1/igt@kms_fbcon_fbt@fbc-suspend.html [51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/shard-apl3/igt@kms_fbcon_fbt@fbc-suspend.html {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#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274 [fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280 [fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289 [fdo#109312]: https://bugs.freedesktop.org/show_bug.cgi?id=109312 [fdo#109313]: https://bugs.freedesktop.org/show_bug.cgi?id=109313 [fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315 [fdo#109506]: https://bugs.freedesktop.org/show_bug.cgi?id=109506 [fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189 [fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723 [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 [fdo#112283]: https://bugs.freedesktop.org/show_bug.cgi?id=112283 [i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072 [i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397 [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180 [i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825 [i915#1937]: https://gitlab.freedesktop.org/drm/intel/issues/1937 [i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346 [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#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672 [i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842 [i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846 [i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856 [i915#3023]: https://gitlab.freedesktop.org/drm/intel/issues/3023 [i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116 [i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281 [i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282 [i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297 [i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458 [i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555 [i915#3591]: https://gitlab.freedesktop.org/drm/intel/issues/3591 [i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637 [i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638 [i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689 [i915#3742]: https://gitlab.freedesktop.org/drm/intel/issues/3742 [i915#3743]: https://gitlab.freedesktop.org/drm/intel/issues/3743 [i915#3804]: https://gitlab.freedesktop.org/drm/intel/issues/3804 [i915#3840]: https://gitlab.freedesktop.org/drm/intel/issues/3840 [i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886 [i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955 [i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070 [i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078 [i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098 [i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103 [i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270 [i915#4349]: https://gitlab.freedesktop.org/drm/intel/issues/4349 [i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538 [i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579 [i915#4816]: https://gitlab.freedesktop.org/drm/intel/issues/4816 [i915#4936]: https://gitlab.freedesktop.org/drm/intel/issues/4936 [i915#5090]: https://gitlab.freedesktop.org/drm/intel/issues/5090 [i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176 [i915#5213]: https://gitlab.freedesktop.org/drm/intel/issues/5213 [i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235 [i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286 [i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325 [i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533 [i915#5354]: https://gitlab.freedesktop.org/drm/intel/issues/5354 [i915#5439]: https://gitlab.freedesktop.org/drm/intel/issues/5439 [i915#5465]: https://gitlab.freedesktop.org/drm/intel/issues/5465 [i915#5493]: https://gitlab.freedesktop.org/drm/intel/issues/5493 [i915#5507]: https://gitlab.freedesktop.org/drm/intel/issues/5507 [i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095 [i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268 [i915#6301]: https://gitlab.freedesktop.org/drm/intel/issues/6301 [i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658 [i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768 [i915#6953]: https://gitlab.freedesktop.org/drm/intel/issues/6953 [i915#7711]: https://gitlab.freedesktop.org/drm/intel/issues/7711 [i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828 [i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79 [i915#7936]: https://gitlab.freedesktop.org/drm/intel/issues/7936 [i915#7941]: https://gitlab.freedesktop.org/drm/intel/issues/7941 [i915#8011]: https://gitlab.freedesktop.org/drm/intel/issues/8011 [i915#8228]: https://gitlab.freedesktop.org/drm/intel/issues/8228 [i915#8292]: https://gitlab.freedesktop.org/drm/intel/issues/8292 [i915#8295]: https://gitlab.freedesktop.org/drm/intel/issues/8295 Build changes ------------- * CI: CI-20190529 -> None * IGT: IGT_7326 -> IGTPW_9154 * Piglit: piglit_4509 -> None CI-20190529: 20190529 CI_DRM_13263: b6601e67405b0d81a1ddd8fb70a99b71ef2e1378 @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_9154: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9154/index.html IGT_7326: 02c2cf17628b6203d6105d4a91dfe8a101d482ce @ 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_9154/index.html [-- Attachment #2: Type: text/html, Size: 15792 bytes --] ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [igt-dev] [Intel-gfx] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest 2023-06-12 19:42 [igt-dev] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest Vinay Belgaumkar 2023-06-12 20:50 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915_pm_freq_api: Add a suspend subtest (rev2) Patchwork 2023-06-13 6:35 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork @ 2023-06-13 21:25 ` Dixit, Ashutosh 2023-06-14 1:01 ` Belgaumkar, Vinay 2 siblings, 1 reply; 5+ messages in thread From: Dixit, Ashutosh @ 2023-06-13 21:25 UTC (permalink / raw) To: Vinay Belgaumkar; +Cc: igt-dev, intel-gfx On Mon, 12 Jun 2023 12:42:13 -0700, Vinay Belgaumkar wrote: > Hi Vinay, > Verify that SLPC API works as expected after a suspend. Added > another subtest that does multiple GT resets and checks freq api > works as expected after each one. > > We now check requested frequency instead of soft min/max after a > reset or suspend. That ensures the soft limits got applied > correctly at init. Also, disable efficient freq before starting the > test which allows current freq to be consistent with SLPC min freq. > > v2: Restore freq in exit handler (Ashutosh) > > Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com> > --- > tests/i915/i915_pm_freq_api.c | 89 +++++++++++++++++++++++++++-------- > 1 file changed, 69 insertions(+), 20 deletions(-) > > diff --git a/tests/i915/i915_pm_freq_api.c b/tests/i915/i915_pm_freq_api.c > index 9005cd220..4e1d4edca 100644 > --- a/tests/i915/i915_pm_freq_api.c > +++ b/tests/i915/i915_pm_freq_api.c > @@ -18,6 +18,12 @@ > * > * SUBTEST: freq-reset > * Description: Test basic freq API works after a reset > + * > + * SUBTEST: freq-reset-multiple > + * Description: Test basic freq API works after multiple resets > + * > + * SUBTEST: freq-suspend > + * Description: Test basic freq API works after a runtime suspend > */ > > IGT_TEST_DESCRIPTION("Test SLPC freq API"); > @@ -79,31 +85,64 @@ static void test_freq_basic_api(int dirfd, int gt) > > } > > -static void test_reset(int i915, int dirfd, int gt) > +static void test_reset(int i915, int dirfd, int gt, int count) > { > uint32_t rpn = get_freq(dirfd, RPS_RPn_FREQ_MHZ); > int fd; > > + for (int i = 0; i < count; i++) { > + igt_assert_f(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0, > + "Failed after %d good cycles\n", i); > + igt_assert_f(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0, > + "Failed after %d good cycles\n", i); > + usleep(ACT_FREQ_LATENCY_US); > + igt_assert_f(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn, > + "Failed after %d good cycles\n", i); > + > + /* Manually trigger a GT reset */ > + fd = igt_debugfs_gt_open(i915, gt, "reset", O_WRONLY); > + igt_require(fd >= 0); > + igt_ignore_warn(write(fd, "1\n", 2)); No need for 'usleep(ACT_FREQ_LATENCY_US)' here? > + > + igt_assert_f(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn, > + "Failed after %d good cycles\n", i); > + } > + close(fd); > +} > + > +static void test_suspend(int i915, int dirfd, int gt) > +{ > + uint32_t rpn = get_freq(dirfd, RPS_RPn_FREQ_MHZ); > + > igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0); > igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0); > usleep(ACT_FREQ_LATENCY_US); > - igt_assert(get_freq(dirfd, RPS_MIN_FREQ_MHZ) == rpn); > + igt_assert(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn); > > - /* Manually trigger a GT reset */ > - fd = igt_debugfs_gt_open(i915, gt, "reset", O_WRONLY); > - igt_require(fd >= 0); > - igt_ignore_warn(write(fd, "1\n", 2)); > - close(fd); > + /* Manually trigger a suspend */ > + igt_system_suspend_autoresume(SUSPEND_STATE_S3, > + SUSPEND_TEST_NONE); No need for 'usleep(ACT_FREQ_LATENCY_US)' here? > > - igt_assert(get_freq(dirfd, RPS_MIN_FREQ_MHZ) == rpn); > - igt_assert(get_freq(dirfd, RPS_MAX_FREQ_MHZ) == rpn); > + igt_assert(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn); > } > > -igt_main > +int i915 = -1; > +uint32_t *stash_min, *stash_max; nit: could we maybe make these fixed size array's (2 or 4 entries) and drop the malloc's for these, malloc's seem excessive in this case. > + > +static void restore_sysfs_freq(int sig) > { > - int i915 = -1; > - uint32_t *stash_min, *stash_max; > + int dirfd, gt; > + /* Restore frequencies */ > + for_each_sysfs_gt_dirfd(i915, dirfd, gt) { > + igt_pm_ignore_slpc_efficient_freq(i915, dirfd, false); > + igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, stash_max[gt]) > 0); > + igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, stash_min[gt]) > 0); nit: I would remove the igt_assert's from here, it's basically a best effort restore so we try to restore everything even if we fail. > + } > + close(i915); > +} > > +igt_main > +{ > igt_fixture { > int num_gts, dirfd, gt; > > @@ -122,7 +161,9 @@ igt_main > for_each_sysfs_gt_dirfd(i915, dirfd, gt) { > stash_min[gt] = get_freq(dirfd, RPS_MIN_FREQ_MHZ); > stash_max[gt] = get_freq(dirfd, RPS_MAX_FREQ_MHZ); > + igt_pm_ignore_slpc_efficient_freq(i915, dirfd, true); > } > + igt_install_exit_handler(restore_sysfs_freq); > } > > igt_describe("Test basic API for controlling min/max GT frequency"); > @@ -140,16 +181,24 @@ igt_main > > for_each_sysfs_gt_dirfd(i915, dirfd, gt) > igt_dynamic_f("gt%u", gt) > - test_reset(i915, dirfd, gt); > + test_reset(i915, dirfd, gt, 1); > } > > - igt_fixture { > + igt_describe("Test basic freq API works after multiple resets"); > + igt_subtest_with_dynamic_f("freq-reset-multiple") { > int dirfd, gt; > - /* Restore frequencies */ > - for_each_sysfs_gt_dirfd(i915, dirfd, gt) { > - igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, stash_max[gt]) > 0); > - igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, stash_min[gt]) > 0); > - } > - close(i915); > + > + for_each_sysfs_gt_dirfd(i915, dirfd, gt) > + igt_dynamic_f("gt%u", gt) > + test_reset(i915, dirfd, gt, 50); > + } Do we need both "freq-reset" and "freq-reset-multiple"? Since "freq-reset" is a subset of "freq-reset-multiple"? Or we want "freq-reset" to run as part of BAT and "freq-reset-multiple" as part of shards e.g.? > + > + igt_describe("Test basic freq API works after suspend"); > + igt_subtest_with_dynamic_f("freq-suspend") { > + int dirfd, gt; > + > + for_each_sysfs_gt_dirfd(i915, dirfd, gt) > + igt_dynamic_f("gt%u", gt) > + test_suspend(i915, dirfd, gt); > } > } > -- > 2.38.1 > Thanks. -- Ashutosh ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [igt-dev] [Intel-gfx] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest 2023-06-13 21:25 ` [igt-dev] [Intel-gfx] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest Dixit, Ashutosh @ 2023-06-14 1:01 ` Belgaumkar, Vinay 0 siblings, 0 replies; 5+ messages in thread From: Belgaumkar, Vinay @ 2023-06-14 1:01 UTC (permalink / raw) To: Dixit, Ashutosh; +Cc: igt-dev, intel-gfx On 6/13/2023 2:25 PM, Dixit, Ashutosh wrote: > On Mon, 12 Jun 2023 12:42:13 -0700, Vinay Belgaumkar wrote: > Hi Vinay, > >> Verify that SLPC API works as expected after a suspend. Added >> another subtest that does multiple GT resets and checks freq api >> works as expected after each one. >> >> We now check requested frequency instead of soft min/max after a >> reset or suspend. That ensures the soft limits got applied >> correctly at init. Also, disable efficient freq before starting the >> test which allows current freq to be consistent with SLPC min freq. >> >> v2: Restore freq in exit handler (Ashutosh) >> >> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com> >> --- >> tests/i915/i915_pm_freq_api.c | 89 +++++++++++++++++++++++++++-------- >> 1 file changed, 69 insertions(+), 20 deletions(-) >> >> diff --git a/tests/i915/i915_pm_freq_api.c b/tests/i915/i915_pm_freq_api.c >> index 9005cd220..4e1d4edca 100644 >> --- a/tests/i915/i915_pm_freq_api.c >> +++ b/tests/i915/i915_pm_freq_api.c >> @@ -18,6 +18,12 @@ >> * >> * SUBTEST: freq-reset >> * Description: Test basic freq API works after a reset >> + * >> + * SUBTEST: freq-reset-multiple >> + * Description: Test basic freq API works after multiple resets >> + * >> + * SUBTEST: freq-suspend >> + * Description: Test basic freq API works after a runtime suspend >> */ >> >> IGT_TEST_DESCRIPTION("Test SLPC freq API"); >> @@ -79,31 +85,64 @@ static void test_freq_basic_api(int dirfd, int gt) >> >> } >> >> -static void test_reset(int i915, int dirfd, int gt) >> +static void test_reset(int i915, int dirfd, int gt, int count) >> { >> uint32_t rpn = get_freq(dirfd, RPS_RPn_FREQ_MHZ); >> int fd; >> >> + for (int i = 0; i < count; i++) { >> + igt_assert_f(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0, >> + "Failed after %d good cycles\n", i); >> + igt_assert_f(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0, >> + "Failed after %d good cycles\n", i); >> + usleep(ACT_FREQ_LATENCY_US); >> + igt_assert_f(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn, >> + "Failed after %d good cycles\n", i); >> + >> + /* Manually trigger a GT reset */ >> + fd = igt_debugfs_gt_open(i915, gt, "reset", O_WRONLY); >> + igt_require(fd >= 0); >> + igt_ignore_warn(write(fd, "1\n", 2)); > No need for 'usleep(ACT_FREQ_LATENCY_US)' here? Don't think we need it. The delay is specifically for H2G calls. I haven't seen the need for a delay here in the limited testing I have done. > >> + >> + igt_assert_f(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn, >> + "Failed after %d good cycles\n", i); >> + } >> + close(fd); >> +} >> + >> +static void test_suspend(int i915, int dirfd, int gt) >> +{ >> + uint32_t rpn = get_freq(dirfd, RPS_RPn_FREQ_MHZ); >> + >> igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0); >> igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0); >> usleep(ACT_FREQ_LATENCY_US); >> - igt_assert(get_freq(dirfd, RPS_MIN_FREQ_MHZ) == rpn); >> + igt_assert(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn); >> >> - /* Manually trigger a GT reset */ >> - fd = igt_debugfs_gt_open(i915, gt, "reset", O_WRONLY); >> - igt_require(fd >= 0); >> - igt_ignore_warn(write(fd, "1\n", 2)); >> - close(fd); >> + /* Manually trigger a suspend */ >> + igt_system_suspend_autoresume(SUSPEND_STATE_S3, >> + SUSPEND_TEST_NONE); > No need for 'usleep(ACT_FREQ_LATENCY_US)' here? I believe this is a blocking call and will only return after resume completes (when console comes back), so delay is not needed. >> - igt_assert(get_freq(dirfd, RPS_MIN_FREQ_MHZ) == rpn); >> - igt_assert(get_freq(dirfd, RPS_MAX_FREQ_MHZ) == rpn); >> + igt_assert(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn); >> } >> >> -igt_main >> +int i915 = -1; >> +uint32_t *stash_min, *stash_max; > nit: could we maybe make these fixed size array's (2 or 4 entries) and drop > the malloc's for these, malloc's seem excessive in this case. What if this is a multi-card device? Though, one thing missing here is the 'free' for the allocations. Will add that. > >> + >> +static void restore_sysfs_freq(int sig) >> { >> - int i915 = -1; >> - uint32_t *stash_min, *stash_max; >> + int dirfd, gt; >> + /* Restore frequencies */ >> + for_each_sysfs_gt_dirfd(i915, dirfd, gt) { >> + igt_pm_ignore_slpc_efficient_freq(i915, dirfd, false); >> + igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, stash_max[gt]) > 0); >> + igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, stash_min[gt]) > 0); > nit: I would remove the igt_assert's from here, it's basically a best > effort restore so we try to restore everything even if we fail. If we fail, it means the api is not working, so we should flag an error. > >> + } >> + close(i915); >> +} >> >> +igt_main >> +{ >> igt_fixture { >> int num_gts, dirfd, gt; >> >> @@ -122,7 +161,9 @@ igt_main >> for_each_sysfs_gt_dirfd(i915, dirfd, gt) { >> stash_min[gt] = get_freq(dirfd, RPS_MIN_FREQ_MHZ); >> stash_max[gt] = get_freq(dirfd, RPS_MAX_FREQ_MHZ); >> + igt_pm_ignore_slpc_efficient_freq(i915, dirfd, true); >> } >> + igt_install_exit_handler(restore_sysfs_freq); >> } >> >> igt_describe("Test basic API for controlling min/max GT frequency"); >> @@ -140,16 +181,24 @@ igt_main >> >> for_each_sysfs_gt_dirfd(i915, dirfd, gt) >> igt_dynamic_f("gt%u", gt) >> - test_reset(i915, dirfd, gt); >> + test_reset(i915, dirfd, gt, 1); >> } >> >> - igt_fixture { >> + igt_describe("Test basic freq API works after multiple resets"); >> + igt_subtest_with_dynamic_f("freq-reset-multiple") { >> int dirfd, gt; >> - /* Restore frequencies */ >> - for_each_sysfs_gt_dirfd(i915, dirfd, gt) { >> - igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, stash_max[gt]) > 0); >> - igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, stash_min[gt]) > 0); >> - } >> - close(i915); >> + >> + for_each_sysfs_gt_dirfd(i915, dirfd, gt) >> + igt_dynamic_f("gt%u", gt) >> + test_reset(i915, dirfd, gt, 50); >> + } > Do we need both "freq-reset" and "freq-reset-multiple"? Since > "freq-reset" is a subset of "freq-reset-multiple"? Or we want "freq-reset" > to run as part of BAT and "freq-reset-multiple" as part of shards e.g.? yes, something like that. We don't want to run 50 resets every time BAT runs. Thanks, Vinay. > >> + >> + igt_describe("Test basic freq API works after suspend"); >> + igt_subtest_with_dynamic_f("freq-suspend") { >> + int dirfd, gt; >> + >> + for_each_sysfs_gt_dirfd(i915, dirfd, gt) >> + igt_dynamic_f("gt%u", gt) >> + test_suspend(i915, dirfd, gt); >> } >> } >> -- >> 2.38.1 >> > Thanks. > -- > Ashutosh ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-06-14 1:01 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2023-06-12 19:42 [igt-dev] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest Vinay Belgaumkar 2023-06-12 20:50 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915_pm_freq_api: Add a suspend subtest (rev2) Patchwork 2023-06-13 6:35 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork 2023-06-13 21:25 ` [igt-dev] [Intel-gfx] [PATCH v2 i-g-t] tests/i915_pm_freq_api: Add a suspend subtest Dixit, Ashutosh 2023-06-14 1:01 ` Belgaumkar, Vinay
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox