All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Subject: [Intel-gfx] [PATCH i-g-t] drm_import_export: Check for working and known GPU
Date: Sat, 25 Jul 2020 09:54:24 +0100	[thread overview]
Message-ID: <20200725085424.523604-1-chris@chris-wilson.co.uk> (raw)

Since this relies on libdrm being updated for new GPUs [spoiler
warning], just mark future failures with a skip until support lands.

References: https://gitlab.freedesktop.org/drm/intel/-/issues/2220
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
 tests/drm_import_export.c | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/tests/drm_import_export.c b/tests/drm_import_export.c
index 6174c9973..d8ae84b32 100644
--- a/tests/drm_import_export.c
+++ b/tests/drm_import_export.c
@@ -40,6 +40,8 @@
 #include <unistd.h>
 #include <sys/syscall.h>
 
+#include "i915/gem.h"
+
 #define DURATION 10
 
 int fd;
@@ -235,13 +237,14 @@ igt_main {
 	igt_fixture {
 		fd1 = drm_open_driver(DRIVER_INTEL);
 		igt_assert(fd1 >= 0);
+		igt_require_gem(fd1);
+
 		bufmgr1 = drm_intel_bufmgr_gem_init(fd1, 8 *1024);
-		igt_assert(bufmgr1);
+		igt_require(bufmgr1);
 
 		drm_intel_bufmgr_gem_enable_reuse(bufmgr1);
 
-		fd = drm_open_driver(DRIVER_INTEL);
-		igt_assert(fd >= 0);
+		fd = gem_reopen_driver(fd1);
 		bufmgr = drm_intel_bufmgr_gem_init(fd, 8 *1024);
 		igt_assert(bufmgr);
 
-- 
2.28.0.rc1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

                 reply	other threads:[~2020-07-25  8:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200725085424.523604-1-chris@chris-wilson.co.uk \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.