mmio-debugging is lazy, we only turn on per-access checking after
a periodic check to see if an error has been flagged. If we load the
module with mmio_debug, we can validate that no such errors occur during
module_init, which is one of the trickier times to get right (having to
balance sanitization of existing HW state with our own).
Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
---
tests/drv_module_reload.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/drv_module_reload.c b/tests/drv_module_reload.c
index 3046d8227..092982960 100644
--- a/tests/drv_module_reload.c
+++ b/tests/drv_module_reload.c
@@ -316,6 +316,9 @@ igt_main
gem_exec_store();
}
+ igt_subtest("basic-mmio-debug")
+ igt_assert_eq(reload("mmio_debug=2147483647"), 0);
+
igt_subtest("basic-no-display")
igt_assert_eq(reload("disable_display=1"), 0);
--
2.15.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
