summaryrefslogtreecommitdiff
path: root/tests/gem_cpu_reloc.c
AgeCommit message (Collapse)Author
2013-11-06tests/bdw: gem_cpu_relocBen Widawsky
support gen8 style blits Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
2013-08-13tests: s/assert/igt_assertDaniel Vetter
Just a wholesale rollout for now, we can refine later on. Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2013-08-12s/drmtest_/igt_/Daniel Vetter
Requested-by: Chris Wilson <chris@chris-wilson.co.uk> Acked-by: Damien Lespiau <damien.lespiau@intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2013-07-18tests: Instrument tests run in simulation to run quicklyDamien Lespiau
We tweak the tests marked as runnable in simulation to run more quickly, more often then not at the expense of stress testing (which is of an arguable interest for the initial bring up in simulation). Hopefully the values chosen still test something, which is not always straightforward. It does run quickly, the number on an IVB machines are: $ time sudo IGT_SIMULATION=0 ./piglit-run.py tests/igt.tests foo [...] real 2m0.141s user 0m16.365s sys 1m33.382s Vs. $ time sudo IGT_SIMULATION=1 ./piglit-run.py tests/igt.tests foo [...] real 0m0.448s user 0m0.226s sys 0m0.183s Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
2012-11-28tests: dont polute stderr if the test succeeds/skipsDaniel Vetter
Results in spurious 'warn' results in piglit. Also don't print progress indicators when not outputting to a terminal. Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-10-02gem_cpu_reloc: Do another pass explicitly moving to the CPU write domainChris Wilson
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2012-10-02gem_cpu_reloc: Use the mappable aperture size!Chris Wilson
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2012-10-02gem_cpu_reloc: And run the test in reverse to check with already bound batchesChris Wilson
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2012-10-02gem_cpu_reloc: Fix for running on SNB+Chris Wilson
I work with these everyday and I still made a basic mistake. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2012-10-02tests: Add gem_cpu_relocChris Wilson
Attempt to stress test performing relocations whilst the batch is in the CPU domain. A freshly allocated buffer starts in the CPU domain, and the pwrite should also be performed whilst in the CPU domain and so we should execute the relocations within the CPU domain. If for any reason one of those steps should land it in the GTT domain, we take the secondary precaution of filling the mappable portion of the GATT. In order to detect whether a relocation fails, we first fill a target buffer with a sequence of invalid commands that would cause the GPU to immediate hang, and then attempt to overwrite them with a legal, if short, batchbuffer using a BLT. Then we come to execute the bo, if the relocation fail and we either copy across all zeros or garbage, then the GPU will hang. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-27 03:50:12 +0000