Re: [PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-06-09 Thread kernel test robot
Hi Jason, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on tegra-drm/drm/tegra/for-next] [cannot apply to drm-tip/drm-tip linus/master v5.19-rc1 next-20220609] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we

Re: [PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-06-08 Thread kernel test robot
Hi Jason, Thank you for the patch! Yet something to improve: [auto build test ERROR on tegra-drm/drm/tegra/for-next] [cannot apply to drm-tip/drm-tip linus/master v5.19-rc1 next-20220608] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we

Re: [PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-06-08 Thread kernel test robot
Hi Jason, Thank you for the patch! Yet something to improve: [auto build test ERROR on tegra-drm/drm/tegra/for-next] [cannot apply to drm-tip/drm-tip linus/master v5.19-rc1 next-20220608] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we

Re: [PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-06-08 Thread Simon Ser
Both patches pushed to drm-misc-next, thanks for your contribution!

[PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-06-08 Thread Jason Ekstrand
Modern userspace APIs like Vulkan are built on an explicit synchronization model. This doesn't always play nicely with the implicit synchronization used in the kernel and assumed by X11 and Wayland. The client -> compositor half of the synchronization isn't too bad, at least on intel, because we

Re: [PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-05-26 Thread Jason Ekstrand
On Wed, May 25, 2022 at 8:20 AM Daniel Vetter wrote: > On Mon, May 09, 2022 at 07:54:19AM +0200, Christian König wrote: > > Reviewed-by: Christian König for the series. > > > > I assume you have the userspace part ready as well? If yes let's push > this > > to drm-misc-next asap. > > Hopefully

Re: [PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-05-26 Thread Jason Ekstrand
On Wed, May 25, 2022 at 10:43 AM Daniel Vetter wrote: > On Wed, May 25, 2022 at 10:35:47AM -0500, Jason Ekstrand wrote: > > On Wed, May 25, 2022 at 8:20 AM Daniel Vetter wrote: > > > > > On Mon, May 09, 2022 at 07:54:19AM +0200, Christian König wrote: > > > > Reviewed-by: Christian König for

Re: [PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-05-25 Thread Daniel Vetter
On Wed, May 25, 2022 at 10:35:47AM -0500, Jason Ekstrand wrote: > On Wed, May 25, 2022 at 8:20 AM Daniel Vetter wrote: > > > On Mon, May 09, 2022 at 07:54:19AM +0200, Christian König wrote: > > > Reviewed-by: Christian König for the series. > > > > > > I assume you have the userspace part ready

Re: [PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-05-25 Thread Daniel Vetter
On Mon, May 09, 2022 at 07:54:19AM +0200, Christian König wrote: > Reviewed-by: Christian König for the series. > > I assume you have the userspace part ready as well? If yes let's push this > to drm-misc-next asap. Hopefully I'm not too late, but I think all my review has also been addressed.

Re: [PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-05-08 Thread Christian König
Reviewed-by: Christian König for the series. I assume you have the userspace part ready as well? If yes let's push this to drm-misc-next asap. Christian. Am 06.05.22 um 20:02 schrieb Jason Ekstrand: Modern userspace APIs like Vulkan are built on an explicit synchronization model. This

[PATCH 1/2] dma-buf: Add an API for exporting sync files (v14)

2022-05-07 Thread Jason Ekstrand
Modern userspace APIs like Vulkan are built on an explicit synchronization model. This doesn't always play nicely with the implicit synchronization used in the kernel and assumed by X11 and Wayland. The client -> compositor half of the synchronization isn't too bad, at least on intel, because we