[Piglit] [PATCH] Allow one 'non-concurrent' test to run in parallel with concurrent tests again

[Michel Dänzer]

On 21.08.2014 05:42, Jason Ekstrand wrote:
> On Aug 19, 2014 8:13 PM, "Michel Dänzer" <michel at daenzer.net
> <mailto:michel at daenzer.net>> wrote:
>>
>> From: Michel Dänzer <michel.daenzer at amd.com
> <mailto:michel.daenzer at amd.com>>
>>
>> This reverts commit acb824ddc53c446124d88e37db610a4f8c59d56c.
>>
>> This decreases the runtime of the gpu.py profile from around 15 minutes to
>> around 12 minutes on my machine, with no change in results.
> 
> Do you use a compositing window manager?

I'm not. I think a compositing manager is more likely to interfere with
e.g. the sync/vblank related tests than running concurrent tests in
parallel.


> If so, then each window gets its own front buffer and you can use the
> -c option and run all the tests in parallel without problems.  If you
> are not running a compositor then there could be a problem if the
> concurrent test pops up a window on top of the non-concurrent test.
> In this case the concurrent test's window would destroy the front
> buffer of the nom-concurrent test.
> 
> This will only work if we can guarantee that the non-concurrent test
> doesn't pop up any windows.

AFAIK they don't, 'concurrent' implies using an FBO instead of a window.


-- 
Earthling Michel Dänzer            |                  http://www.amd.com
Libre software enthusiast          |                Mesa and X developer