All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Disable all GEM timers and work on unload
Date: Wed, 16 Oct 2013 13:50:29 +0200	[thread overview]
Message-ID: <20131016115027.GJ4830@phenom.ffwll.local> (raw)
In-Reply-To: <1381920601-1092-1-git-send-email-chris@chris-wilson.co.uk>

On Wed, Oct 16, 2013 at 11:50:01AM +0100, Chris Wilson wrote:
> We have two once very similar functions, i915_gpu_idle() and
> i915_gem_idle(). The former is used as the lower level operation to
> flush work on the GPU, whereas the latter is the high level interface to
> flush the GEM bookkeeping in addition to flushing the GPU. As such
> i915_gem_idle() also clears out the request and activity lists and
> cancels the delayed work. This is what we need for unloading the driver,
> unfortunately we called i915_gpu_idle() instead.
> 
> In the process, make sure that when cancelling the delayed work and
> timer, which is synchronous, that we do not hold any locks to prevent a
> deadlock if the work item is already waiting upon the mutex. This
> requires us to push the mutex down from the caller to i915_gem_idle().
> 
> v2: s/i915_gem_idle/i915_gem_suspend/
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=70334
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Tested-by: xunx.fang@intel.com

Queued for -next, thanks for the patch.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2013-10-16 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11  9:14 [PATCH] drm/i915: Disable all GEM timers and work on unload Chris Wilson
2013-10-11 16:22 ` Daniel Vetter
2013-10-11 16:28   ` Chris Wilson
2013-10-16 10:50 ` Chris Wilson
2013-10-16 11:50   ` Daniel Vetter [this message]
2013-10-16 16:47     ` Chris Wilson
2013-10-16 17:41       ` Daniel Vetter

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=20131016115027.GJ4830@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --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.