diff options
| author | Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> | 2022-08-02 23:19:12 +0200 |
|---|---|---|
| committer | Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> | 2022-08-18 17:09:12 +0200 |
| commit | c00695ae7f11e7e2b159bde85e43d4a04d0f44cb (patch) | |
| tree | 627f61efd8a2734db38a1b47e36747d35285e1b9 | |
| parent | 03706cd84099c02570b18fc6e01837bd6f96ea14 (diff) | |
tests/gem_exec_fence: Fix wrong engine checked for store_dword capability
Commit ed7c8cfb67e3 ("tests/i915/gem_exec_fence: Add
__for_each_physical_engine to utilize all engines."), while replacing
depraciated for_each_physical_engine(e, fd) loop with
__for_each_physical_engine(fd, e2) and gem_can_store_dword() inside that
loop with gem_class_can_store_dword(), didn't switch to e2 consequently --
eb_ring(e) argument of gem_can_store_dword() was replaced with e->class
passed to gem_class_can_store_dword() instead of e2->class. As a result,
a batch that stores dword is now submitted to all engines, also those that
don't support that operation. Fix it.
Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>
| -rw-r--r-- | tests/i915/gem_exec_fence.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/i915/gem_exec_fence.c b/tests/i915/gem_exec_fence.c index 7ff7614da..048870053 100644 --- a/tests/i915/gem_exec_fence.c +++ b/tests/i915/gem_exec_fence.c @@ -331,7 +331,7 @@ static void test_fence_await(int fd, const intel_ctx_t *ctx, i = 0; for_each_ctx_engine(fd, ctx, e2) { - if (!gem_class_can_store_dword(fd, e->class)) + if (!gem_class_can_store_dword(fd, e2->class)) continue; if (flags & NONBLOCK) { |