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 01/28] drm/i915: Wait for a moment before forcibly resetting the device
Date: Mon, 28 Jan 2019 11:24:12 +0200	[thread overview]
Message-ID: <87d0ohkudf.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190128010245.20148-1-chris@chris-wilson.co.uk>

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

> During igt, we ask to reset the device if any requests are still
> outstanding at the end of a test, as this quickly kills off any
> erroneous hanging request streams that may escape a test. However, since
> it may take the device a few milliseconds to flush itself after the end
> of a normal test, *cough* guc *cough*, we may accidentally tell the
> device to reset itself after it idles. If we wait a moment, our usual
> I915_IDLE_ENGINES_TIMEOUT of 200ms (seems a bit high, but still better
> than umpteen hangchecks!), we can differentiate better between a stuck
> engine and a healthy one, and so avoid prematurely forcing the reset and
> any extra complications that may entail.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_debugfs.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 3b995f9fdc06..e46de507fea2 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -4051,7 +4051,8 @@ i915_drop_caches_set(void *data, u64 val)
>  		  val, val & DROP_ALL);
>  	wakeref = intel_runtime_pm_get(i915);
>  
> -	if (val & DROP_RESET_ACTIVE && !intel_engines_are_idle(i915))
> +	if (val & DROP_RESET_ACTIVE &&
> +	    wait_for(intel_engines_are_idle(i915), I915_IDLE_ENGINES_TIMEOUT))
>  		i915_gem_set_wedged(i915);

Some of the compilications have been welcomed. But it is still
better to try to entail them into tests explicitly rather
than using indirect test harness stress.

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


>  
>  	/* No need to check and wait for gpu resets, only libdrm auto-restarts
> -- 
> 2.20.1
>
> _______________________________________________
> 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

  parent reply	other threads:[~2019-01-28  9:26 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28  1:02 [PATCH 01/28] drm/i915: Wait for a moment before forcibly resetting the device Chris Wilson
2019-01-28  1:02 ` [PATCH 02/28] drm/i915: Rename execlists->queue_priority to preempt_priority_hint Chris Wilson
2019-01-28 10:56   ` Tvrtko Ursulin
2019-01-28 11:04     ` Chris Wilson
2019-01-28  1:02 ` [PATCH 03/28] drm/i915/execlists: Suppress preempting self Chris Wilson
2019-01-28  1:02 ` [PATCH 04/28] drm/i915/execlists: Suppress redundant preemption Chris Wilson
2019-01-28  1:02 ` [PATCH 05/28] drm/i915/selftests: Exercise some AB...BA preemption chains Chris Wilson
2019-01-28  1:02 ` [PATCH 06/28] drm/i915: Stop tracking MRU activity on VMA Chris Wilson
2019-01-28 10:09   ` Tvrtko Ursulin
2019-01-28  1:02 ` [PATCH 07/28] drm/i915: Pull VM lists under the VM mutex Chris Wilson
2019-01-28  1:02 ` [PATCH 08/28] drm/i915: Move vma lookup to its own lock Chris Wilson
2019-01-28  1:02 ` [PATCH 09/28] drm/i915: Always allocate an object/vma for the HWSP Chris Wilson
2019-01-28  1:02 ` [PATCH 10/28] drm/i915: Add timeline barrier support Chris Wilson
2019-01-28  1:02 ` [PATCH 11/28] drm/i915: Move list of timelines under its own lock Chris Wilson
2019-01-28  1:02 ` [PATCH 12/28] drm/i915: Introduce concept of per-timeline (context) HWSP Chris Wilson
2019-01-28  1:02 ` [PATCH 13/28] drm/i915: Enlarge vma->pin_count Chris Wilson
2019-01-28  1:02 ` [PATCH 14/28] drm/i915: Allocate a status page for each timeline Chris Wilson
2019-01-28  1:02 ` [PATCH 15/28] drm/i915: Share per-timeline HWSP using a slab suballocator Chris Wilson
2019-01-28  1:02 ` [PATCH 16/28] drm/i915: Track the context's seqno in its own timeline HWSP Chris Wilson
2019-01-28  1:02 ` [PATCH 17/28] drm/i915: Track active timelines Chris Wilson
2019-01-28  1:02 ` [PATCH 18/28] drm/i915: Identify active requests Chris Wilson
2019-01-28  1:02 ` [PATCH 19/28] drm/i915: Remove the intel_engine_notify tracepoint Chris Wilson
2019-01-28  1:02 ` [PATCH 20/28] drm/i915: Replace global breadcrumbs with per-context interrupt tracking Chris Wilson
2019-01-28 16:24   ` Tvrtko Ursulin
2019-01-28  1:02 ` [PATCH 21/28] drm/i915: Drop fake breadcrumb irq Chris Wilson
2019-01-28  1:02 ` [PATCH 22/28] drm/i915: Generalise GPU activity tracking Chris Wilson
2019-01-28  8:09   ` [PATCH] drm/i915: Allocate active tracking nodes from a slabcache Chris Wilson
2019-01-28  1:02 ` [PATCH 23/28] " Chris Wilson
2019-01-28  1:02 ` [PATCH 24/28] drm/i915: Pull i915_gem_active into the i915_active family Chris Wilson
2019-01-28  1:02 ` [PATCH 25/28] drm/i915: Keep timeline HWSP allocated until the system is idle Chris Wilson
2019-01-28  1:02 ` [PATCH 26/28] drm/i915/execlists: Refactor out can_merge_rq() Chris Wilson
2019-01-28  1:02 ` [PATCH 27/28] drm/i915: Use HW semaphores for inter-engine synchronisation on gen8+ Chris Wilson
2019-01-28  1:02 ` [PATCH 28/28] drm/i915: Prioritise non-busywait semaphore workloads Chris Wilson
2019-01-28  2:33 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/28] drm/i915: Wait for a moment before forcibly resetting the device Patchwork
2019-01-28  2:46 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-28  2:57 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-28  4:23 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-01-28  9:24 ` Mika Kuoppala [this message]
2019-01-28  9:38   ` [PATCH 01/28] " 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=87d0ohkudf.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.