public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Eric Anholt <eric@anholt.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Don't forget to apply SNB PIPE_CONTROL GTT workaround.
Date: Tue, 31 Jul 2012 09:21:55 +0100	[thread overview]
Message-ID: <1343722926_20786@CP5-2952> (raw)
In-Reply-To: <1343697866-5572-1-git-send-email-eric@anholt.net>

On Mon, 30 Jul 2012 18:24:26 -0700, Eric Anholt <eric@anholt.net> wrote:
> If a buffer that was the target of a PIPE_CONTROL from userland was a
> reused one that hadn't been evicted which had not previously had this
> workaround applied, then we would not bind it into the GTT and the
> write would land somewhere else.
> 
> Based on a doubting-my-sanity debugging session with cworth, I'm
> pretty sure this will fix his reproducible GL_EXT_timer_query
> failures, and hopefully the intermittent OQ issues on snb that
> danvet's been working on.
> 
> I have not tested it yet, but hopefully when cworth gets home he will.

Had to look hard to find the secret ingredient. The reason why this
patch will work is that that in the middle of the error checking we have
an early success return after applying the new reloc domains iff the
object still holds the same GTT offset as presumed by the reloc.

Probably deserves a little more clarification in the changelog as to why
the patch works.

Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

I think this should also fix
  https://bugs.freedesktop.org/show_bug.cgi?id=48019
but my snb has decided today is the day to hard hang instead.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  parent reply	other threads:[~2012-07-31  8:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31  1:24 [PATCH] drm/i915: Don't forget to apply SNB PIPE_CONTROL GTT workaround Eric Anholt
2012-07-31  5:38 ` Carl Worth
2012-07-31  8:21 ` Chris Wilson [this message]
2012-07-31 22:35 ` Eric Anholt
2012-08-05 19:46   ` 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=1343722926_20786@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --cc=eric@anholt.net \
    --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