public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: "Flush Me Harder" required on gen6+
Date: Thu, 28 Jun 2012 21:06:51 +0200	[thread overview]
Message-ID: <20120628190651.GD5596@phenom.ffwll.local> (raw)
In-Reply-To: <1340876273_97159@CP5-2952>

On Thu, Jun 28, 2012 at 10:37:07AM +0100, Chris Wilson wrote:
> On Thu, 28 Jun 2012 09:48:42 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > The prep to remove the flushing list in
> > 
> > commit cc889e0f6ce6a63c62db17d702ecfed86d58083f
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date:   Wed Jun 13 20:45:19 2012 +0200
> > 
> >     drm/i915: disable flushing_list/gpu_write_list
> > 
> > causes quite some decent regressions. We can fix this by setting the
> > CS_STALL bit to ensure that the following seqno write happens only
> > after the cache flush has completed. But only do that when the caller
> > actually wants the flush (and not also when we invalidate caches
> > before starting the next batch).
> > 
> > I've looked through all our ancient scrolls about gen6+ pipe control
> > workarounds, and this seems to be indeed a legal combination: We're
> > allowed to set the CS_STALL bit when we flush the render cache (which
> > we do).
> > 
> > While yelling at this code, also pass back the return value from
> > intel_emit_post_sync_nonzero_flush properly.
> > 
> > v2: Instead of emitting more pipe controls, set the CS_STALL bit on
> > the write flush as suggested by Chris Wilson. It seems to work, too.
> > 
> > Cc: Eric Anholt <eric@anholt.net>
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=51436
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=51429
> > Tested-by: Lu Hua <huax.lu@intel.com>
> > Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Tested-by: Chris Wilson <chris@chris-wilson.co.uk>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Queued for -next, thanks for the review.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

      reply	other threads:[~2012-06-28 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  7:48 [PATCH] drm/i915: "Flush Me Harder" required on gen6+ Daniel Vetter
2012-06-28  9:37 ` Chris Wilson
2012-06-28 19:06   ` 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=20120628190651.GD5596@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --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