[PATCH 2/2] tests/gem_madvise: set execbuf.batch_len before doing an execbuf

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

 



From: Brad Volkin <bradley.d.volkin@xxxxxxxxx>

The command parser's batch_len optimization causes the parser to
reject this batch as not having an MI_BATCH_BUFFER_END because
the length was not set correctly.

Signed-off-by: Brad Volkin <bradley.d.volkin@xxxxxxxxx>
---
 tests/gem_madvise.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/gem_madvise.c b/tests/gem_madvise.c
index 04a82aa..f95fbda 100644
--- a/tests/gem_madvise.c
+++ b/tests/gem_madvise.c
@@ -131,6 +131,7 @@ dontneed_before_exec(void)
 
 	execbuf.buffers_ptr = (uintptr_t)&exec;
 	execbuf.buffer_count = 1;
+	execbuf.batch_len = sizeof(buf);
 	gem_execbuf(fd, &execbuf);
 
 	gem_close(fd, exec.handle);
-- 
1.9.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://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