From: Shuang He <shuang.he@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: pipe control notify removed?
Date: Wed, 15 Dec 2010 11:22:56 +0800 [thread overview]
Message-ID: <4D083490.4020902@intel.com> (raw)
In-Reply-To: <20101215031453.GA29548@zhen-devel.sh.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 838 bytes --]
Yeah, I also met this issue, and bisection point to this as well :)
32402 <https://bugs.freedesktop.org/show_bug.cgi?id=32402> 19:05:15
cri hig chris@chris-wilson.co.uk shuang.he@intel.com NEW
[piketon -next bisected] Many tests make GPU hang and reset
Thanks
--Shuang
On 2010-12-15 11:14, Zhenyu Wang wrote:
> Chris, just notice you removed pipe control notify entirely on -next,
> that seems wrong to me. In Ironlake time, we've seen interrupt stall issue
> with user interrupt, and be warned user interrupt is deprecated, so we moved
> on to use pipe control notify, although there's a workaround later covered
> that's required on Ironlake. But it's stable finally. And for sandybridge,
> there's no such workaround needed.
>
> btw, could you also send mails for changes on -next? It'll be easy to be
> notified.
>
[-- Attachment #1.2: Type: text/html, Size: 2418 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2010-12-15 3:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 3:14 pipe control notify removed? Zhenyu Wang
2010-12-15 3:22 ` Shuang He [this message]
2010-12-15 10:05 ` Chris Wilson
2010-12-16 1:59 ` Zhenyu Wang
2010-12-16 2:23 ` Fu Michael
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=4D083490.4020902@intel.com \
--to=shuang.he@intel.com \
--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