From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel J Blueman <daniel.blueman@gmail.com>,
Eric Anholt <eric@anholt.net>
Cc: Keith Packard <keithp@keithp.com>,
Dave Airlie <airlied@redhat.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Daniel J Blueman <daniel.blueman@gmail.com>
Subject: Re: [PATCH 3.0-rc3] i915: Fix gen6 (SNB) GPU stalling
Date: Tue, 14 Jun 2011 18:23:16 +0100 [thread overview]
Message-ID: <f80fcd$h9106@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1308070307-2630-1-git-send-email-daniel.blueman@gmail.com>
On Wed, 15 Jun 2011 00:51:47 +0800, Daniel J Blueman <daniel.blueman@gmail.com> wrote:
> True; that is quite heavy handed delay looping.
>
> It's a pity the usual Intel font didn't make it to the programmer's
> reference manuals. Anyway, unmasking the blitter user interrupt in the hardware
> status mask register addresses the root cause. Out of reset it's FFFFFFFFh,
> so we don't need to read it here.
>
> It would be good to get this into -rc4. -stable probably needs some additional
> tweaks.
>
> Signed-off-by: Daniel J Blueman <daniel.blueman@gmail.com>
Tested-by: Chris Wilson <chris@chris-wilson.co.uk>
Should apply as is and be equally effective for stable.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-14 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 16:51 [PATCH 3.0-rc3] i915: Fix gen6 (SNB) GPU stalling Daniel J Blueman
2011-06-14 17:23 ` Chris Wilson [this message]
2011-06-15 2:06 ` Eric Anholt
2011-06-15 3:24 ` Daniel J Blueman
2011-06-15 4:43 ` [Intel-gfx] " Ben Widawsky
2011-06-15 5:04 ` Daniel J Blueman
2011-06-15 15:16 ` Ben Widawsky
2011-06-16 2:45 ` Daniel J Blueman
2011-06-16 18:36 ` Eric Anholt
2011-06-15 16:38 ` Eric Anholt
2011-06-16 3:45 ` Daniel J Blueman
2011-06-15 17:11 ` Kenneth Graunke
[not found] ` <6E3BC7F7C9A4BF4286DD4C043110F30B568EC644CB@shsmsx502.ccr.corp.intel.com>
2011-06-17 14:12 ` Jesse Barnes
2011-06-17 15:29 ` Robert Hooker
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='f80fcd$h9106@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@redhat.com \
--cc=daniel.blueman@gmail.com \
--cc=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.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