[PATCH igt 2/2] lib/kmod: Stop reloading i915 after every kselftest

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Since CI runs each subtest individually, we do not get the batching of
tests and execute every fixture around each subtest. The consequence of
this for CI is that we quickly exhaust static allocations like lockdep's
array of lockclasses, or causing hash conflicts with new locks being
reallocation into existing addresses, the result is a warning from
lockdep and ts disabling.

Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
---
 lib/igt_kmod.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/lib/igt_kmod.c b/lib/igt_kmod.c
index f468a4da..bc1ace23 100644
--- a/lib/igt_kmod.c
+++ b/lib/igt_kmod.c
@@ -519,9 +519,6 @@ void igt_kselftest_end(struct igt_kselftest *tst)
 {
 	kmod_module_remove_module(tst->kmod, KMOD_REMOVE_FORCE);
 	close(tst->kmsg);
-
-	if (strcmp(tst->module_name, "i915") == 0)
-		igt_i915_driver_load(NULL);
 }
 
 void igt_kselftest_fini(struct igt_kselftest *tst)
-- 
2.15.0

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




[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux