On Tue, Aug 23, 2016 at 11:48:34AM +0100, Chris Wilson wrote: > Legacy cursor updates are entirely asynchronous with respect to all > other users of the atomic pipeline. They neither wait for any > outstanding flips, nor do they cause subsequent flips to be delayed. The > only ordering we do require is given by making the legacy cursor update > nonblocking (so the sequence of userspace calls from a process is
s/nonblocking/blocking/! > ordered from the pov of the client). -- Chris Wilson, Intel Open Source Technology Centre
