All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH] drm/i915: don't leak global_timeline
Date: Wed, 16 Nov 2016 19:32:49 +0000	[thread overview]
Message-ID: <1479324769-1532-1-git-send-email-matthew.auld@intel.com> (raw)

We need to clean up the global_timeline in i915_gem_load_cleanup.

Cc: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
---
 drivers/gpu/drm/i915/i915_gem.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 3fb5e66..c440e72 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -4557,6 +4557,8 @@ void i915_gem_load_cleanup(struct drm_device *dev)
 
 	WARN_ON(!llist_empty(&dev_priv->mm.free_list));
 
+	i915_gem_timeline_fini(&dev_priv->gt.global_timeline);
+
 	kmem_cache_destroy(dev_priv->dependencies);
 	kmem_cache_destroy(dev_priv->requests);
 	kmem_cache_destroy(dev_priv->vmas);
-- 
2.7.4

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2016-11-16 19:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 19:32 Matthew Auld [this message]
2016-11-16 20:46 ` ✗ Fi.CI.BAT: warning for drm/i915: don't leak global_timeline Patchwork
2016-11-16 20:57 ` [PATCH] " Chris Wilson
2016-11-17  8:48 ` Daniel Vetter
2016-11-17  8:54   ` Chris Wilson
2016-11-17 20:20 ` Matthew Auld
2016-11-17 20:24   ` Chris Wilson
2016-11-17 20:38 ` Matthew Auld
2016-11-17 20:57   ` Chris Wilson
2016-11-17 20:46 ` ✗ Fi.CI.BAT: warning for drm/i915: don't leak global_timeline (rev2) Patchwork
2016-11-18  6:15 ` ✗ Fi.CI.BAT: warning for drm/i915: don't leak global_timeline (rev3) Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1479324769-1532-1-git-send-email-matthew.auld@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.