All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 1/3] drm/i915: Drop racy markup of missed-irqs from idle-worker
Date: Thu, 21 Jul 2016 10:58:05 +0100	[thread overview]
Message-ID: <57909CAD.2010005@linux.intel.com> (raw)
In-Reply-To: <1469084259-23110-1-git-send-email-chris@chris-wilson.co.uk>


On 21/07/16 07:57, Chris Wilson wrote:
> During the idle-worker we disable the hangcheck and so kick any waiters
> that should have been completed (since the GPU is now idle). Unlike the
> hangcheck, we do not take any care to avoid the race between the irq
> handler and ourselves, and so it is possible for us to declare a missed
> interrupt even as the bottom-half is being scheduled to run. Let's
> ignore this race to stop a potential false-positive error.

If the bottom half is scheduled to run then then..

> References: https://bugs.freedesktop.org/show_bug.cgi?id=96974
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> ---
>   drivers/gpu/drm/i915/i915_gem.c | 7 +++----
>   1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 40047eb48826..9e826585edb2 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -2706,10 +2706,9 @@ i915_gem_idle_work_handler(struct work_struct *work)
>   	rearm_hangcheck = false;
>
>   	stuck_engines = intel_kick_waiters(dev_priv);

... this will not return a stucked engine since the there is a bh task 
assigned all until the bh exits.

So I don't get it. :)

Regards,

Tvrtko

> -	if (unlikely(stuck_engines)) {
> -		DRM_DEBUG_DRIVER("kicked stuck waiters...missed irq\n");
> -		dev_priv->gpu_error.missed_irq_rings |= stuck_engines;
> -	}
> +	if (unlikely(stuck_engines))
> +		DRM_DEBUG_DRIVER("kicked stuck waiters (%x)...missed irq?\n",
> +				 stuck_engines);
>
>   	if (INTEL_GEN(dev_priv) >= 6)
>   		gen6_rps_idle(dev_priv);
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-07-21  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21  6:57 [PATCH v2 1/3] drm/i915: Drop racy markup of missed-irqs from idle-worker Chris Wilson
2016-07-21  6:57 ` [PATCH v2 2/3] drm/i915: Update the breadcrumb interrupt counter before enabling Chris Wilson
2016-07-21  6:57 ` [PATCH v2 3/3] drm/i915: Check for a stuck waiter before a missed interrupt Chris Wilson
2016-07-21 18:34   ` Chris Wilson
2016-07-22  7:57   ` Chris Wilson
2016-07-21  7:55 ` ✓ Ro.CI.BAT: success for series starting with [v2,1/3] drm/i915: Drop racy markup of missed-irqs from idle-worker Patchwork
2016-07-21  9:58 ` Tvrtko Ursulin [this message]
2016-07-21 10:10   ` [PATCH v2 1/3] " Chris Wilson
2016-07-21 10:28     ` Tvrtko Ursulin
2016-07-21 11:04       ` Chris Wilson
2016-07-22 10:10         ` Tvrtko Ursulin
2016-07-22 10:22           ` 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=57909CAD.2010005@linux.intel.com \
    --to=tvrtko.ursulin@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.