Loading...

Botching up IOCTLs

2,456 views

Loading...

Loading...

Transcript

The interactive transcript could not be loaded.

Loading...

Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Jan 16, 2015

Daniel Vetter
http://lca2015.linux.org.au/schedule/...
One clear insight kernel graphics hackers gained in the past few years is that trying to come up with a unified interface to manage the execution units and memory on completely different GPUs is a futile effort. So nowadays every driver has its own set of ioctls to allocate memory and submit work to the GPU. Which is nice, since there's no more insanity in the form of fake-generic, but actually only used-once interfaces. But the clear downside is that there's much more potential to screw things up.

To avoid repeating all the same mistakes again this talk will present some of the lessons learned while botching the job for the drm subsystem in general and the i915 driver specifically. Topics covered will be the bare basic to avoid needless busywork later on, reasonable minimal testing to avoid CVEs and other embarrassement. And generally a thicket of war stories to figure out what works and where's still some white spots in the userspace interface landscape.

Loading...


to add this to Watch Later

Add to

Loading playlists...