[PATCH] Implement support for GPU timings of calls when proofiling with glretrace.
Carl Worth
cworth at cworth.org
Wed Aug 1 18:39:28 PDT 2012
Eric Anholt <eric at anholt.net> writes:
> The issue I have right now with trying to do performance debug through
> apitrace is I can't easily assign blame between the VS and FS of the
> shader program that's taking all the GPU time.
...
> trying to go into the trace and whack the FS source to just be
> gl_FragData[0] = vec4(0, 1, 0, 0) (and updating the length argument in
> the API call -- would be nice for that to be automatic).
How about a mode for glretrace that replies twice, once with the FS
source whacked as above. And then a script to appropriately combine the
results of both runs.
That should be easy to implement and avoids any of the difficulties with
creating edited trace files.
I'll plan to do that in the morning.
-Carl (trying to announce plans in advance to avoid duplication of effort)
--
carl.d.worth at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/apitrace/attachments/20120801/28396c48/attachment.pgp>
More information about the apitrace
mailing list