- 29 Aug, 2013 6 commits
-
-
Chris Wilson authored
This should be no functional change as we operate on an array of crtc[1]. Later we shall test clone mode across a number of crtc. Signed-off-by:Chris Wilson <chris@chris-wilson.co.uk>
-
Chris Wilson authored
For machine with split BCS/RCS rings, we also need to test whether we correctly wait upon outstanding render work before flipping and changing modes. This should also serve to exercise the ring selection code for flips. Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by:
-
- 28 Aug, 2013 2 commits
-
-
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Since we no longer increment the counter every frame, we need to use a timestamp instead. Signed-off-by:
-
- 27 Aug, 2013 12 commits
-
-
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Having 100% always mean one processor fully utilised is much easier to understand (than having to remember how many cores are on each machine and scale appropriately). Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by:
-
- 26 Aug, 2013 10 commits
-
-
Chris Wilson authored
And use a shade of gray to distinguish from the total instead. Signed-off-by: -
Daniel Vetter authored
I didn't really want to revert those, too ... Signed-off-by:Daniel Vetter <daniel.vetter@ffwll.ch>
-
Daniel Vetter authored
This reverts commit 912a7d85. Now fixed for real! Signed-off-by:
-
Daniel Vetter authored
Longjmp creates havoc with stack variables of the current stackframe. And since fixtures should be used to set up such variables creating havoc isn't a great idea. With this I can revert a bunch of bogus patches I've done to paper over this by moving stack variables to be global. The same issue is actually a feature for subtest blocks since subtests should be independant anyway. Signed-off-by: -
Daniel Vetter authored
Currently fails since the patches aren't merged yet. Signed-off-by: -
Daniel Vetter authored
I wanted to write a testcase for gtt mmap access restriction checking and only noticed after conversion to subtests that this here is for cpu mmaps ;-) Signed-off-by: -
Imre Deak authored
Signed-off-by:Imre Deak <imre.deak@intel.com>
-
Imre Deak authored
So far we handled -h or --help arguments properly only if the test called igt_subtest_init_parse_opts(). Fix this for igt_subtest_init() callers too. Make sure we still don't exit for any other unknown options, which the caller may parse with a second getopt scan. Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
This required me to contract the per-process information considerably, hopefully readability is not sacrificed too much. Signed-off-by:
-
- 25 Aug, 2013 7 commits
-
-
Chris Wilson authored
Using window.size=<width>x<height> or window.size=<scale>% in the config file, or --size=<scale>% or --size=<width>x<height> Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
For when you don't have any display server, use brute force. Signed-off-by: -
Chris Wilson authored
By drawing it behind the waits, it is obscured by the translucent waits. Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by:
-
- 23 Aug, 2013 3 commits
-
-
Daniel Vetter authored
Also I've stumbled over igt_fixture again. Somehow gcc loves to wreak havoc with stack variables set up in igt_fixtures ... Duct-tape in the form of moving fd out to global scope applied. Signed-off-by: -
Chris Wilson authored
Signed-off-by: -
Chris Wilson authored
Signed-off-by:
-
