Re: [Intel-gfx] [PATCH v3] drm/amdgpu: Transfer fences to dmabuf importer

On Tue, Aug 7, 2018 at 3:54 PM, Christian König wrote: > Am 07.08.2018 um 15:37 schrieb Daniel Vetter: >> >> On Tue, Aug 07, 2018 at 03:17:06PM +0200, Christian König wrote: >>> >>> Am 07.08.2018 um 14:59 schrieb Daniel Vetter: On Tue, Aug 07, 2018 at 02:51:50PM +0200, Christian König wr

Re: [Intel-gfx] [PATCH v3] drm/amdgpu: Transfer fences to dmabuf importer

Am 07.08.2018 um 15:37 schrieb Daniel Vetter: On Tue, Aug 07, 2018 at 03:17:06PM +0200, Christian König wrote: Am 07.08.2018 um 14:59 schrieb Daniel Vetter: On Tue, Aug 07, 2018 at 02:51:50PM +0200, Christian König wrote: Am 07.08.2018 um 14:43 schrieb Daniel Vetter: On Tue, Aug 07, 2018 at 0

Re: [Intel-gfx] [PATCH v3] drm/amdgpu: Transfer fences to dmabuf importer

On Tue, Aug 07, 2018 at 03:17:06PM +0200, Christian König wrote: > Am 07.08.2018 um 14:59 schrieb Daniel Vetter: > > On Tue, Aug 07, 2018 at 02:51:50PM +0200, Christian König wrote: > > > Am 07.08.2018 um 14:43 schrieb Daniel Vetter: > > > > On Tue, Aug 07, 2018 at 01:23:19PM +0200, Christian König

Re: [Intel-gfx] [PATCH v3] drm/amdgpu: Transfer fences to dmabuf importer

Am 07.08.2018 um 14:59 schrieb Daniel Vetter: On Tue, Aug 07, 2018 at 02:51:50PM +0200, Christian König wrote: Am 07.08.2018 um 14:43 schrieb Daniel Vetter: On Tue, Aug 07, 2018 at 01:23:19PM +0200, Christian König wrote: Am 07.08.2018 um 13:05 schrieb Chris Wilson: amdgpu only uses shared-fe

Re: [Intel-gfx] [PATCH v3] drm/amdgpu: Transfer fences to dmabuf importer

On Tue, Aug 07, 2018 at 02:51:50PM +0200, Christian König wrote: > Am 07.08.2018 um 14:43 schrieb Daniel Vetter: > > On Tue, Aug 07, 2018 at 01:23:19PM +0200, Christian König wrote: > > > Am 07.08.2018 um 13:05 schrieb Chris Wilson: > > > > amdgpu only uses shared-fences internally, but dmabuf impo

Re: [Intel-gfx] [PATCH v3] drm/amdgpu: Transfer fences to dmabuf importer

Am 07.08.2018 um 14:43 schrieb Daniel Vetter: On Tue, Aug 07, 2018 at 01:23:19PM +0200, Christian König wrote: Am 07.08.2018 um 13:05 schrieb Chris Wilson: amdgpu only uses shared-fences internally, but dmabuf importers rely on implicit write hazard tracking via the reservation_object.fence_exc

Re: [Intel-gfx] [PATCH v3] drm/amdgpu: Transfer fences to dmabuf importer

On Tue, Aug 07, 2018 at 02:43:22PM +0200, Daniel Vetter wrote: > On Tue, Aug 07, 2018 at 01:23:19PM +0200, Christian König wrote: > > Am 07.08.2018 um 13:05 schrieb Chris Wilson: > > > amdgpu only uses shared-fences internally, but dmabuf importers rely on > > > implicit write hazard tracking via t

Re: [Intel-gfx] [PATCH v3] drm/amdgpu: Transfer fences to dmabuf importer

On Tue, Aug 07, 2018 at 01:23:19PM +0200, Christian König wrote: > Am 07.08.2018 um 13:05 schrieb Chris Wilson: > > amdgpu only uses shared-fences internally, but dmabuf importers rely on > > implicit write hazard tracking via the reservation_object.fence_excl. > > Well I would rather suggest a so

Re: [Intel-gfx] [PATCH v3] drm/amdgpu: Transfer fences to dmabuf importer

Am 07.08.2018 um 13:05 schrieb Chris Wilson: amdgpu only uses shared-fences internally, but dmabuf importers rely on implicit write hazard tracking via the reservation_object.fence_excl. Well I would rather suggest a solution where we stop doing this. The problem here is that i915 assumes that

[Intel-gfx] [PATCH v3] drm/amdgpu: Transfer fences to dmabuf importer

amdgpu only uses shared-fences internally, but dmabuf importers rely on implicit write hazard tracking via the reservation_object.fence_excl. For example, the importer use the write hazard for timing a page flip to only occur after the exporter has finished flushing its write into the surface. As s