All of lore.kernel.org
 help / color / mirror / Atom feed
From: sinjan.kumar@intel.com
To: igt-dev@lists.freedesktop.org, sai.gowtham.ch@intel.com,
	kamil.konieczny@linux.intel.com, janga.rahul.kumar@intel.com,
	ramadevi.gandi@intel.com, priyanka.dandamudi@intel.com,
	sinjan.kumar@intel.com
Subject: [igt-dev] [PATCH 1/2] tests/i915/gem_busy : Added subtests description
Date: Thu, 23 Jun 2022 17:42:52 +0530	[thread overview]
Message-ID: <20220623121253.1352382-2-sinjan.kumar@intel.com> (raw)
In-Reply-To: <20220623121253.1352382-1-sinjan.kumar@intel.com>

From: Sinjan Kumar <sinjan.kumar@intel.com>

Added subtest description to gem_busy tests

Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Signed-off-by: Sinjan Kumar <sinjan.kumar@intel.com>
---
 tests/i915/gem_busy.c | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/tests/i915/gem_busy.c b/tests/i915/gem_busy.c
index 603691f2..63028069 100644
--- a/tests/i915/gem_busy.c
+++ b/tests/i915/gem_busy.c
@@ -447,6 +447,7 @@ igt_main
 			igt_fork_hang_detector(fd);
 		}
 
+		igt_describe("Basic test to check busyness of each engine.");
 		igt_subtest_with_dynamic("busy") {
 			igt_dynamic("all") {
 				gem_quiescent_gpu(fd);
@@ -461,6 +462,8 @@ igt_main
 			}
 		}
 
+		igt_describe("Test to check race condition by randomly closing "
+			     "the handle using gem_close.");
 		igt_subtest("close-race")
 			close_race(fd, ctx);
 
@@ -482,12 +485,17 @@ igt_main
 				gem_require_mmap_device_coherent(fd);
 			}
 
+			igt_describe("Extended test to check busyness of "
+				     "dwstore-capable engines.");
 			test_each_engine_store("extended", fd, ctx, e) {
 				gem_quiescent_gpu(fd);
 				one(fd, ctx, e, 0);
 				gem_quiescent_gpu(fd);
 			}
 
+			igt_describe("Extended test to check busyness of engine "
+				     "busyness of dwstore-capable engines while "
+				     "doing parallel execution.");
 			test_each_engine_store("parallel", fd, ctx, e) {
 				gem_quiescent_gpu(fd);
 				one(fd, ctx, e, PARALLEL);
@@ -501,6 +509,9 @@ igt_main
 				igt_require(has_semaphores(fd));
 			}
 
+		igt_describe("Test to check busyness of engine on submitting "
+			     "a new batch while engine is busy in executing "
+			     "previous batch.");
 			test_each_engine("semaphore", fd, ctx, e) {
 				gem_quiescent_gpu(fd);
 				semaphore(fd, ctx, e);
@@ -520,6 +531,8 @@ igt_main
 			hang = igt_allow_hang(fd, ctx->id, 0);
 		}
 
+		igt_describe("Basic test to check hang state beahaviour of "
+			     "engine with increased timeout.");
 		test_each_engine("hang", fd, ctx, e) {
 			gem_quiescent_gpu(fd);
 			basic(fd, ctx, e, HANG);
@@ -532,6 +545,9 @@ igt_main
 				gem_require_mmap_device_coherent(fd);
 			}
 
+			igt_describe("Extended test to check hang state "
+				     "behaviour of dwstore-capable engines "
+				     " with increased timeout.");
 			test_each_engine_store("hang-extended", fd, ctx, e) {
 				gem_quiescent_gpu(fd);
 				one(fd, ctx, e, HANG);
-- 
2.25.1

  reply	other threads:[~2022-06-23 12:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 12:12 [igt-dev] [PATCH 0/2] tests/i915/gem_busy : Added subtests description sinjan.kumar
2022-06-23 12:12 ` sinjan.kumar [this message]
2022-06-23 16:02   ` [igt-dev] [PATCH 1/2] " Kamil Konieczny
2022-06-23 12:12 ` [igt-dev] [PATCH 2/2] HAX: don't do full run sinjan.kumar
2022-06-23 12:45 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/i915/gem_busy : Added subtests description Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2022-06-24  4:37 [igt-dev] [PATCH 0/2] HAX " sinjan.kumar
2022-06-24  4:37 ` [igt-dev] [PATCH 1/2] " sinjan.kumar
2022-06-24  8:43   ` Kamil Konieczny
2022-06-16  3:58 [igt-dev] [PATCH 0/2] " sinjan.kumar
2022-06-16  3:58 ` [igt-dev] [PATCH 1/2] " sinjan.kumar
2022-06-22 14:08   ` Kamil Konieczny

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=20220623121253.1352382-2-sinjan.kumar@intel.com \
    --to=sinjan.kumar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=janga.rahul.kumar@intel.com \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=priyanka.dandamudi@intel.com \
    --cc=ramadevi.gandi@intel.com \
    --cc=sai.gowtham.ch@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 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.