From: Nirmoy Das <nirmoy.das@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: andi.shyti@intel.com, oak.zeng@intel.com,
Nirmoy Das <nirmoy.das@intel.com>
Subject: [igt-dev] [PATCH i-g-t 2/4] tests/intel/gem_ctx_shared: Skip some test on MTL
Date: Mon, 18 Sep 2023 18:47:45 +0200 [thread overview]
Message-ID: <20230918164747.30171-3-nirmoy.das@intel.com> (raw)
In-Reply-To: <20230918164747.30171-1-nirmoy.das@intel.com>
We do GGTT update on MTL using bcs engine, blocking that would
fail the test so skip such subtests on bcs engine for MTL.
Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
---
tests/intel/gem_ctx_shared.c | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/tests/intel/gem_ctx_shared.c b/tests/intel/gem_ctx_shared.c
index d24ae5483..fd429306e 100644
--- a/tests/intel/gem_ctx_shared.c
+++ b/tests/intel/gem_ctx_shared.c
@@ -1047,6 +1047,12 @@ static void smoketest(int i915, const intel_ctx_cfg_t *cfg,
for_each_if(gem_class_can_store_dword(i915, (e)->class)) \
igt_dynamic_f("%s", e->name)
+#define for_each_nonblocking_ggtt_binder_queue(e, i915, cfg) \
+ for_each_ctx_cfg_engine(i915, cfg, e) \
+ for_each_if(gem_class_can_store_dword(i915, (e)->class) && \
+ !gem_engine_can_block_ggtt_binder(i915, e)) \
+ igt_dynamic_f("%s", e->name)
+
igt_main
{
const struct intel_execution_engine2 *e;
@@ -1104,22 +1110,22 @@ igt_main
}
igt_subtest_with_dynamic("Q-independent") {
- for_each_queue(e, i915, &cfg)
+ for_each_nonblocking_ggtt_binder_queue(e, i915, &cfg)
independent(i915, &cfg, e, 0);
}
igt_subtest_with_dynamic("Q-in-order") {
- for_each_queue(e, i915, &cfg)
+ for_each_nonblocking_ggtt_binder_queue(e, i915, &cfg)
reorder(i915, &cfg, e->flags, EQUAL);
}
igt_subtest_with_dynamic("Q-out-order") {
- for_each_queue(e, i915, &cfg)
+ for_each_nonblocking_ggtt_binder_queue(e, i915, &cfg)
reorder(i915, &cfg, e->flags, 0);
}
igt_subtest_with_dynamic("Q-promotion") {
- for_each_queue(e, i915, &cfg)
+ for_each_nonblocking_ggtt_binder_queue(e, i915, &cfg)
promotion(i915, &cfg, e->flags);
}
}
--
2.41.0
next prev parent reply other threads:[~2023-09-18 16:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 16:47 [igt-dev] [PATCH i-g-t 0/4] Ignore some tests on MTL which Nirmoy Das
2023-09-18 16:47 ` [igt-dev] [PATCH i-g-t 1/4] lib/igt_gt: Add gem_engine_can_block_ggtt_binder Nirmoy Das
2023-09-18 16:47 ` Nirmoy Das [this message]
2023-09-18 16:47 ` [igt-dev] [PATCH i-g-t 3/4] tests/intel/gem_ctx_schedule: Skip some test on MTL Nirmoy Das
2023-09-18 17:00 ` Nirmoy Das
2023-09-19 10:20 ` Kamil Konieczny
2023-09-19 14:17 ` Nirmoy Das
2023-09-20 7:54 ` Kamil Konieczny
2023-09-18 16:47 ` [igt-dev] [PATCH i-g-t 4/4] tests/intel/gem_spin_batch: " Nirmoy Das
2023-09-20 7:51 ` Kamil Konieczny
2023-09-18 21:40 ` [igt-dev] ✓ Fi.CI.BAT: success for Ignore some tests on MTL which (rev4) Patchwork
2023-09-18 22:44 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-09-20 0:17 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-22 10:29 ` Nirmoy Das
2023-09-20 8:57 ` [igt-dev] [PATCH i-g-t 0/4] Ignore some tests on MTL which Andi Shyti
2023-09-22 11:25 ` [igt-dev] ✗ Fi.CI.BAT: failure for Ignore some tests on MTL which (rev5) 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=20230918164747.30171-3-nirmoy.das@intel.com \
--to=nirmoy.das@intel.com \
--cc=andi.shyti@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=oak.zeng@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