[Intel-gfx] [PATCH 03/62] drm/i915/gt: Decouple inflight virtual engines
Matthew Auld
matthew.william.auld at gmail.com
Thu Dec 24 12:57:14 UTC 2020
On Wed, 23 Dec 2020 at 11:12, Chris Wilson <chris at chris-wilson.co.uk> wrote:
>
> Once a virtual engine has been bound to a sibling, it will remain bound
> until we finally schedule out the last active request. We can not rebind
> the context to a new sibling while it is inflight as the context save
> will conflict, hence we wait. As we cannot then use any other sibliing
> while the context is inflight, only kick the bound sibling while it
> inflight and upon scheduling out the kick the rest (so that we can swap
> engines on timeslicing if the previously bound engine becomes
> oversubscribed).
>
> Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Reviewed-by: Matthew Auld <matthew.auld at intel.com>
More information about the Intel-gfx
mailing list