August 21, 2018
As we all know, OpenGL is an aging API which originated in the 1990s. Despite that, it uses modular structure, allowing new features to be added via extensions. An extremely useful approach, proven to be robust and used by many other APIs - OpenCL and Vulkan are the more well known.
Although, OpenGL in itself is the rendering API, the windowing system binding APIs such as GLX, WGL and EGL, are showing their age as well. An era where multi GPU systems were extremely uncommon and even harder to find.
Fast-forward to present days: dual GPU systems are becoming the norm, with platforms using 16 or even 32 not being unheard of.
So how did the API evolve, how do we handle multi GPUs installed on the same system? Solutions vary across vendors, but in Mesa we have
DRI_PRIME is an environment variable, initially introduced to work with two GPUs. By setting it to 1 prior to calling their application, the GL stack will query the X server and use the "other" GPU present on the system.
That was a good initial solution, although it brought a number of questions:
With the first question being more urgent, the community came with a solution: Allow the user to select the device by listing the device
ID_PATH_TAG, as provided by udev, in
With that ticked off, how do we handle the other two? Thanks to the extendable structure of EGL, we can accomplish that with the EGLDevice family of extensions.
They define the concept of EGLDevice, the means of enumerating and querying device specific attributes. Another two extensions
EGL_MESA_device_software define respectively hardware devices, backed with a DRM device node and software devices - as available in Mesa, but not many other GL implementations.
EGL_EXT_platform_device, defines a way of using an EGLDevice, yet without an explicit awareness of the underlying windowing system.
Which means that we can create a context, although we cannot test and analyse the interactions with the Android, Wayland compositor or X11 that's underneath. To address that,
EGL_EXT_explicit_device was proposed - allowing us to select, simultaneously, the device and the platform to be used.
As pointed earlier, the set of extensions allows us to explicitly select which device we want to use.
Hence, the use-cases are only limited to one's imagination. Here are a few that come to mind:
My personal interest is testing and development. We could easily have a single system with multiple GPUs instead of one system per GPU. That will make it easier for driver developers to test across different devices, improving the process and robustness of the drivers.
As part of the process, I have provided patches for Mesa and the Piglit testing suite. They cover the following extensions:
At the time of writing, the Piglit patches have been merged, while the Mesa ones are on the mailing list awaiting review.
EGL_EXT_device_base- implementing both
In my testing, they have proved to be in fairly good shape, although further testing and review is needed.
While the extension EGL_MESA_device_software is in good shape, we are planning to follow the official Khronos process and ratify it. Additionally, a few questions were raised in the
EGL_EXT_explicit_device spec, which will need to be resolved and Mesa implementation will be required.
While that covers most issues, one corner-case remains - how can one do the same with X? GLX does not have such a set of extensions. Our goals is to draft and bring them forward to Khronos. Thus projects which aim to simplify all the platform specifics for you, such as Waffle and SDL, they will have a consistent way of handling device selection.
Which brings us to the final piece. We are planning to design and implement a user-friendly API for Waffle, that makes use of the extensions.
I'll be giving a talk about this and the Mesa releasing this September at XDC 2018 in A Coruña, Spain. A dozen Collaborans will be in attendance as well, so please come say hello!
If you have a device with a Mali T720 or T820 GPU, you’re in luck – your device is now supported in upstream Mesa at feature parity with…
PipeWire, the new and emerging open source framework that aims to greatly improve the exchange and management of audio and video streams…
With the advent of meson and gst-build, it is now possible to set up a GStreamer Windows development environment that rivals the finest…
I recently went to XDC 2019, where I gave yet another talk about Zink. I kinda forgot to write a blog-post about it, so here’s me trying…
Prior to joining Collabora, I took part in Round 17 of the Outreachy internships, to work on the virtual drivers in the media subsystem…
What HDCP is, and why supporting HDCP in Weston is justified in both an economical and technical context.