All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 04/18] drm/i915: Only emit the 'send bug report' once for a GPU hang
Date: Mon, 19 Aug 2019 14:29:46 +0300	[thread overview]
Message-ID: <87d0h15r6d.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190819075835.20065-5-chris@chris-wilson.co.uk>

Chris Wilson <chris@chris-wilson.co.uk> writes:

> Use a locked xchg to ensure that the global log message giving
> instructions on how to send a bug report is emitted precisely once.
>

Well you must have run into this as this patch appeared.
Arguably better than some read/write once trickery.

Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>

> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>  drivers/gpu/drm/i915/i915_gpu_error.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index b0ae055b6c82..e284bd76fa86 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -1765,7 +1765,7 @@ void i915_capture_error_state(struct drm_i915_private *i915,
>  		return;
>  	}
>  
> -	if (!warned &&
> +	if (!xchg(&warned, true) &&
>  	    ktime_get_real_seconds() - DRIVER_TIMESTAMP < DAY_AS_SECONDS(180)) {
>  		pr_info("GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.\n");
>  		pr_info("Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel\n");
> @@ -1773,7 +1773,6 @@ void i915_capture_error_state(struct drm_i915_private *i915,
>  		pr_info("The GPU crash dump is required to analyze GPU hangs, so please always attach it.\n");
>  		pr_info("GPU crash dump saved to /sys/class/drm/card%d/error\n",
>  			i915->drm.primary->index);
> -		warned = true;
>  	}
>  }
>  
> -- 
> 2.23.0.rc1
>
> _______________________________________________
> 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

  reply	other threads:[~2019-08-19 11:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19  7:58 Lock dropping Chris Wilson
2019-08-19  7:58 ` [PATCH 01/18] drm/i915: Always wrap the ring offset before resetting Chris Wilson
2019-08-19  8:40   ` Mika Kuoppala
2019-08-19  7:58 ` [PATCH 02/18] drm/i915/gt: Mark up the nested engine-pm timeline lock as irqsafe Chris Wilson
2019-08-19  8:43   ` Mika Kuoppala
2019-08-19  9:04     ` Chris Wilson
2019-08-19 11:31       ` Mika Kuoppala
2019-08-19  7:58 ` [PATCH 03/18] drm/i915: Use 0 for the unordered context Chris Wilson
2019-08-19  7:58 ` [PATCH 04/18] drm/i915: Only emit the 'send bug report' once for a GPU hang Chris Wilson
2019-08-19 11:29   ` Mika Kuoppala [this message]
2019-08-19 11:36     ` Chris Wilson
2019-08-19  7:58 ` [PATCH 05/18] drm/i915: i915_active.retire() is optional Chris Wilson
2019-08-19 14:35   ` Matthew Auld
2019-08-19  7:58 ` [PATCH 06/18] drm/i915: Generalise the clflush dma-worker Chris Wilson
2019-08-19  7:58 ` [PATCH 07/18] drm/i915: Replace PIN_NONFAULT with calls to PIN_NOEVICT Chris Wilson
2019-08-19  7:58 ` [PATCH 08/18] drm/i915: Track ggtt fence reservations under its own mutex Chris Wilson
2019-08-19  7:58 ` [PATCH 09/18] drm/i915: Only track bound elements of the GTT Chris Wilson
2019-08-19  7:58 ` [PATCH 10/18] drm/i915: Pull obj->userfault tracking under the ggtt->mutex Chris Wilson
2019-08-19  7:58 ` [PATCH 11/18] drm/i915: Replace i915_vma_put_fence() Chris Wilson
2019-08-19  7:58 ` [PATCH 12/18] drm/i915: Make shrink/unshrink be atomic Chris Wilson
2019-08-19  7:58 ` [PATCH 13/18] drm/i915: Make i915_vma.flags atomic_t for mutex reduction Chris Wilson
2019-08-19  7:58 ` [PATCH 14/18] drm/i915: Pull i915_vma_pin under the vm->mutex Chris Wilson
2019-08-19  7:58 ` [PATCH 15/18] drm/i915: Push the i915_active.retire into a worker Chris Wilson
2019-08-19  7:58 ` [PATCH 16/18] drm/i915: Coordinate i915_active with its own mutex Chris Wilson
2019-08-19  7:58 ` [PATCH 17/18] drm/i915: Move idle barrier cleanup into engine-pm Chris Wilson
2019-08-19  7:58 ` [PATCH 18/18] drm/i915: Drop struct_mutex from around i915_retire_requests() Chris Wilson
2019-08-19  8:39 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/18] drm/i915: Always wrap the ring offset before resetting Patchwork
2019-08-19  9:15 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-08-19  9:20   ` 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=87d0h15r6d.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@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.