On pe, 2016-08-12 at 11:28 +0100, Chris Wilson wrote: > The existing ABI says that scanouts are pinned into the mappable region > so that legacy clients (e.g. old Xorg or plymouthd) can write directly > into the scanout through a GTT mapping. However if the surface does not > fit into the mappable region, we are better off just trying to fit it > anywhere and hoping for the best. (Any userspace that is cappable of s/cappable/capable/ > using ginormous scanouts is also likely not to rely on pure GTT > updates.) With the partial vma fault support, we are no longer > restricted to only using scanouts that we can pin (though it is still > preferred for performance reasons and for powersaving features like > FBC). > > v2: Skip fence pinning when not mappable. > v3: Add a comment to explain the possible rammifactions of not being > able to use fences for unmappable scanouts. > v4: Rebase to skip over some local patches > v5: Rebase to defer until after we have unmappable GTT fault support > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx> Could use some Acked-by tags. 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
