public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Sk Anirban <sk.anirban@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, badal.nilawar@intel.com,
	riana.tauro@intel.com, karthik.poosa@intel.com,
	raag.jadav@intel.com, soham.purkait@intel.com,
	mallesh.koujalagi@intel.com, Sk Anirban <sk.anirban@intel.com>
Subject: [PATCH] tests/intel/xe_pm_residency: ensure C6 GT before cpg-gt-toggle
Date: Mon,  9 Mar 2026 16:27:57 +0530	[thread overview]
Message-ID: <20260309105756.110294-2-sk.anirban@intel.com> (raw)

The test assumes GTs are idle before forcewake is acquired and power-gate
status is validated. If a prior subtest leaves a GT in C0 (GT stays active
for any reason), the final power-gate checks can fail for the wrong reason.
Add an explicit assert for each GT to reach C6 at the start of the test.

Signed-off-by: Sk Anirban <sk.anirban@intel.com>
---
 tests/intel/xe_pm_residency.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/tests/intel/xe_pm_residency.c b/tests/intel/xe_pm_residency.c
index 61b63ed4f..d21878682 100644
--- a/tests/intel/xe_pm_residency.c
+++ b/tests/intel/xe_pm_residency.c
@@ -399,6 +399,10 @@ static void cpg_gt_toggle(int fd)
 {
 	int gt;
 
+	xe_for_each_gt(fd, gt)
+		igt_assert_f(igt_wait(xe_gt_is_in_c6(fd, gt), 1000, 10),
+			     "GT %d should be in C6\n", gt);
+
 	fw_handle = igt_debugfs_open(fd, "forcewake_all", O_RDONLY);
 	igt_assert_lte(0, fw_handle);
 
-- 
2.43.0


             reply	other threads:[~2026-03-09 11:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 10:57 Sk Anirban [this message]
2026-03-09 18:14 ` ✓ Xe.CI.BAT: success for tests/intel/xe_pm_residency: ensure C6 GT before cpg-gt-toggle Patchwork
2026-03-09 18:17 ` ✓ i915.CI.BAT: " Patchwork
2026-03-09 22:39 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-08  6:46   ` Anirban, Sk
2026-03-10  1:59 ` ✗ i915.CI.Full: " Patchwork
2026-04-02 10:50 ` [PATCH] " Poosa, Karthik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260309105756.110294-2-sk.anirban@intel.com \
    --to=sk.anirban@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=karthik.poosa@intel.com \
    --cc=mallesh.koujalagi@intel.com \
    --cc=raag.jadav@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=soham.purkait@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox