On to, 2017-05-18 at 10:46 +0100, Chris Wilson wrote:
> If we write a relocation into the buffer, we require our own implicit
> synchronisation added after the start of the execbuf, outside of the
> user's control. As we may end up clflushing, or doing the patch itself
> on the GPU, asynchronously we need to look at the implicit serialisation
> on obj->resv and hence need to disable EXEC_OBJECT_ASYNC for this
> object.
>
> If the user does trigger a stall for relocations, we make sure the stall
> is complete enough so that the batch is not submitted before we complete
> those relocations.
>
> Fixes: 77ae9957897d ("drm/i915: Enable userspace to opt-out of implicit fencing")
> Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
> Cc: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx>
> Cc: Jason Ekstrand <jason@xxxxxxxxxxxxxx>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
