Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik Poosa <karthik.poosa@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, riana.tauro@intel.com,
	Karthik Poosa <karthik.poosa@intel.com>
Subject: [PATCH i-g-t v2] tests/intel/xe_pm_residency: Add an assertion on MI_STORE execution time
Date: Tue, 24 Sep 2024 13:33:57 +0530	[thread overview]
Message-ID: <20240924080357.1961472-1-karthik.poosa@intel.com> (raw)

MI_STORE_DWORD generally completes within couple of ms.
Assert if it takes more than 1.2 seconds, as it will cause
IGT test to timeout due to sleep of 120 seconds which is
the current per test timeout.

v2: Correct couple of typos in patch and commit message.

Signed-off-by: Karthik Poosa <karthik.poosa@intel.com>
Reviewed-by: Riana Tauro <riana.tauro@intel.com>
---
 tests/intel/xe_pm_residency.c | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/tests/intel/xe_pm_residency.c b/tests/intel/xe_pm_residency.c
index 0e687558b..75cdeeeee 100644
--- a/tests/intel/xe_pm_residency.c
+++ b/tests/intel/xe_pm_residency.c
@@ -144,6 +144,15 @@ static void exec_load(int fd, struct drm_xe_engine_class_instance *hwe, unsigned
 			  1e-3 * submit,
 			  1e-3 * (elapsed - submit));
 
+		/*
+		 * MI_STORE_DWORD generally completes within couple of ms.
+		 * Assert if it takes more than 1.2 seconds, as it will cause
+		 * IGT test to timeout due to sleep of 120 seconds which is
+		 * the current per test timeout. Currently there is no way to
+		 * read this timeout from IGT test.
+		 */
+		igt_assert((uint64_t)elapsed < (uint64_t)(1.2 * NSEC_PER_SEC));
+
 		syncobj_reset(fd, &syncobj, 1);
 
 		/*
-- 
2.25.1


             reply	other threads:[~2024-09-24  7:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24  8:03 Karthik Poosa [this message]
2024-09-26  1:22 ` ✗ CI.xeBAT: failure for tests/intel/xe_pm_residency: Add an assertion on MI_STORE execution time (rev2) Patchwork
2024-09-26  1:24 ` ✗ Fi.CI.BAT: " Patchwork
2024-09-26  7:33 ` ✗ CI.xeFULL: " Patchwork
2024-09-27  9:05 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-28 16:40 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-30 21:03 ` ✓ CI.xeBAT: success for tests/intel/xe_pm_residency: Add an assertion on MI_STORE execution time (rev3) Patchwork
2024-09-30 21:10 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-01  8:00   ` Poosa, Karthik
2024-10-01  5:27 ` ✗ CI.xeFULL: " Patchwork

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=20240924080357.1961472-1-karthik.poosa@intel.com \
    --to=karthik.poosa@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=riana.tauro@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