On Sun, 25 Mar 2012 19:47:40 +0200, Daniel Vetter <daniel.vet...@ffwll.ch> wrote: > While moving around things, this two functions slowly grew out of any > sane bounds. So extract a few lines that do the copying and > clflushing. Also add a few comments to explain what's going on. > > v2: Again do s/needs_clflush/needs_clflush_after/ in the write paths > as suggested by Chris Wilson. > > Signed-Off-by: Daniel Vetter <daniel.vet...@ffwll.ch>
I've tested up to this point and have no further comments to make. (Ok, there is the s/claring/glaring/ spelling mistake ;-) 1-13: Tested-by: Chris Wilson <ch...@chris-wilson.co.uk> Reviewed-by: Chris Wilson <ch...@chris-wilson.co.uk> And it turns out I've never used swizzled pwrites. ;) -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
