9 Commits

Author SHA1 Message Date
Daniel Vetter
a35dcac0ff tests/gem_wait_rendering_timeout: check polling behaviour
... with timeout=0. We have special code in the kernel to optimize
that one.
2012-05-30 20:16:24 +02:00
Daniel Vetter
b8e00110a0 lib/gem_wait_rendering_timeout: sprinkle busy_ioctl checks
While we have that testcase, let's cross-check the busy ioctl.
2012-05-29 22:23:14 +02:00
Daniel Vetter
04dfa492d1 tests/gem_wait_rendering_timeout: test the timeout case
When I've first tried this it somehow failed, but I can't reproduce
this any more. I guess I've hunted a ghost.
2012-05-29 17:35:21 +02:00
Daniel Vetter
b711bfe54f tests/gem_wait_rendering_timeout: fix up the autotuner
duuh
2012-05-29 16:49:41 +02:00
Daniel Vetter
2952feb23f tests/get_wait_rendering_timeout: fixup the auto-tuner
- start at 1 iterations
- actually adjust the number of iterations like the comment claims
2012-05-29 16:35:30 +02:00
Daniel Vetter
cf979c2063 tests/gem_wait_rendering_timeout: some fixes for the blt function
- widht/height are in pixel, and the cmd uses 32bit, so we need to
  adjust this.
- we write to the buffer, set the right reloc domain.
2012-05-29 16:34:32 +02:00
Daniel Vetter
25bf5574a2 tests/gem_wait_rendering_timeout: properly skip test
also assign the timeout value unconditionally, we want to know it even
when we've timeout out.
2012-05-29 16:24:04 +02:00
Daniel Vetter
f14a045137 tests/gem_wait_rendering_timeout: make it compile
... we need to do this libdrm depency dance. Or just copy&paste it.
2012-05-29 16:14:31 +02:00
Ben Widawsky
9cfcb75b79 tests/wait render timeout test
Assures that signals interrupting the wait works properly. Because of
the scheduling around signals, interrupted waits will *seem* faster as
the GPU continues to work while all the CPU scheduling stuff happens.

Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
2012-05-25 13:08:28 +02:00