summaryrefslogtreecommitdiff
path: root/lib/igt_kmod.c
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2017-11-13 10:51:28 +0000
committerChris Wilson <chris@chris-wilson.co.uk>2017-11-16 11:56:11 +0000
commit405ae11df35c883df446e7e2539d2df0c9c19a1e (patch)
tree36728b84b42e893df3aeab10e74dd2f4f3bec30a /lib/igt_kmod.c
parent3a243cb110462dbec2f9f1e3299e425b39d790c6 (diff)
lib/kmod: Stop reloading i915 after every kselftest
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@chris-wilson.co.uk> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
Diffstat (limited to 'lib/igt_kmod.c')
-rw-r--r--lib/igt_kmod.c3
1 files changed, 0 insertions, 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)