intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	naresh.kumar.kachhi@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 0/3] disable rings before sync flush
Date: Wed, 12 Mar 2014 16:07:38 +0100	[thread overview]
Message-ID: <20140312150738.GK30571@phenom.ffwll.local> (raw)
In-Reply-To: <20140312112803.GL23307@nuc-i3427.alporthouse.com>

On Wed, Mar 12, 2014 at 11:28:03AM +0000, Chris Wilson wrote:
> On Wed, Mar 12, 2014 at 04:39:39PM +0530, naresh.kumar.kachhi@intel.com wrote:
> > From: Naresh Kumar Kachhi <naresh.kumar.kachhi@intel.com>
> > 
> > initial version: stop rings before sync flush
> > 
> > v1: address the comments from Chris Wilson on
> > http://www.spinics.net/lists/intel-gfx/msg41025.html.
> > Rather than adding stop and start ring, we are moving
> > ring disable before hw_status_page_setup (sync flush).
> > 
> > v2: Based on Chris's suggestion. Added one more patch to wait
> > until the rings become idle after disabling. In case of timeout
> > we log a message. 
> > 
> > Naresh Kumar Kachhi (3):
> >   drm/i915: disable rings before HW status page setup
> >   drm/i915: wait for rings to become idle once disabled
> >   drm/i915: warn if ring is active before sync flush
> > 
> >  drivers/gpu/drm/i915/i915_reg.h         |  2 ++
> >  drivers/gpu/drm/i915/intel_ringbuffer.c | 18 +++++++++++++-----
> >  drivers/gpu/drm/i915/intel_ringbuffer.h |  2 ++
> >  3 files changed, 17 insertions(+), 5 deletions(-)
> 
> With the minor changes in patch 2,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> and the recommendation for stable@

All 3 merged with the request polish applied to the 2nd patch.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2014-03-12 15:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  5:16 [PATCH] drm/i915: stop command parser before sync flush naresh.kumar.kachhi
2014-03-04  7:39 ` Chris Wilson
2014-03-12  6:50   ` [PATCH v1 0/2] disable rings " naresh.kumar.kachhi
2014-03-12  6:50     ` [PATCH v1 1/2] drm/i915: disable rings before HW status page setup naresh.kumar.kachhi
2014-03-12  6:50     ` [PATCH v1 2/2] drm/i915: warn if ring is active before sync flush naresh.kumar.kachhi
2014-03-12  8:06     ` [PATCH v1 0/2] disable rings " Chris Wilson
2014-03-12  8:12       ` Chris Wilson
2014-03-12 11:09         ` [PATCH v2 0/3] " naresh.kumar.kachhi
2014-03-12 11:09           ` [PATCH v2 1/3] drm/i915: disable rings before HW status page setup naresh.kumar.kachhi
2014-03-12 11:09           ` [PATCH v2 2/3] drm/i915: wait for rings to become idle once disabled naresh.kumar.kachhi
2014-03-12 11:18             ` Chris Wilson
2014-03-12 11:09           ` [PATCH v2 3/3] drm/i915: warn if ring is active before sync flush naresh.kumar.kachhi
2014-03-12 11:28           ` [PATCH v2 0/3] disable rings " Chris Wilson
2014-03-12 15:07             ` Daniel Vetter [this message]

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=20140312150738.GK30571@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=naresh.kumar.kachhi@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).