From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: ville.syrjala@linux.intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 05/12] drm/i915: Clear VLV_IER around irq processing
Date: Thu, 14 Apr 2016 15:47:59 +0300 [thread overview]
Message-ID: <87wpo0mk5c.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <1460571598-24452-6-git-send-email-ville.syrjala@linux.intel.com>
ville.syrjala@linux.intel.com writes:
> [ text/plain ]
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> On VLV/CHV the master interrupt enable bit only affects GT/PM
> interrupts. Display interrupts are not affected by the master
> irq control.
>
> Also it seems that the CPU interrupt will only be generated when
> the combined result of all GT/PM/display interrupts has a 0->1
> edge. We already use the master interrupt enable bit to make sure
> GT/PM interrupt can generate such an edge if we don't end up clearing
> all IIR bits. We must do the same for display interrupts, and for
> that we can simply clear out VLV_IER, and restore after we've acked
> all the interrupts we are about to process.
>
> So with both master interrupt enable and VLV_IER cleared out, we will
> guarantee that there will be a 0->1 edge if any IIR bits are still set
> at the end, and thus another CPU interrupt will be generated.
>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Fixes: 579de73b048a ("drm/i915: Exit cherryview_irq_handler() after
> one pass")
I have bisected the bsw ci/bat unstability (frequent gpu hangs) to the
commit pointed by Fixes: And reverting seems to help.
I am now running the same drv_module_reload loop on top of this
series. It looks good but its too early to draw conclusions.
I will leave it running for the night.
-Mika
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_irq.c | 36 +++++++++++++++++++++++++++++++++++-
> 1 file changed, 35 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index 626775039919..46be03c616f4 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -1778,7 +1778,7 @@ static irqreturn_t valleyview_irq_handler(int irq, void *arg)
> disable_rpm_wakeref_asserts(dev_priv);
>
> while (true) {
> - /* Find, clear, then process each source of interrupt */
> + u32 ier = 0;
>
> gt_iir = I915_READ(GTIIR);
> pm_iir = I915_READ(GEN6_PMIIR);
> @@ -1789,7 +1789,22 @@ static irqreturn_t valleyview_irq_handler(int irq, void *arg)
>
> ret = IRQ_HANDLED;
>
> + /*
> + * Theory on interrupt generation, based on empirical evidence:
> + *
> + * x = ((VLV_IIR & VLV_IER) ||
> + * (((GT_IIR & GT_IER) || (GEN6_PMIIR & GEN6_PMIER)) &&
> + * (VLV_MASTER_IER & MASTER_INTERRUPT_ENABLE)));
> + *
> + * A CPU interrupt will only be raised when 'x' has a 0->1 edge.
> + * Hence we clear MASTER_INTERRUPT_ENABLE and VLV_IER to
> + * guarantee the CPU interrupt will be raised again even if we
> + * don't end up clearing all the VLV_IIR, GT_IIR, GEN6_PMIIR
> + * bits this time around.
> + */
> I915_WRITE(VLV_MASTER_IER, 0);
> + ier = I915_READ(VLV_IER);
> + I915_WRITE(VLV_IER, 0);
>
> if (gt_iir)
> I915_WRITE(GTIIR, gt_iir);
> @@ -1815,6 +1830,7 @@ static irqreturn_t valleyview_irq_handler(int irq, void *arg)
> if (iir)
> I915_WRITE(VLV_IIR, iir);
>
> + I915_WRITE(VLV_IER, ier);
> I915_WRITE(VLV_MASTER_IER, MASTER_INTERRUPT_ENABLE);
> POSTING_READ(VLV_MASTER_IER);
> }
> @@ -1839,6 +1855,8 @@ static irqreturn_t cherryview_irq_handler(int irq, void *arg)
> disable_rpm_wakeref_asserts(dev_priv);
>
> do {
> + u32 ier = 0;
> +
> master_ctl = I915_READ(GEN8_MASTER_IRQ) & ~GEN8_MASTER_IRQ_CONTROL;
> iir = I915_READ(VLV_IIR);
>
> @@ -1847,7 +1865,22 @@ static irqreturn_t cherryview_irq_handler(int irq, void *arg)
>
> ret = IRQ_HANDLED;
>
> + /*
> + * Theory on interrupt generation, based on empirical evidence:
> + *
> + * x = ((VLV_IIR & VLV_IER) ||
> + * ((GEN8_MASTER_IRQ & ~GEN8_MASTER_IRQ_CONTROL) &&
> + * (GEN8_MASTER_IRQ & GEN8_MASTER_IRQ_CONTROL)));
> + *
> + * A CPU interrupt will only be raised when 'x' has a 0->1 edge.
> + * Hence we clear GEN8_MASTER_IRQ_CONTROL and VLV_IER to
> + * guarantee the CPU interrupt will be raised again even if we
> + * don't end up clearing all the VLV_IIR and GEN8_MASTER_IRQ_CONTROL
> + * bits this time around.
> + */
> I915_WRITE(GEN8_MASTER_IRQ, 0);
> + ier = I915_READ(VLV_IER);
> + I915_WRITE(VLV_IER, 0);
>
> gen8_gt_irq_handler(dev_priv, master_ctl);
>
> @@ -1865,6 +1898,7 @@ static irqreturn_t cherryview_irq_handler(int irq, void *arg)
> if (iir)
> I915_WRITE(VLV_IIR, iir);
>
> + I915_WRITE(VLV_IER, ier);
> I915_WRITE(GEN8_MASTER_IRQ, GEN8_MASTER_IRQ_CONTROL);
> POSTING_READ(GEN8_MASTER_IRQ);
> } while (0);
> --
> 2.7.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-14 12:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 18:19 [PATCH 00/12] drm/i915: VLV/CHV irq handler fixes ville.syrjala
2016-04-13 18:19 ` [PATCH 01/12] drm/i915: Use GEN8_MASTER_IRQ_CONTROL consistently ville.syrjala
2016-04-13 18:19 ` [PATCH 02/12] drm/i915: Set up VLV_MASTER_IER consistently ville.syrjala
2016-04-13 18:19 ` [PATCH 03/12] drm/i915: Clear VLV_IIR after PIPESTAT ville.syrjala
2016-04-13 18:19 ` [PATCH 04/12] drm/i915: Clear VLV_MASTER_IER around irq processing ville.syrjala
2016-04-13 18:19 ` [PATCH 05/12] drm/i915: Clear VLV_IER " ville.syrjala
2016-04-13 20:53 ` Chris Wilson
2016-04-14 8:22 ` Ville Syrjälä
2016-04-14 8:32 ` Chris Wilson
2016-04-14 8:49 ` Ville Syrjälä
2016-04-14 9:36 ` Chris Wilson
2016-04-14 12:30 ` Ville Syrjälä
2016-04-14 12:47 ` Mika Kuoppala [this message]
2016-04-15 7:32 ` Mika Kuoppala
2016-04-13 18:19 ` [PATCH 06/12] drm/i915: Eliminate loop from VLV irq handler ville.syrjala
2016-04-13 18:19 ` [PATCH 07/12] drm/i915: Move variables to narrower scope in VLV/CHV irq handlers ville.syrjala
2016-04-13 18:19 ` [PATCH 08/12] drm/i915: Split PORT_HOTPLUG_STAT ack out from i9xx_hpd_irq_handler() ville.syrjala
2016-04-13 18:19 ` [PATCH 09/12] drm/i915: Split VLV/CVH PIPESTAT handling into ack+handler ville.syrjala
2016-04-13 18:19 ` [PATCH 10/12] drm/i915: Move gt/pm irq handling out from irq disabled section on VLV ville.syrjala
2016-04-13 18:19 ` [PATCH 11/12] drm/i915: Eliminate passing dev+dev_priv to {snb, ilk}_gt_irq_handler() ville.syrjala
2016-04-13 21:02 ` Daniel Vetter
2016-04-13 18:19 ` [PATCH 12/12] drm/i915: Split gen8_gt_irq_handler into ack+handle ville.syrjala
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=87wpo0mk5c.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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