From: Andi Shyti <andi.shyti@intel.com>
To: IGT dev <igt-dev@lists.freedesktop.org>
Cc: Andi Shyti <andi@etezian.org>
Subject: [igt-dev] [RFC PATCH v6 4/4] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test
Date: Wed, 6 Feb 2019 11:18:50 +0200 [thread overview]
Message-ID: <20190206091850.2078-5-andi.shyti@intel.com> (raw)
In-Reply-To: <20190206091850.2078-1-andi.shyti@intel.com>
The "exec-ctx" is a demo subtest inserted in the gem_exec_basic
test. The main goal of the test is to get to the engines by using
the new API as implemented in in commit 87079e04 ("lib: implement
new engine discovery interface").
The "exec-ctx" subtest simply gets the list of engines, binds
them to a context and executes a buffer. This is done through a
new "for_each_engine_ctx" loop which iterates through the
engines.
Signed-off-by: Andi Shyti <andi.shyti@intel.com>
---
tests/i915/gem_exec_basic.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/tests/i915/gem_exec_basic.c b/tests/i915/gem_exec_basic.c
index dcb83864b1c1..b68829f664db 100644
--- a/tests/i915/gem_exec_basic.c
+++ b/tests/i915/gem_exec_basic.c
@@ -135,6 +135,20 @@ igt_main
gtt(fd, e->exec_id | e->flags);
}
+ igt_subtest("exec-ctx") {
+ uint32_t ctx_id;
+ struct intel_execution_engine2 *e2;
+ int index_map = 0;
+
+ ctx_id = gem_context_create(fd);
+
+ for_each_engine_ctx(fd, ctx_id, e2)
+ igt_assert(gem_has_ring_by_idx(fd, ++index_map,
+ ctx_id));
+
+ gem_context_destroy(fd, ctx_id);
+ }
+
igt_fixture {
igt_stop_hang_detector();
close(fd);
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-06 9:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 9:18 [igt-dev] [RFC PATCH v6 0/4] new engine discovery interface Andi Shyti
2019-02-06 9:18 ` [igt-dev] [RFC PATCH v6 1/4] include/drm-uapi: import i915_drm.h header file Andi Shyti
2019-02-06 9:18 ` [igt-dev] [RFC PATCH v6 2/4] lib: implement new engine discovery interface Andi Shyti
2019-02-06 9:31 ` Chris Wilson
2019-02-08 12:55 ` Andi Shyti
2019-02-08 13:03 ` Chris Wilson
2019-02-06 18:11 ` Antonio Argenziano
2019-02-08 11:03 ` Andi Shyti
2019-02-08 11:06 ` Chris Wilson
2019-02-06 9:18 ` [igt-dev] [RFC PATCH v6 3/4] lib: ioctl_wrappers: reach engines by index as well Andi Shyti
2019-02-06 9:33 ` Chris Wilson
2019-02-06 9:18 ` Andi Shyti [this message]
2019-02-06 9:25 ` [igt-dev] ✗ Fi.CI.BAT: failure for new engine discovery interface (rev7) Patchwork
2019-02-07 8:58 ` Petri Latvala
2019-02-08 10:56 ` Andi Shyti
2019-02-12 8:43 ` Tvrtko Ursulin via igt-dev
2019-02-12 11:39 ` Arkadiusz Hiler via igt-dev
2019-02-12 11:56 ` Tvrtko Ursulin via igt-dev
2019-02-15 9:50 ` Petri Latvala via igt-dev
2019-02-25 13:22 ` Tvrtko Ursulin
2019-02-26 9:32 ` Petri Latvala
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=20190206091850.2078-5-andi.shyti@intel.com \
--to=andi.shyti@intel.com \
--cc=andi@etezian.org \
--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