1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Wiring Up GL_ARB_debug_output For Valve

Valve

Published on 23 February 2013 10:58 AM EST
Written by Michael Larabel in Valve
3 Comments

One of the requests that Valve has long had for Intel and the open-source Linux graphics drivers in general has been supporting GL_ARB_debug_output, an OpenGL extension that assists game/application developers in debugging and optimizing their code. Fortunately, support for this extension is finally being pursued aggressively within Mesa.

The request by Valve for a better GL_ARB_debug_output implementation for Mesa dates back to last July.

Following Intel and Valve collaborating about Linux GPU drivers, Intel made some driver hacks to expose some debugging/performance information hidden behind an environment variable but didn't toy around with the GL_ARB_debug_output extension. Intel's Eric Anholt is now finally getting to properly supporting this OpenGL debug extension.

Per the Khronos specification on GL_ARB_debug_output, here's some of the important parts:
This extension allows the GL to notify applications when various events occur that may be useful during application development and debugging.
...
These events are represented in the form of enumerable messages with a human-readable string representation. Examples of debug events include incorrect use of the GL, warnings of undefined behavior, and performance warnings.
...
The type of the message roughly identifies the nature of the event that caused the message. Examples include errors, performance warnings, or warnings about undefined behavior.
...
Each message is also assigned to a severity level that denotes roughly how "important" that message is in comparison to other messages across all sources and types. For example, notification of a GL error would likely have a higher severity than a performance warning due to redundant state changes.
...
Messages are communicated to the application through an application- defined callback function that is called by the GL implementation on each debug message. The motivation for the callback routine is to free application developers from actively having to query whether a GL error, or any other debuggable event has happened after each call to a GL function. With a callback, developers can keep their code free of debug checks, and only have to react to messages as they occur. In situations where using a callback is not possible, a message log is also provided that stores copies of recent messages until they are actively queried. To control the volume of debug output, messages can be disabled either individually by ID, or entire groups of messages can be turned off based on combination of source and type.
Anholt shared on Friday evening that he has an initial GL_ARB_debug_output implementation for Mesa. Right now this work consists of fourteen patches against core Mesa.

Among the items hooked into reporting for this debug output extension is the Intel WARN_ONCE macro and the perf_debug() function (formerly the fallback_debug() function), which means any of the previously exposed Intel driver performance information is now reported to this new extension. There was also extra checks added for stalling on mapping a buffer object and shader errors and warnings.

With this work coming from Intel's Open-Source Technology Center, obviously it was designed and hooked up primarily for the i965 DRI driver (though the infrastructure and core functionality in Mesa itself) but other Mesa/Gallium3D drivers will be able to build their support atop these patches. The patch series begins here on the mailing list.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. Btrfs On 4 x Intel SSDs In RAID 0/1/5/6/10
  2. AMD Radeon R9 290 On Ubuntu 14.10: RadeonSI Gallium3D vs. Catalyst
  3. MSI X99S SLI PLUS On Linux
  4. NVIDIA GeForce GTX 970 Offers Great Linux Performance
Latest Linux Articles
  1. Windows 8.1 vs. Ubuntu 14.10 With Intel HD Graphics
  2. 6-Way Ubuntu 14.10 Radeon Gallium3D vs. Catalyst Driver Comparison
  3. NVIDIA vs. Nouveau Drivers On Ubuntu 14.10
  4. Ubuntu 14.10 Offers AMD Radeon Driver Performance Improvements
Latest Linux News
  1. Wine 1.7.30 Continues Work On DirectWrite & Offers Regedit Fixes
  2. Has The Sky Fallen? Qualcomm Contributes To Freedreno's DRM/KMS Driver
  3. Manjaro Works To Make Calamares A Distribution-Independent Installer
  4. DisplayLink USB 3.0 Support Sounds Like A Mess
  5. PulseAudio Gains A Native Bluetooth Headset Backend
  6. X.Org Foundation Decides On Its Women Outreach Project
  7. GTK+ 3.16's New GtkGLArea Widget Gets Improved
  8. X.Org Server 1.17 ABI Bumped
  9. Fedora 21 Beta To Be Released Next Week
  10. Go 1.4 Beta Release Brings Big Runtime Changes
Latest Forum Discussions
  1. Closed source to opensource
  2. How to get rid of Linux
  3. Is foolish currently develop in machine code, hexadecimal and assembly?
  4. Reducing The CPU Usage In Mesa To Improve Performance
  5. Help diagnosing problems with a Readon HD 4670 on Mesa 10.3.2-1
  6. Advertisements On Phoronix
  7. nv and xorg.conf under Debian PPC
  8. Looking for a Open-Source AMD experienced Linux mentor