All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v2] drm/i915: Taint (TAINT_DIE) the kernel if the GPU reset fails
Date: Mon, 04 Dec 2017 15:41:11 +0200	[thread overview]
Message-ID: <1512394871.4394.39.camel@linux.intel.com> (raw)
In-Reply-To: <20171129140533.9375-1-chris@chris-wilson.co.uk>

On Wed, 2017-11-29 at 14:05 +0000, Chris Wilson wrote:
> History tells us that if we cannot reset the GPU now, we never will. This
> then impacts everything that is run subsequently. On failing the reset,
> we mark the driver as wedged, trying to prevent further execution on the
> GPU, forcing userspace to fallback to using the CPU to update its
> framebuffers and let the user know what happened.
> 
> We also want to go one step further and add a taint to the kernel so that
> any subsequent faults can be traced back to this failure. This is
> important for igt, where if the GPU/driver fails we want to reboot and
> restart testing rather than continue on into oblivion.
> 
> TAINT_DIE is colloquially known as "system on fire", which seems
> appropriate for unresponsive hardware.
> 
> v2: Also taint if the recovery fails (again history shows us that is
> typically fatal).
> 
> References: https://bugs.freedesktop.org/show_bug.cgi?id=103514
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Michał Winiarski <michal.winiarski@intel.com>

<SNIP>

> @@ -1951,6 +1954,19 @@ void i915_reset(struct drm_i915_private *i915, unsigned int flags)
>  	wake_up_bit(&error->flags, I915_RESET_HANDOFF);
>  	return;
>  
> +taint:
> +	/*
> +	 * History tells us that if we cannot reset the GPU now, we
> +	 * never will. This then impacts everything that is run
> +	 * subsequently. On failing the reset, we mark the driver
> +	 * as wedged, preventing further execution on the GPU.
> +	 * We also want to go one step further and add a taint to the
> +	 * kernel so that any subsequent faults can be traced back to
> +	 * this failure. This is important for igt, where if the
> +	 * GPU/driver fails we want to reboot and restart testing
> +	 * rather than continue on into oblivion.
> +	 */

As Marta mentioned too, How igt works on a given day is bit volatile to
document in the kernel comments.

With that dropped;

Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-12-04 13:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 13:59 [PATCH] drm/i915: Taint (TAINT_DIE) the kernel if the GPU reset fails Chris Wilson
2017-11-29 14:05 ` [PATCH v2] " Chris Wilson
2017-11-30 12:24   ` Lofstedt, Marta
2017-12-04 13:41   ` Joonas Lahtinen [this message]
2017-12-04 13:45     ` Chris Wilson
2017-12-05 16:56     ` Chris Wilson
2017-12-05 17:06   ` Chris Wilson
2017-11-30 10:02 ` ✗ Fi.CI.BAT: failure for drm/i915: Taint (TAINT_DIE) the kernel if the GPU reset fails (rev2) Patchwork
2017-11-30 14:15 ` Patchwork
2017-12-05 17:26 ` [PATCH v3] drm/i915: Taint (TAINT_WARN) the kernel if the GPU reset fails Chris Wilson
2017-12-05 17:27 ` [PATCH v4] " Chris Wilson
2017-12-05 18:34 ` ✓ Fi.CI.BAT: success for drm/i915: Taint (TAINT_DIE) the kernel if the GPU reset fails (rev4) Patchwork
2017-12-05 21:09 ` ✓ Fi.CI.IGT: " Patchwork

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=1512394871.4394.39.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --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.