All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Summers <stuart.summers@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 2/2] drm/i915: Extend reset modparam to domain resets
Date: Tue, 14 May 2019 09:46:53 -0700	[thread overview]
Message-ID: <20190514164653.935-2-stuart.summers@intel.com> (raw)
In-Reply-To: <20190514164653.935-1-stuart.summers@intel.com>

In the event a platform does not properly implement reset,
do not go through reset flows for engine domains to avoid
an unlikely situation where writes are accepted but register
values are never cleared, as this can result in GPU wedges
in these cases.

Signed-off-by: Stuart Summers <stuart.summers@intel.com>
---
 drivers/gpu/drm/i915/gt/intel_reset.c | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
index 464369bc55ad..81f9f9f73b1c 100644
--- a/drivers/gpu/drm/i915/gt/intel_reset.c
+++ b/drivers/gpu/drm/i915/gt/intel_reset.c
@@ -309,6 +309,12 @@ static int gen6_hw_domain_reset(struct drm_i915_private *i915,
 	struct intel_uncore *uncore = &i915->uncore;
 	int err;
 
+	if (!i915_modparams.reset) {
+		DRM_DEBUG_DRIVER("Skipping 0x%08x engines reset\n",
+				 hw_domain_mask);
+		return 0;
+	}
+
 	/*
 	 * GEN6_GDRST is not in the gt power well, no need to check
 	 * for fifo space for the write or forcewake the chip for
@@ -517,6 +523,13 @@ static int gen8_engine_reset_prepare(struct intel_engine_cs *engine)
 		return 0;
 	}
 
+	if (!i915_modparams.reset) {
+		DRM_DEBUG_DRIVER("Skipping %s reset request {request: %08x, RESET_CTL: %08x}\n",
+				 engine->name, request,
+				 intel_uncore_read_fw(uncore, reg));
+		return 0;
+	}
+
 	intel_uncore_write_fw(uncore, reg, _MASKED_BIT_ENABLE(request));
 	ret = __intel_wait_for_register_fw(uncore, reg, mask, ack,
 					   700, 0, NULL);
-- 
2.21.0.5.gaeb582a983

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-05-14 16:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 16:46 [PATCH 1/2] drm/i915: Re-add enable_rc6 modparam Stuart Summers
2019-05-14 16:46 ` Stuart Summers [this message]
2019-05-14 16:54   ` [PATCH 2/2] drm/i915: Extend reset modparam to domain resets Chris Wilson
2019-05-14 17:03     ` Summers, Stuart
2019-05-14 16:53 ` [PATCH 1/2] drm/i915: Re-add enable_rc6 modparam Chris Wilson
2019-05-14 18:32   ` Summers, Stuart
2019-05-15  0:06     ` Rodrigo Vivi
2019-05-15  5:43       ` Tvrtko Ursulin
2019-05-15 14:16         ` Summers, Stuart
2019-05-16  9:59       ` Jani Nikula
2019-05-16 14:10         ` Summers, Stuart
2019-05-16 15:42           ` Jani Nikula
2019-05-16 15:49             ` Summers, Stuart
2019-05-17 16:17               ` Rodrigo Vivi
2019-05-17 16:34                 ` Ville Syrjälä
2019-05-17 16:44                   ` Rodrigo Vivi
2019-05-17 17:02                     ` Ville Syrjälä
2019-05-21 19:17                 ` Summers, Stuart
2019-05-14 17:07 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] " Patchwork
2019-05-14 17:29 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-15  0:23 ` ✗ Fi.CI.IGT: failure " 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=20190514164653.935-2-stuart.summers@intel.com \
    --to=stuart.summers@intel.com \
    --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.