All of lore.kernel.org
 help / color / mirror / Atom feed
From: "O'Rourke, Tom" <Tom.O'Rourke@intel.com>
To: Dave Gordon <david.s.gordon@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 05/13 v4] drm/i915: Debugfs interface to read GuC load status
Date: Fri, 17 Jul 2015 17:39:27 -0700	[thread overview]
Message-ID: <20150718003927.GE81395@torourke-desk1> (raw)
In-Reply-To: <1436466554-24806-6-git-send-email-david.s.gordon@intel.com>

On Thu, Jul 09, 2015 at 07:29:06PM +0100, Dave Gordon wrote:
> From: Alex Dai <yu.dai@intel.com>
> 
> The new node provides access to the status of the GuC-specific loader;
> also the scratch registers used for communication between the i915
> driver and the GuC firmware.
> 
> v2:
>     Changes to output formats per Chris Wilson's suggestions
> 
> v4:
>     Rebased
> 
> Issue: VIZ-4884
> Signed-off-by: Alex Dai <yu.dai@intel.com>
> Signed-off-by: Dave Gordon <david.s.gordon@intel.com>
> ---
Reviewed-by: Tom O'Rourke <Tom.O'Rourke@intel.com>

>  drivers/gpu/drm/i915/i915_debugfs.c | 39 +++++++++++++++++++++++++++++++++++++
>  1 file changed, 39 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 98fd3c9..9ff5f17 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -2359,6 +2359,44 @@ static int i915_llc(struct seq_file *m, void *data)
>  	return 0;
>  }
>  
> +static int i915_guc_load_status_info(struct seq_file *m, void *data)
> +{
> +	struct drm_info_node *node = m->private;
> +	struct drm_i915_private *dev_priv = node->minor->dev->dev_private;
> +	struct intel_guc_fw *guc_fw = &dev_priv->guc.guc_fw;
> +	u32 tmp, i;
> +
> +	if (!HAS_GUC_UCODE(dev_priv->dev))
> +		return 0;
> +
> +	seq_printf(m, "GuC firmware status:\n");
> +	seq_printf(m, "\tpath: %s\n",
> +		guc_fw->guc_fw_path);
> +	seq_printf(m, "\tfetch: %s\n",
> +		intel_guc_fw_status_repr(guc_fw->guc_fw_fetch_status));
> +	seq_printf(m, "\tload: %s\n",
> +		intel_guc_fw_status_repr(guc_fw->guc_fw_load_status));
> +	seq_printf(m, "\tversion wanted: %d.%d\n",
> +		guc_fw->guc_fw_major_wanted, guc_fw->guc_fw_minor_wanted);
> +	seq_printf(m, "\tversion found: %d.%d\n",
> +		guc_fw->guc_fw_major_found, guc_fw->guc_fw_minor_found);
> +
> +	tmp = I915_READ(GUC_STATUS);
> +
> +	seq_printf(m, "\nGuC status 0x%08x:\n", tmp);
> +	seq_printf(m, "\tBootrom status = 0x%x\n",
> +		(tmp & GS_BOOTROM_MASK) >> GS_BOOTROM_SHIFT);
> +	seq_printf(m, "\tuKernel status = 0x%x\n",
> +		(tmp & GS_UKERNEL_MASK) >> GS_UKERNEL_SHIFT);
> +	seq_printf(m, "\tMIA Core status = 0x%x\n",
> +		(tmp & GS_MIA_MASK) >> GS_MIA_SHIFT);
> +	seq_puts(m, "\nScratch registers:\n");
> +	for (i = 0; i < 16; i++)
> +		seq_printf(m, "\t%2d: \t0x%x\n", i, I915_READ(SOFT_SCRATCH(i)));
> +
> +	return 0;
> +}
> +
>  static int i915_edp_psr_status(struct seq_file *m, void *data)
>  {
>  	struct drm_info_node *node = m->private;
> @@ -5073,6 +5111,7 @@ static const struct drm_info_list i915_debugfs_list[] = {
>  	{"i915_gem_hws_bsd", i915_hws_info, 0, (void *)VCS},
>  	{"i915_gem_hws_vebox", i915_hws_info, 0, (void *)VECS},
>  	{"i915_gem_batch_pool", i915_gem_batch_pool_info, 0},
> +	{"i915_guc_load_status", i915_guc_load_status_info, 0},
>  	{"i915_frequency_info", i915_frequency_info, 0},
>  	{"i915_hangcheck_info", i915_hangcheck_info, 0},
>  	{"i915_drpc_info", i915_drpc_info, 0},
> -- 
> 1.9.1
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-07-18  0:42 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 18:29 [PATCH 00/13 v4] Batch submission via GuC Dave Gordon
2015-07-09 18:29 ` [PATCH 01/13 v4] drm/i915: Add i915_gem_object_create_from_data() Dave Gordon
2015-07-18  0:36   ` O'Rourke, Tom
2015-07-09 18:29 ` [PATCH 02/13 v4] drm/i915: Add GuC-related module parameters Dave Gordon
2015-07-18  0:37   ` O'Rourke, Tom
2015-07-09 18:29 ` [PATCH 03/13 v4] drm/i915: Add GuC-related header files Dave Gordon
2015-07-18  0:38   ` O'Rourke, Tom
2015-07-21  6:38     ` Daniel Vetter
2015-07-24 22:08       ` O'Rourke, Tom
2015-07-09 18:29 ` [PATCH 04/13 v4] drm/i915: GuC-specific firmware loader Dave Gordon
2015-07-13 15:35   ` Daniel Vetter
2015-07-18  0:35   ` O'Rourke, Tom
2015-07-20 16:18     ` Yu Dai
2015-07-09 18:29 ` [PATCH 05/13 v4] drm/i915: Debugfs interface to read GuC load status Dave Gordon
2015-07-18  0:39   ` O'Rourke, Tom [this message]
2015-07-09 18:29 ` [PATCH 06/13 v4] drm/i915: Expose two LRC functions for GuC submission mode Dave Gordon
2015-07-24 22:12   ` O'Rourke, Tom
2015-07-09 18:29 ` [PATCH 07/13 v4] drm/i915: GuC submission setup, phase 1 Dave Gordon
2015-07-24 22:31   ` O'Rourke, Tom
2015-07-27 22:41     ` Yu Dai
2015-07-27 23:12       ` O'Rourke, Tom
2015-07-28  0:18         ` Yu Dai
2015-07-28 15:16         ` Dave Gordon
2015-07-28 19:40           ` Dave Gordon
2015-07-28 22:42             ` O'Rourke, Tom
2015-07-28 21:38           ` O'Rourke, Tom
2015-07-09 18:29 ` [PATCH 08/13 v4] drm/i915: Enable GuC firmware log Dave Gordon
2015-07-24 22:40   ` O'Rourke, Tom
2015-07-09 18:29 ` [PATCH 09/13 v4] drm/i915: Implementation of GuC client Dave Gordon
2015-07-25  2:31   ` O'Rourke, Tom
2015-07-09 18:29 ` [PATCH 10/13 v4] drm/i915: Interrupt routing for GuC submission Dave Gordon
2015-07-27 15:33   ` O'Rourke, Tom
2015-07-28 11:29     ` Dave Gordon
2015-07-09 18:29 ` [PATCH 11/13 v4] drm/i915: Integrate GuC-based command submission Dave Gordon
2015-07-27 15:57   ` O'Rourke, Tom
2015-07-27 19:33     ` Yu Dai
2015-07-28 13:59     ` Dave Gordon
2015-07-28 16:47       ` Yu Dai
2015-07-09 18:29 ` [PATCH 12/13 v4] drm/i915: Debugfs interface for GuC submission statistics Dave Gordon
2015-07-27 15:36   ` O'Rourke, Tom
2015-07-09 18:29 ` [PATCH 13/13 v4] drm/i915: Enable GuC submission, where supported Dave Gordon
2015-07-18  0:45 ` [PATCH 00/13 v4] Batch submission via GuC O'Rourke, Tom

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=20150718003927.GE81395@torourke-desk1 \
    --to=tom.o'rourke@intel.com \
    --cc=david.s.gordon@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.