Just to note I haven't tested yet as I don't have hsw to hand, but seems
simple enough to send out anyway...

--- >8 ---

To make it clear on failure what register was being tested the test_lri
helper now uses igt_debug to log the register address and value being
tested. The test_lri helper now also double checks that the initial
intel_register_write() takes before issuing the LRI.

Signed-off-by: Robert Bragg <rob...@sixbynine.org>
---
 tests/gem_exec_parse.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/tests/gem_exec_parse.c b/tests/gem_exec_parse.c
index cc2103a..534a933 100644
--- a/tests/gem_exec_parse.c
+++ b/tests/gem_exec_parse.c
@@ -272,8 +272,15 @@ test_lri(int fd, uint32_t handle,
                MI_BATCH_BUFFER_END,
        };
 
+       igt_debug("testing lri, reg=%x, val=%x, expected errno=%d\n",
+                 test->reg, test->test_val, expected_errno);
+
        intel_register_write(test->reg, test->init_val);
 
+       igt_assert_eq_u32((intel_register_read(test->reg) &
+                          test->read_mask),
+                         test->init_val);
+
        exec_batch(fd, handle,
                   lri, sizeof(lri),
                   I915_EXEC_RENDER,
-- 
2.10.2

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

Reply via email to