mbox series

[v6,00/21] Move all drivers to a common dma-buf locking convention

Message ID 20220928191600.5874-1-dmitry.osipenko@collabora.com
Headers show
Series Move all drivers to a common dma-buf locking convention | expand

Message

Dmitry Osipenko Sept. 28, 2022, 7:15 p.m. UTC
Hello,

This series moves all drivers to a dynamic dma-buf locking specification.

Comments

Dmitry Osipenko Oct. 11, 2022, 5:31 p.m. UTC | #1
On 9/28/22 22:15, Dmitry Osipenko wrote:
> Hello,
> 
> This series moves all drivers to a dynamic dma-buf locking specification.
> From now on all dma-buf importers are made responsible for holding
> dma-buf's reservation lock around all operations performed over dma-bufs
> in accordance to the locking specification. This allows us to utilize
> reservation lock more broadly around kernel without fearing of a potential
> deadlocks.
> 
> This patchset passes all i915 selftests. It was also tested using VirtIO,
> Panfrost, Lima, Tegra, udmabuf, AMDGPU and Nouveau drivers. I tested cases
> of display+GPU, display+V4L and GPU+V4L dma-buf sharing (where appropriate),
> which covers majority of kernel drivers since rest of the drivers share
> same or similar code paths.

All the non-drm patches have been acked by the respective maintainers.
I'm now feeling comfortable to take this series into drm-misc-next and
going to do it later this week.

If anyone have more comments to add, then please do it now. It won't be
possible to drop out patches from drm-misc once they will be merged. All
further changes will have to be made on top of the applied patches.

Thanks to all who reviewed this patchset!