[PATCH i-g-t v3 2/5] tests/intel/xe_pmu: Validate engine activity after suspend
Umesh Nerlige Ramappa
umesh.nerlige.ramappa at intel.com
Mon Jun 9 16:38:32 UTC 2025
On Fri, Jun 06, 2025 at 03:40:05PM +0530, Riana Tauro wrote:
>Add a test to validate engine activity after suspend. This is
>to validate if guc action for engine activity is sent after
>suspend
>
>Signed-off-by: Riana Tauro <riana.tauro at intel.com>
LGTM,
Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa at intel.com>
>---
> tests/intel/xe_pmu.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
>diff --git a/tests/intel/xe_pmu.c b/tests/intel/xe_pmu.c
>index d9b0d2c96..e6afca9c4 100644
>--- a/tests/intel/xe_pmu.c
>+++ b/tests/intel/xe_pmu.c
>@@ -46,6 +46,9 @@
> * SUBTEST: engine-activity-gt-reset
> * Description: Test to validate engine activity on all engines before and after gt reset
> *
>+ * SUBTEST: engine-activity-suspend
>+ * Description: Test to validate engine activity on all engines before and after s2idle
>+ *
> * SUBTEST: engine-activity-most-load
> * Description: Test to validate engine activity by running workload on all engines except one
> *
>@@ -847,6 +850,13 @@ igt_main
> engine_activity_load_all(fd, num_engines, TEST_LOAD);
> }
>
>+ igt_describe("Validate engine activity before and after s2idle");
>+ igt_subtest("engine-activity-suspend") {
>+ engine_activity_load_all(fd, num_engines, TEST_LOAD);
>+ igt_system_suspend_autoresume(SUSPEND_STATE_FREEZE, SUSPEND_TEST_NONE);
>+ engine_activity_load_all(fd, num_engines, TEST_LOAD);
>+ }
>+
> igt_subtest_group {
> unsigned int num_fns;
>
>--
>2.47.1
>
More information about the igt-dev
mailing list