6 Commits

Author	SHA1	Message	Date
Daniel Vetter	021909e10d	tests: dont polute stderr if the test succeeds/skips ... 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-11-28 11:08:37 +01:00
Chris Wilson	aaa460951d	gem_cpu_reloc: Do another pass explicitly moving to the CPU write domain ... Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>	2012-10-02 21:40:46 +01:00
Chris Wilson	99a0824669	gem_cpu_reloc: Use the mappable aperture size! ... Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>	2012-10-02 21:05:29 +01:00
Chris Wilson	217511012a	gem_cpu_reloc: And run the test in reverse to check with already bound batches ... Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>	2012-10-02 21:05:29 +01:00
Chris Wilson	8b2c19da0b	gem_cpu_reloc: Fix for running on SNB+ ... I work with these everyday and I still made a basic mistake. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>	2012-10-02 21:05:29 +01:00
Chris Wilson	3b9a76d2fa	tests: Add gem_cpu_reloc ... 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>	2012-10-02 17:35:01 +01:00