On Wed, 23 Dec 2020 at 11:12, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxx> Reviewed-by: Matthew Auld <matthew.auld@xxxxxxxxx> _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
