[PATCH] Implement support for GPU timings of calls when proofiling with glretrace.

[James Benton]

On 01/08/12 01:26, Carl Worth wrote:
> José Fonseca <jose.r.fonseca at gmail.com> writes:
>> - it keeps.a ceiling on maximum number on queries open
> This part had me scratching my head for a bit, but I think I understand
> it now.
>
> The first patch in that series does a rather simple-minded thing of
> blocking on every frame until all the results are in. And that's
> obviously not interesting.
>
> The commit with the "maximum number of queries" instead queues up this
> number of queries and then starts harvesting results, (potentially
> blocking depending on the hard-coded limit and on how much activity the
> application has outstanding).
>
> My series instead queues up results without any hard-coded limit. What
> it does is simply harvest all available results at the end of every
> frame. So it never blocks to collect results. I think this is preferred.
>
>
> -Carl

We were experiencing erroneous results with a 3dmark06 test when using 
retrace and I found limiting the active queries fixed the problem.

However, I just tested again and this turned out not to be the issue.

It was actually due to how context switches worked, I just committed a 
patch to remove this arbitrary limit and it is now fully asynchronous again.

James