From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/i915: Add Guc/HuC firmware details to error state
Date: Fri, 20 Oct 2017 12:41:57 +0300 [thread overview]
Message-ID: <1508492517.5349.25.camel@linux.intel.com> (raw)
In-Reply-To: <20171019202308.33884-1-michal.wajdeczko@intel.com>
On Thu, 2017-10-19 at 20:23 +0000, Michal Wajdeczko wrote:
> Include GuC and HuC firmware details in captured error state
> to provide additional debug information. To reuse existing
> uc firmware pretty printer, introduce new drm-printer variant
> that works with our i915_error_state_buf output. Also update
> uc firmware pretty printer to accept const input.
>
> v2: don't rely on current caps (Chris)
> dump correct fw info (Michal)
> v3: simplify capture of custom paths (Chris)
>
> Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
A few comments below.
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
> @@ -774,6 +793,11 @@ int i915_error_state_to_str(struct drm_i915_error_state_buf *m,
> err_print_capabilities(m, &error->device_info);
> err_print_params(m, &error->params);
>
> + if (error->device_info.has_guc) {
> + intel_uc_fw_dump(&error->guc_fw, &p);
> + intel_uc_fw_dump(&error->huc_fw, &p);
> + }
I might use "error->{g,h}uc_fw.path" as the condition, for both
individually. We will have DMC here in the future, too.
> +static void i915_capture_uc_state(struct drm_i915_private *dev_priv,
> + struct i915_gpu_state *error)
> +{
> + error->guc_fw = dev_priv->guc.fw;
> + error->huc_fw = dev_priv->huc.fw;
> +
> + /* Make sure to capture custom firmware paths */
This is again a "what" comment, not "why". And they're not necessarily
the custom ones. The "why" is generic to all error capture funcs.
> + error->guc_fw.path = kstrdup(error->guc_fw.path, GFP_ATOMIC);
> + error->huc_fw.path = kstrdup(error->huc_fw.path, GFP_ATOMIC);
> +}
--
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
next prev parent reply other threads:[~2017-10-20 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 20:23 [PATCH v3] drm/i915: Add Guc/HuC firmware details to error state Michal Wajdeczko
2017-10-19 20:47 ` ✗ Fi.CI.BAT: failure for drm/i915: Add Guc/HuC firmware details to error state (rev3) Patchwork
2017-10-20 9:41 ` Joonas Lahtinen [this message]
2017-10-20 11:44 ` [PATCH v3] drm/i915: Add Guc/HuC firmware details to error state Chris Wilson
2017-10-20 12:14 ` Michal Wajdeczko
2017-10-20 12:21 ` Chris Wilson
2017-10-20 12:36 ` Michal Wajdeczko
2017-10-20 12:43 ` Chris Wilson
2017-10-20 12:50 ` Michal Wajdeczko
2017-10-20 12:57 ` Chris Wilson
2017-10-20 14:44 ` Michal Wajdeczko
2017-10-20 14:50 ` Chris Wilson
2017-10-20 14:59 ` Michal Wajdeczko
2017-10-20 15:14 ` 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=1508492517.5349.25.camel@linux.intel.com \
--to=joonas.lahtinen@linux.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