Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Nirmoy Das <nirmoy.das@intel.com>
Subject: [igt-dev] [PATCH i-g-t] tests/intel/gem_eio: Skip stress test on BCS0 for MTL
Date: Mon,  2 Oct 2023 12:48:46 +0200	[thread overview]
Message-ID: <20231002104846.21443-1-nirmoy.das@intel.com> (raw)

We do GGTT update on MTL using bcs engine, blocking that would
fail the test so skip such subtests on bcs engine for MTL.

Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
---
 tests/intel/gem_eio.c | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/tests/intel/gem_eio.c b/tests/intel/gem_eio.c
index 6d4b8f7df..99891ad15 100644
--- a/tests/intel/gem_eio.c
+++ b/tests/intel/gem_eio.c
@@ -1111,8 +1111,16 @@ static void test_reset_stress(int fd, unsigned int flags)
 	const intel_ctx_t *ctx0 = context_create_safe(fd);
 	uint64_t ahnd = get_reloc_ahnd(fd, ctx0->id);
 
-	for_each_ring(e, fd)
+	for_each_ring(e, fd) {
+		struct intel_execution_engine2 engine;
+
+		engine = gem_eb_flags_to_engine(eb_ring(e));
+
+		if (gem_engine_can_block_ggtt_binder(fd, &engine))
+			continue;
+
 		reset_stress(fd, ahnd, ctx0, e->name, eb_ring(e), flags);
+	}
 
 	intel_ctx_destroy(fd, ctx0);
 	put_ahnd(ahnd);
-- 
2.41.0

             reply	other threads:[~2023-10-02 10:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 10:48 Nirmoy Das [this message]
2023-10-02 12:44 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/intel/gem_eio: Skip stress test on BCS0 for MTL Patchwork
2023-10-02 13:52 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-10-05 10:39 ` [igt-dev] [PATCH i-g-t] " Nirmoy Das
2023-10-05 10:54   ` Kamil Konieczny
2023-10-06  8:56     ` Nirmoy Das
2023-10-09 16:48       ` Kamil Konieczny
2023-10-05 10:46 ` Kamil Konieczny
2023-10-05 19:01 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/intel/gem_eio: Skip stress test on BCS0 for MTL (rev2) Patchwork
2023-10-05 20:12 ` [igt-dev] ✗ CI.xeBAT: " Patchwork
2023-10-06 11:36 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/intel/gem_eio: Skip stress test on BCS0 for MTL (rev3) Patchwork
2023-10-06 12:12 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-10-06 23:51 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-09 11:34 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/intel/gem_eio: Skip stress test on BCS0 for MTL (rev4) Patchwork
2023-10-09 12:11 ` [igt-dev] [PATCH i-g-t] tests/intel/gem_eio: Skip stress test on BCS0 for MTL Andrzej Hajda
2023-10-09 12:34 ` [igt-dev] ✓ CI.xeBAT: success for tests/intel/gem_eio: Skip stress test on BCS0 for MTL (rev4) Patchwork
2023-10-09 13:40 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-09 14:57   ` Nirmoy Das

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=20231002104846.21443-1-nirmoy.das@intel.com \
    --to=nirmoy.das@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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