From: janga.rahul.kumar@intel.com
To: igt-dev@lists.freedesktop.org, ramadevi.gandi@intel.com,
sai.gowtham.ch@intel.com
Subject: [igt-dev] [PATCH 1/2] tests/i915/gem_exec_fence : Add subtests description
Date: Wed, 29 Jun 2022 13:53:53 +0530 [thread overview]
Message-ID: <20220629082354.3907635-2-janga.rahul.kumar@intel.com> (raw)
In-Reply-To: <20220629082354.3907635-1-janga.rahul.kumar@intel.com>
From: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
Add test description for below subtests:
basic-busy-all, basic-wait-all, busy-hang-all, wait-hang-all,
basic-busy, basic-wait, basic-await, nb-await.
v2 : Modified subtests description.
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Signed-off-by: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
---
tests/i915/gem_exec_fence.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/tests/i915/gem_exec_fence.c b/tests/i915/gem_exec_fence.c
index b7ce425d..a6499a68 100644
--- a/tests/i915/gem_exec_fence.c
+++ b/tests/i915/gem_exec_fence.c
@@ -3012,8 +3012,12 @@ igt_main
igt_fork_hang_detector(i915);
}
+ igt_describe("Basic check for composite fence on all busy engines.");
igt_subtest("basic-busy-all")
test_fence_busy_all(i915, ctx, 0);
+
+ igt_describe("Basic check for composite fence with additional wait on all busy"
+ " engines.");
igt_subtest("basic-wait-all")
test_fence_busy_all(i915, ctx, WAIT);
@@ -3022,8 +3026,13 @@ igt_main
hang = igt_allow_hang(i915, ctx->id, 0);
}
+ igt_describe("Check for composite fence on all busy engines with a pending gpu"
+ " hang.");
igt_subtest("busy-hang-all")
test_fence_busy_all(i915, ctx, HANG);
+
+ igt_describe("Check for composite fence with additional wait on all busy engines"
+ " and with a pending gpu hang.");
igt_subtest("wait-hang-all")
test_fence_busy_all(i915, ctx, WAIT | HANG);
@@ -3044,24 +3053,34 @@ igt_main
intel_allocator_multiprocess_start();
}
+ igt_describe("Basic check for explicit fence on each busy engine.");
igt_subtest_with_dynamic("basic-busy") {
for_each_ctx_engine(i915, ctx, e) {
igt_dynamic_f("%s", e->name)
test_fence_busy(i915, ctx, e, 0);
}
}
+
+ igt_describe("Basic check for explicit fence with additinal wait time on"
+ " each busy engine.");
igt_subtest_with_dynamic("basic-wait") {
for_each_ctx_engine(i915, ctx, e) {
igt_dynamic_f("%s", e->name)
test_fence_busy(i915, ctx, e, WAIT);
}
}
+
+ igt_describe("Basic check for explicit fence with async wait on each"
+ " engine.");
igt_subtest_with_dynamic("basic-await") {
for_each_ctx_engine(i915, ctx, e) {
igt_dynamic_f("%s", e->name)
test_fence_await(i915, ctx, e, 0);
}
}
+
+ igt_describe("Check for explicit fence with non-blocking wait on each"
+ " engine.");
igt_subtest_with_dynamic("nb-await") {
for_each_ctx_engine(i915, ctx, e) {
igt_dynamic_f("%s", e->name)
--
2.25.1
next prev parent reply other threads:[~2022-06-29 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 8:23 [igt-dev] [PATCH 0/2] HAX add test description to gem_exec_fence janga.rahul.kumar
2022-06-29 8:23 ` janga.rahul.kumar [this message]
2022-06-29 8:37 ` [igt-dev] [PATCH 1/2] tests/i915/gem_exec_fence : Add subtests description Kamil Konieczny
2022-06-29 8:23 ` [igt-dev] [PATCH 2/2] HAX: don't do full run janga.rahul.kumar
2022-06-29 11:17 ` [igt-dev] ✗ GitLab.Pipeline: warning for HAX add test description to gem_exec_fence (rev2) Patchwork
2022-06-29 11:18 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2022-06-29 21:00 [igt-dev] [PATCH 0/2] HAX Add test description to gem_exec_fence test janga.rahul.kumar
2022-06-29 21:00 ` [igt-dev] [PATCH 1/2] tests/i915/gem_exec_fence : Add subtests description janga.rahul.kumar
2022-08-30 15:01 ` Kamil Konieczny
2022-10-06 12:20 [igt-dev] [PATCH 0/2] HAX Add test description to gem_exec_fence test janga.rahul.kumar
2022-10-06 12:20 ` [igt-dev] [PATCH 1/2] tests/i915/gem_exec_fence : Add subtests description janga.rahul.kumar
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=20220629082354.3907635-2-janga.rahul.kumar@intel.com \
--to=janga.rahul.kumar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--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.