public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/6] drm/i915: Preserve ring buffers objects across resume
Date: Wed, 2 Apr 2014 15:10:13 -0700	[thread overview]
Message-ID: <20140402151013.4e37c8c8@jbarnes-desktop> (raw)
In-Reply-To: <1396452971-25654-3-git-send-email-chris@chris-wilson.co.uk>

On Wed,  2 Apr 2014 16:36:08 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> +static void
> +i915_gem_stop_ringbuffers(struct drm_device *dev)
> +{
> +	struct drm_i915_private *dev_priv = dev->dev_private;
> +	struct intel_ring_buffer *ring;
> +	int i;
> +
> +	for_each_ring(ring, dev_priv, i)
> +		intel_cleanup_ring_buffer(ring);
> +}
> +

You've improved the init/alloc ringbuffer naming, but this one
confuses me.  stop_ringbuffers to me says we're just idling them, but
cleanup_ring_buffer actually does the unmap and free right?

If so, it looks like this will still tear things down on suspend?

Maybe it's all the refactoring making me miss it. :)

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2014-04-02 22:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 15:36 [PATCH 1/6] drm/i915: Replace hardcoded cacheline size with macro Chris Wilson
2014-04-02 15:36 ` [PATCH 2/6] drm/i915: Move all ring resets before setting the HWS page Chris Wilson
2014-04-02 21:58   ` Jesse Barnes
2014-04-03 15:18     ` Daniel Vetter
2014-04-02 15:36 ` [PATCH 3/6] drm/i915: Preserve ring buffers objects across resume Chris Wilson
2014-04-02 22:10   ` Jesse Barnes [this message]
2014-04-03  6:43     ` Chris Wilson
2014-04-02 15:36 ` [PATCH 4/6] drm/i915: Allow the module to load even if we fail to setup rings Chris Wilson
2014-04-02 22:11   ` Jesse Barnes
2014-04-03  6:42     ` Chris Wilson
2014-04-02 15:36 ` [PATCH 5/6] drm/i915: Mark device as wedged if we fail to resume Chris Wilson
2014-04-02 15:36 ` [PATCH 6/6] drm/i915: Include a little more information about why ring init fails Chris Wilson
2014-04-02 21:57 ` [PATCH 1/6] drm/i915: Replace hardcoded cacheline size with macro Jesse Barnes
2014-04-03  6:45   ` Chris Wilson
2014-04-03 15:16     ` Daniel Vetter
2014-04-03 15:23       ` Chris Wilson
2014-04-03 21:09         ` 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=20140402151013.4e37c8c8@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox