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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 28 Oct 2012 17:56:16 +0000 (10:56 -0700)
commit2c609a2f31e7961301c3b7ecbc8b47b29c1ea790
tree8ed52ed9e9558b6693bfbcd62619204f432e71c1
parent1161c54f6c3d4681a1a366232b76d6a5b21b2dfa
drm/i915: Use cpu relocations if the object is in the GTT but not mappable

commit 504c7267a1e84b157cbd7e9c1b805e1bc0c2c846 upstream.

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>
Cc: Dave Airlie <airlied@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/gpu/drm/i915/i915_gem_execbuffer.c