drm/i915: execbuffer pins objects, no need to ensure they're still in the GTT
authorKeith Packard <keithp@keithp.com>
Fri, 21 Nov 2008 07:14:48 +0000 (23:14 -0800)
committerDave Airlie <airlied@redhat.com>
Mon, 24 Nov 2008 23:28:43 +0000 (09:28 +1000)
commit6133047aa64d2fd5b3b79dff74f696ded45615b2
tree5a1b8ee154479156da304e181a05289da7cf81c5
parent05eff845a28499762075d3a72e238a31f4d2407c
drm/i915: execbuffer pins objects, no need to ensure they're still in the GTT

Before we had the notion of pinning objects, we had a kludge around to make
sure all of the objects were still resident in the GTT before we committed
to executing a batch buffer. We don't need this any longer, and it sticks an
error return in the middle of object domain computations that must be
associated with a subsequent flush/invalidate emmission into the ring.

Signed-off-by: Keith Packard <keithp@keithp.com>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
drivers/gpu/drm/i915/i915_gem.c