drm/i915: Use cpu relocations if the object is in the GTT but not mappable
authorChris Wilson <chris@chris-wilson.co.uk>
Thu, 23 Aug 2012 12:12:52 +0000 (13:12 +0100)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Fri, 24 Aug 2012 00:29:16 +0000 (02:29 +0200)
commit504c7267a1e84b157cbd7e9c1b805e1bc0c2c846
tree43191ede34f343627904c51dd4e0f8917b9561e1
parent0327d6ba998ca181013a5a1709701a6532a41972
drm/i915: Use cpu relocations if the object is in the GTT but not mappable

This prevents the case of unbinding the object in order to process the
relocations through the GTT and then rebinding it only to then proceed
to use cpu relocations as the object is now in the CPU write domain. By
choosing to use cpu relocations up front, we can therefore avoid the
rebind penalty.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drivers/gpu/drm/i915/i915_gem_execbuffer.c