DRM Synchronization Object Improvements Queued For Linux 4.14
Written by Michael Larabel in Linux Kernel on 29 August 2017 at 01:49 AM EDT. 9 Comments
Introduced in the Linux 4.13 kernel for the Direct Rendering Manager drivers was the concept of DRM synchronization objects while for Linux 4.14 this feature will be improved upon.

DRM synchronization objects (also referred to as "syncobj") are a top-level DRM object that contains a pointer to a fence, with that fence in turn updated via the command submission ioctls. Synchronization objects can be passed between objects. This work was added for supporting Vulkan external semaphores among other possible use-cases.

Now queued in DRM-Next for in turn landing with Linux 4.14 are more improvements to the DRM synchronization object code.

Landing tonight is a wait interface for allowing sync objects to be used to back Vulkan fences, with this code being based upon the AMDGPU code.

There is also now a signal ioctl, so user-space can trigger a sync object directly. This IOCTL is motivated too by Vulkan fences. Also related is a reset ioctl for this syncobj code, among some other improvements now in DRM-Next Git.
Related News
About The Author
Author picture

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter or contacted via MichaelLarabel.com.

Popular News This Week