To ensure the module exists, first load it. Then when we try to unload
the module (to check that our modprobe interface works), we will not get
spurious failures due to -ENOENT (in this case meaning the module did
not exist):
(vgem_basic:18361) igt-core-DEBUG: Starting subtest: unload
(vgem_basic:18361) igt-kmod-DEBUG: Could not remove module vgem (No such file
or directory)
Test requirement not met in function test_unload, file vgem_basic.c:331:
Test requirement: module_unload() == 0
Last errno: 2, No such file or directory
Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk>
---
tests/vgem_basic.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/vgem_basic.c b/tests/vgem_basic.c
index 982da73a..cfd94071 100644
--- a/tests/vgem_basic.c
+++ b/tests/vgem_basic.c
@@ -328,6 +328,9 @@ static void test_unload(void)
int vgem, dmabuf;
uint32_t *ptr;
+ /* Load and unload vgem just to make sure it exists */
+ vgem = __drm_open_driver(DRIVER_VGEM);
+ igt_require(vgem != -1);
igt_require(module_unload() == 0);
vgem = __drm_open_driver(DRIVER_VGEM);
--
2.14.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
