Re: [Mesa-dev] GL_ARB_debug_output from drivers

2013-02-25 Thread Ian Romanick
On 02/22/2013 07:52 PM, Eric Anholt wrote: One of the features Valve asked for, that they expected after using other drivers, is that they can easily get information about performance traps (and other important stuff) from drivers. We wrote INTEL_DEBUG=perf this summer as a quick fix, but it's n

Re: [Mesa-dev] GL_ARB_debug_output from drivers

2013-02-23 Thread Jordan Justen
Series Reviewed-by: Jordan Justen On Fri, Feb 22, 2013 at 7:52 PM, Eric Anholt wrote: > One of the features Valve asked for, that they expected after using other > drivers, is that they can easily get information about performance traps > (and other important stuff) from drivers. We wrote INTEL

Re: [Mesa-dev] GL_ARB_debug_output from drivers

2013-02-23 Thread Jose Fonseca
- Original Message - > One of the features Valve asked for, that they expected after using other > drivers, is that they can easily get information about performance traps > (and other important stuff) from drivers. We wrote INTEL_DEBUG=perf this > summer as a quick fix, but it's not how

[Mesa-dev] GL_ARB_debug_output from drivers

2013-02-22 Thread Eric Anholt
One of the features Valve asked for, that they expected after using other drivers, is that they can easily get information about performance traps (and other important stuff) from drivers. We wrote INTEL_DEBUG=perf this summer as a quick fix, but it's not how most drivers integrate this sort of fe