As we now use a deferred free queue for objects, simply retiring the
active objects is not enough to immediately free them and recover their
mmap space - we must now also drain the freed object list.

Fixes: fbbd37b36fa5 ("drm/i915: Move object release to a freelist + worker"
Signed-off-by: Chris Wilson <[email protected]>
Cc: Joonas Lahtinen <[email protected]>
Cc: <[email protected]>
---
 drivers/gpu/drm/i915/i915_gem.c | 22 ++++++++++------------
 1 file changed, 10 insertions(+), 12 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 636e388e19de..a8771d9d4e0e 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -2119,20 +2119,18 @@ static int i915_gem_object_create_mmap_offset(struct 
drm_i915_gem_object *obj)
        if (!err)
                return 0;
 
-       /* We can idle the GPU locklessly to flush stale objects, but in order
-        * to claim that space for ourselves, we need to take the big
-        * struct_mutex to free the requests+objects and allocate our slot.
-        */
-       err = i915_gem_wait_for_idle(dev_priv, I915_WAIT_INTERRUPTIBLE);
-       if (err)
-               return err;
+       /* Attempt to reap some mmap space from dead objects */
+       do {
+               err = i915_gem_wait_for_idle(dev_priv, I915_WAIT_INTERRUPTIBLE);
+               if (err)
+                       break;
 
-       err = i915_mutex_lock_interruptible(&dev_priv->drm);
-       if (!err) {
-               i915_gem_retire_requests(dev_priv);
+               i915_gem_drain_freed_objects(dev_priv);
                err = drm_gem_create_mmap_offset(&obj->base);
-               mutex_unlock(&dev_priv->drm.struct_mutex);
-       }
+               if (!err)
+                       break;
+
+       } while (flush_delayed_work(&dev_priv->gt.retire_work));
 
        return err;
 }
-- 
2.11.0

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to