One concern I forgot to mention: Interoperability with
AMD_performance_monitor.
With this patch series as is, after glBeginPerfQueryINTEL, there will be
a value you can pass to glEndPerfMonitorAMD that won't produce
GL_INVALID_VALUE as it should. Making sure context's monitor objects are
accessible only through the extension that created them is something
that needs to be done, but I'm not sure what would be the best way.
Comments and hits welcome.
--
Petri Latvala
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev