From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Keith Packard <keithp@keithp.com>,
dri-devel@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
daniel@ffwll.ch
Subject: Re: i915_driver_irq_handler: irq 42: nobody cared
Date: Fri, 30 Mar 2012 13:24:38 +0100 [thread overview]
Message-ID: <1333110296_156038@CP5-2952> (raw)
In-Reply-To: <4F75A303.3030409@suse.cz>
On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby <jslaby@suse.cz> wrote:
> On 03/30/2012 12:45 PM, Chris Wilson wrote:
> > On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby <jslaby@suse.cz> wrote:
> >> I don't know what to dump more, because iir is obviously zero too. What
> >> other sources of interrupts are on the (G33) chip?
> >
> > IIR is the master interrupt, with chained secondary interrupt statuses.
> > If IIR is 0, the interrupt wasn't raised by the GPU.
>
> This does not make sense, the handler does something different. Even if
> IIR is 0, it still takes a look at pipe stats.
That was introduced in 05eff845a28499762075d3a72e238a31f4d2407c to close
a race where the pipestat triggered an interrupt after we processed the
secondary registers and before reseting the primary.
But the basic premise that we should only enter the interrupt handler
with IIR!=0 holds (presuming non-shared interrupt lines such as MSI).
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-30 12:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F717CE3.4040206@suse.cz>
2012-03-27 8:42 ` i915_driver_irq_handler: irq 42: nobody cared Jiri Slaby
2012-03-30 9:59 ` Jiri Slaby
2012-03-30 10:45 ` Chris Wilson
2012-03-30 12:11 ` Jiri Slaby
2012-03-30 12:24 ` Chris Wilson [this message]
2012-04-06 21:31 ` i915_driver_irq_handler: irq 42: nobody cared [generic IRQ handling broken?] Jiri Slaby
2012-04-06 22:40 ` Thomas Gleixner
2012-04-09 17:12 ` Jesse Barnes
2012-04-09 17:52 ` Dave Airlie
2012-04-10 8:44 ` Jiri Slaby
2012-04-10 8:50 ` Daniel Vetter
2012-04-10 8:52 ` i915_driver_irq_handler: irq 42: nobody cared Jiri Slaby
2012-04-10 16:50 ` Marcin Slusarz
2012-04-09 17:11 ` Jesse Barnes
2012-04-10 8:47 ` Jiri Slaby
2012-04-10 8:58 ` Daniel Vetter
2012-04-10 9:48 ` Jiri Slaby
2012-04-10 16:26 ` Jesse Barnes
2012-04-10 18:11 ` Jiri Slaby
2012-04-10 18:34 ` Jesse Barnes
2012-04-10 19:52 ` Jiri Slaby
2012-04-10 20:32 ` Daniel Vetter
2012-04-10 20:34 ` Jesse Barnes
2012-04-11 10:40 ` Daniel Vetter
2012-05-03 19:56 ` Jiri Slaby
2012-05-03 21:15 ` Daniel Vetter
2012-05-03 21:16 ` Jiri Slaby
2012-05-03 21:54 ` Jesse Barnes
2012-05-03 23:15 ` Ben Widawsky
2012-04-11 6:29 ` Michel Dänzer
2012-04-11 16:03 ` Jesse Barnes
[not found] ` <20120327085749.GE4276@phenom.ffwll.local>
2012-03-27 10:54 ` Jiri Slaby
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=1333110296_156038@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--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