public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Andi Shyti via igt-dev <igt-dev@lists.freedesktop.org>
To: IGT dev <igt-dev@lists.freedesktop.org>
Cc: Petri Latvala <petri.latvala@intel.com>, Andi Shyti <andi@etezian.org>
Subject: [igt-dev] [RFC PATCH v7 5/5] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test
Date: Tue, 12 Feb 2019 01:08:11 +0200	[thread overview]
Message-ID: <20190211230811.24955-6-andi.shyti@intel.com> (raw)
In-Reply-To: <20190211230811.24955-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 | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/tests/i915/gem_exec_basic.c b/tests/i915/gem_exec_basic.c
index dcb83864b1c1..17fc04ec15f3 100644
--- a/tests/i915/gem_exec_basic.c
+++ b/tests/i915/gem_exec_basic.c
@@ -135,6 +135,21 @@ 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;
+
+		igt_require_gem_engine_list(fd);
+		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

  parent reply	other threads:[~2019-02-11 23:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 23:08 [igt-dev] [RFC PATCH v7 0/5] new engine discovery interface Andi Shyti via igt-dev
2019-02-11 23:08 ` [igt-dev] [RFC PATCH v7 1/5] include/drm-uapi: import i915_drm.h header file Andi Shyti via igt-dev
2019-02-11 23:08 ` [igt-dev] [RFC PATCH v7 2/5] lib: implement new engine discovery interface Andi Shyti via igt-dev
2019-02-11 23:15   ` Chris Wilson
2019-02-11 23:08 ` [igt-dev] [RFC PATCH v7 3/5] lib: ioctl_wrappers: check GET/SETPARAM ioctl and build active engine list Andi Shyti via igt-dev
2019-02-11 23:16   ` Chris Wilson
2019-02-12  9:07     ` Andi Shyti via igt-dev
2019-02-11 23:08 ` [igt-dev] [RFC PATCH v7 4/5] lib: ioctl_wrappers: reach engines by index as well Andi Shyti via igt-dev
2019-02-11 23:08 ` Andi Shyti via igt-dev [this message]
2019-02-11 23:48 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [RFC,v7,1/5] include/drm-uapi: import i915_drm.h header file 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=20190211230811.24955-6-andi.shyti@intel.com \
    --to=igt-dev@lists.freedesktop.org \
    --cc=andi.shyti@intel.com \
    --cc=andi@etezian.org \
    --cc=petri.latvala@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