Re: [PATCH 5/5] drm/amdgpu: rework dma_resv handling v2

2021-06-11 Thread Christian König
Am 11.06.21 um 16:56 schrieb Daniel Vetter: On Fri, Jun 11, 2021 at 02:03:01PM +0200, Christian König wrote: Drop the workaround and instead implement a better solution. Basically we are now chaining all submissions using a dma_fence_chain container and adding them as exclusive fence to the dma

Re: [PATCH 5/5] drm/amdgpu: rework dma_resv handling v2

2021-06-11 Thread Daniel Vetter
On Fri, Jun 11, 2021 at 02:03:01PM +0200, Christian König wrote: > Drop the workaround and instead implement a better solution. > > Basically we are now chaining all submissions using a dma_fence_chain > container and adding them as exclusive fence to the dma_resv object. > > This way other drive

[PATCH 5/5] drm/amdgpu: rework dma_resv handling v2

2021-06-11 Thread Christian König
Drop the workaround and instead implement a better solution. Basically we are now chaining all submissions using a dma_fence_chain container and adding them as exclusive fence to the dma_resv object. This way other drivers can still sync to the single exclusive fence while amdgpu only sync to fen