From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 12/22] drm/i915/guc: Treat GuC initialization failure as -EIO
Date: Fri, 12 Apr 2019 18:20:47 -0700 [thread overview]
Message-ID: <a5b61ab6-8947-a301-73cc-4cd4555d93fb@intel.com> (raw)
In-Reply-To: <20190411084436.24384-13-michal.wajdeczko@intel.com>
On 4/11/19 1:44 AM, Michal Wajdeczko wrote:
> There is no fallback to execlists, but instead of aborting whole
> driver load, just mark it as wedged.
>
I don't see any inject_load_failure() in the guc paths (WOPCM aside).
Can you sprinkle a few of them around to make sure this is solid?
Thanks,
Daniele
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 3 ++-
> drivers/gpu/drm/i915/intel_uc.c | 6 ++----
> 2 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 0a818a60ad31..ac64a6fd9b91 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -4963,7 +4963,8 @@ int i915_gem_init(struct drm_i915_private *dev_priv)
> mutex_lock(&dev_priv->drm.struct_mutex);
> intel_uc_fini_hw(dev_priv);
> err_uc_init:
> - intel_uc_fini(dev_priv);
> + if (ret != -EIO)
> + intel_uc_fini(dev_priv);
> err_pm:
> if (ret != -EIO) {
> intel_cleanup_gt_powersave(dev_priv);
> diff --git a/drivers/gpu/drm/i915/intel_uc.c b/drivers/gpu/drm/i915/intel_uc.c
> index 8e5e4226df53..03bc2a0ee34b 100644
> --- a/drivers/gpu/drm/i915/intel_uc.c
> +++ b/drivers/gpu/drm/i915/intel_uc.c
> @@ -435,12 +435,10 @@ int intel_uc_init_hw(struct drm_i915_private *i915)
> /*
> * Note that there is no fallback as either user explicitly asked for
> * the GuC or driver default option was to run with the GuC enabled.
> + * Return -EIO to just disable GPU submission but keep KMS alive.
> */
> - if (GEM_WARN_ON(ret == -EIO))
> - ret = -EINVAL;
> -
> dev_err(i915->drm.dev, "GuC initialization failed %d\n", ret);
> - return ret;
> + return -EIO;
> }
>
> void intel_uc_fini_hw(struct drm_i915_private *i915)
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-13 1:20 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 8:44 [PATCH v2 00/22] GuC 32.0.3 Michal Wajdeczko
2019-04-11 8:44 ` [PATCH v2 01/22] drm/i915/guc: Change platform default GuC mode Michal Wajdeczko
2019-04-12 22:52 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 02/22] drm/i915/guc: Don't allow GuC submission Michal Wajdeczko
2019-04-15 7:37 ` Martin Peres
2019-04-11 8:44 ` [PATCH v2 03/22] drm/i915/guc: Simplify preparation of GuC parameter block Michal Wajdeczko
2019-04-15 18:27 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 04/22] drm/i915/guc: Update GuC firmware versions and names Michal Wajdeczko
2019-04-12 22:42 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 05/22] drm/i915/guc: Update GuC firmware CSS header Michal Wajdeczko
2019-04-15 20:25 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 06/22] drm/i915/guc: Update GuC boot parameters Michal Wajdeczko
2019-04-12 23:46 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 07/22] drm/i915/guc: Update GuC sleep status values Michal Wajdeczko
2019-04-13 0:06 ` Daniele Ceraolo Spurio
2019-04-13 0:24 ` Daniele Ceraolo Spurio
2019-04-15 20:21 ` John Spotswood
2019-04-13 0:20 ` [PATCH v2] drm/i915/guc: updated suspend/resume protocol Daniele Ceraolo Spurio
2019-04-16 23:16 ` John Spotswood
2019-04-11 8:44 ` [PATCH v2 08/22] drm/i915/guc: Update GuC sample-forcewake command Michal Wajdeczko
2019-04-13 0:10 ` Daniele Ceraolo Spurio
2019-04-16 23:45 ` John Spotswood
2019-04-11 8:44 ` [PATCH v2 09/22] drm/i915/guc: Update GuC ADS object definition Michal Wajdeczko
2019-04-13 1:16 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 10/22] drm/i915/guc: Always ask GuC to update power domain states Michal Wajdeczko
2019-04-15 20:46 ` Daniele Ceraolo Spurio
2019-04-16 23:26 ` John Spotswood
2019-04-11 8:44 ` [PATCH v2 11/22] drm/i915/guc: Reset GuC ADS during sanitize Michal Wajdeczko
2019-04-16 11:44 ` Lis, Tomasz
2019-04-11 8:44 ` [PATCH v2 12/22] drm/i915/guc: Treat GuC initialization failure as -EIO Michal Wajdeczko
2019-04-13 1:20 ` Daniele Ceraolo Spurio [this message]
2019-04-11 8:44 ` [PATCH v2 13/22] drm/i915/guc: New GuC interrupt register for Gen11 Michal Wajdeczko
2019-04-13 1:28 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 14/22] drm/i915/guc: New GuC scratch registers " Michal Wajdeczko
2019-04-13 1:30 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 15/22] drm/i915/huc: New HuC status register " Michal Wajdeczko
2019-04-15 21:19 ` Daniele Ceraolo Spurio
2019-04-15 21:44 ` Michal Wajdeczko
2019-04-15 22:10 ` Daniele Ceraolo Spurio
2019-04-15 22:23 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 16/22] drm/i915/guc: Create vfuncs for the GuC interrupts control functions Michal Wajdeczko
2019-04-15 17:51 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 17/22] drm/i915/guc: Correctly handle GuC interrupts on Gen11 Michal Wajdeczko
2019-04-11 8:44 ` [PATCH v2 18/22] drm/i915/guc: Update GuC CTB response definition Michal Wajdeczko
2019-04-15 17:57 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 19/22] drm/i915/guc: Enable GuC CTB communication on Gen11 Michal Wajdeczko
2019-04-11 23:58 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 20/22] drm/i915/guc: Define GuC firmware version for Icelake Michal Wajdeczko
2019-04-15 22:22 ` Srivatsa, Anusha
2019-04-11 8:44 ` [PATCH v2 21/22] drm/i915/huc: Define HuC " Michal Wajdeczko
2019-04-18 12:27 ` Ye, Tony
2019-04-11 8:44 ` [PATCH v2 22/22] HAX: prevent CI failures on configs with forced GuC submission Michal Wajdeczko
2019-04-12 11:30 ` Martin Peres
2019-04-12 11:54 ` Michal Wajdeczko
2019-04-11 19:17 ` ✗ Fi.CI.SPARSE: warning for GuC 32.0.3 (rev2) Patchwork
2019-04-11 19:37 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-11 20:24 ` [PATCH v2 00/22] GuC 32.0.3 Chris Wilson
2019-04-12 2:26 ` ✓ Fi.CI.IGT: success for GuC 32.0.3 (rev2) Patchwork
2019-04-13 0:46 ` ✗ Fi.CI.SPARSE: warning for GuC 32.0.3 (rev3) Patchwork
2019-04-13 1:09 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-13 4:33 ` ✓ 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=a5b61ab6-8947-a301-73cc-4cd4555d93fb@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox