From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Chris Wilson" <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org,
"Antti Koskipää" <antti.koskipaa@linux.intel.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Exit cherryview_irq_handler() after one pass
Date: Thu, 10 Mar 2016 15:01:20 +0200 [thread overview]
Message-ID: <20160310130120.GH10446@intel.com> (raw)
In-Reply-To: <20160310124248.GQ1405@nuc-i3427.alporthouse.com>
On Thu, Mar 10, 2016 at 12:42:48PM +0000, Chris Wilson wrote:
> On Thu, Mar 10, 2016 at 02:24:39PM +0200, Ville Syrj�l� wrote:
> > On Thu, Mar 10, 2016 at 12:10:46PM +0000, Chris Wilson wrote:
> > > My testing only looks at the GT side, and we do stress that pretty hard
> > > because of execlists and have reasonable methods of detection if we stop
> > > processing execbuf. I'm more worried about the display and pipe interrupts.
> >
> > IIRC GT was where the problem was originally.
>
> Before execlists, the only source of GT interrupts would be
> user-interrupts. There the problem is usually not so much that we miss
> the GT interrupt, but that the seqno write is not completed by the time
> the interrupt is asserted. I hope that was the problem you saw.
IIRC those guys already had execlists in use with their Android stuff.
But we did have that whole snooping mess still unresolved at the time
so who knows what was really going on.
--
Ville Syrj�l�
Intel OTC
next prev parent reply other threads:[~2016-03-10 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 11:44 [PATCH] drm/i915: Exit cherryview_irq_handler() after one pass Chris Wilson
2016-03-10 12:01 ` Ville Syrjälä
2016-03-10 12:10 ` Chris Wilson
2016-03-10 12:24 ` Ville Syrjälä
2016-03-10 12:42 ` Chris Wilson
2016-03-10 13:01 ` Ville Syrjälä [this message]
2016-03-10 12:01 ` [Intel-gfx] " Tvrtko Ursulin
2016-03-10 12:12 ` kbuild test robot
2016-03-10 12:18 ` [PATCH v2] " Chris Wilson
2016-03-10 12:25 ` Ville Syrjälä
2016-03-10 12:38 ` [Intel-gfx] " Tvrtko Ursulin
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=20160310130120.GH10446@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=antti.koskipaa@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--cc=tvrtko.ursulin@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).