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 3/5] lib: ioctl_wrappers: check GET/SETPARAM ioctl and build active engine list
Date: Tue, 12 Feb 2019 01:08:09 +0200 [thread overview]
Message-ID: <20190211230811.24955-4-andi.shyti@intel.com> (raw)
In-Reply-To: <20190211230811.24955-1-andi.shyti@intel.com>
The igt_require_gem_engine_list() is called whenever the test
wants to use the GET/SETPARAM ioctls.
The function checks whether the GET/SETPARAM are implemented in
the running kernel and stops the test in case these commands are
not supported.
At the first call it creates the current engine list as
implemented in the gem_init_engine_list() function.
Signed-off-by: Andi Shyti <andi.shyti@intel.com>
---
lib/ioctl_wrappers.c | 7 +++++++
lib/ioctl_wrappers.h | 1 +
2 files changed, 8 insertions(+)
diff --git a/lib/ioctl_wrappers.c b/lib/ioctl_wrappers.c
index 404c2fbf9355..2d2a3033d961 100644
--- a/lib/ioctl_wrappers.c
+++ b/lib/ioctl_wrappers.c
@@ -53,6 +53,7 @@
#include "intel_chipset.h"
#include "intel_io.h"
#include "igt_debugfs.h"
+#include "igt_gt.h"
#include "igt_sysfs.h"
#include "config.h"
@@ -1465,6 +1466,12 @@ void igt_require_gem(int fd)
igt_require_f(err == 0, "Unresponsive i915/GEM device\n");
}
+void igt_require_gem_engine_list(int fd)
+{
+ igt_require_intel(fd);
+ igt_require(!gem_init_engine_list(fd));
+}
+
bool gem_has_ring(int fd, unsigned ring)
{
struct drm_i915_gem_execbuffer2 execbuf;
diff --git a/lib/ioctl_wrappers.h b/lib/ioctl_wrappers.h
index b22b36b0b2dd..e0b54154f5c1 100644
--- a/lib/ioctl_wrappers.h
+++ b/lib/ioctl_wrappers.h
@@ -142,6 +142,7 @@ bool gem_bo_busy(int fd, uint32_t handle);
/* feature test helpers */
void igt_require_gem(int fd);
+void igt_require_gem_engine_list(int fd);
bool gem_has_llc(int fd);
bool gem_has_bsd(int fd);
bool gem_has_blt(int 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-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 ` Andi Shyti via igt-dev [this message]
2019-02-11 23:16 ` [igt-dev] [RFC PATCH v7 3/5] lib: ioctl_wrappers: check GET/SETPARAM ioctl and build active engine list 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 ` [igt-dev] [RFC PATCH v7 5/5] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test Andi Shyti via igt-dev
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-4-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