From: Matthias Hopf <mhopf@suse.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] Dont use hardware acceleration on Sandybridge rev 07 hardware or earlier.
Date: Sat, 20 Nov 2010 16:17:40 +0100 [thread overview]
Message-ID: <20101120151740.GA16296@suse.de> (raw)
In-Reply-To: <c6d829$pjmtjh@fmsmga001.fm.intel.com>
On Nov 19, 10 21:47:48 +0000, Chris Wilson wrote:
> On Fri, 19 Nov 2010 04:29:57 +0100, Matthias Hopf <mhopf@suse.de> wrote:
> > This is known to lock up the GPU even with the workaround in place.
>
> Before applying this patch, I'd like to know the results of using the
> FORCE_WAKE write before reading the ring buffer registers. Also as we are
> accumulating workarounds for SNB faster than is healthy, we should be
> careful about which one we mean at the time of the comment.
I know, I know. The patch is (one of) the results of the Novell-HP-Intel
workshop in Taipei this week. It turned out that rev07 is too unstable.
Keith and Eric can probably comment on this. Better than I can.
I'm currently unsure whether the FORCE_WAKE write is the workaround
Eric was testing, but we used his intel_drm_next branch for that.
Without that workaround in place the rev07 locked up basically
immediately, while with the workaround it took a while (though not very
long) to freeze the GPU.
Strictly speaking the patch is possibly not really required for
upstream, as it's only about rev07. We will use it to be able to
continue testing at Novell with these old revisions.
Thanks
CU
Matthias
--
Matthias Hopf <mhopf@suse.de> __ __ __
Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de
Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de
next prev parent reply other threads:[~2010-11-20 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 3:29 [PATCH] Don't use hardware acceleration on Sandybridge rev 07 hardware or earlier Matthias Hopf
2010-11-19 21:47 ` [PATCH] Dont " Chris Wilson
2010-11-20 15:17 ` Matthias Hopf [this message]
2010-11-21 3:59 ` Keith Packard
2010-11-21 9:03 ` Chris Wilson
2010-11-24 3:13 ` Zou, Nanhai
2010-12-05 11:44 ` Chris Wilson
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=20101120151740.GA16296@suse.de \
--to=mhopf@suse.de \
--cc=chris@chris-wilson.co.uk \
--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