Intel-GFX Archive on lore.kernel.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: Clear scanline waits before disabling the pipe.
Date: Sun, 08 Aug 2010 19:54:59 +0100	[thread overview]
Message-ID: <89kc63$hmibu9@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <878w4h0x9i.fsf@pollan.anholt.net>

On Sun, 08 Aug 2010 11:34:01 -0700, Eric Anholt <eric@anholt.net> wrote:
> On Sun,  8 Aug 2010 12:01:38 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > If we disable the pipe and the GPU is currently waiting on a scanline
> > WAIT_FOR_EVENT, the GPU will hang. Fortunately, there is a magic bit
> > which we can write on i915+ to break this wait before disabling the
> > pipe.
> 
> At one point I thought we were taking the lock and idling the GPU before
> a modeset, which would handle this problem, right?  This doesn't seem
> reliable if we aren't, as we may just have not reached the MI_WAIT_FOR_EVENT
> in the ring yet.

Hear, hear. I do think this is still racy, but Jesse thought the hardware
would do the right thing is could just break the wait and disable the
pipe before it had a chance to stall...

Actually, I'm not even convinced that the hardware does the right thing if
a wait for scanline is executed on a disabled pipe - my headless g45 with
a fake output is broken with page-flipping/video.

Hmm, might be a worthy addition to hangcheck though to just reset the wait.
-- 
Chris Wilson, Intel Open Source Technology Centre

      reply	other threads:[~2010-08-08 18:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-08 11:01 [PATCH] drm/i915: Clear scanline waits before disabling the pipe Chris Wilson
2010-08-08 18:34 ` Eric Anholt
2010-08-08 18:54   ` Chris Wilson [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='89kc63$hmibu9@fmsmga002.fm.intel.com' \
    --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