On ke, 2016-08-17 at 18:33 +0100, Chris Wilson wrote: > If we cannot release the fence (for example if someone is inexplicably > trying to write into a tiled framebuffer that is currently pinned to the > display! *cough* kms_frontbuffer_tracking *cough*) fallback to using the > page-by-page pwrite/pread interface, rather than fail the syscall > entirely. > > Since this is triggerable by the user (along pwrite) we have to remove > the WARN_ON(fence->pin_count). > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> 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
