From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: akash.goel@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 15/18] drm/i915: Debugfs support for GuC logging control
Date: Mon, 15 Aug 2016 17:03:25 +0100 [thread overview]
Message-ID: <57B1E7CD.5000709@linux.intel.com> (raw)
In-Reply-To: <1471272599-14586-16-git-send-email-akash.goel@intel.com>
On 15/08/16 15:49, akash.goel@intel.com wrote:
> From: Sagar Arun Kamble <sagar.a.kamble@intel.com>
>
> This patch provides debugfs interface i915_guc_output_control for
> on the fly enabling/disabling of logging in GuC firmware and controlling
> the verbosity level of logs.
> The value written to the file, should have bit 0 set to enable logging and
> bits 4-7 should contain the verbosity info.
>
> v2: Add a forceful flush, to collect left over logs, on disabling logging.
> Useful for Validation.
>
> v3: Besides minor cleanup, implement read method for the debugfs file and
> set the guc_log_level to -1 when logging is disabled. (Tvrtko)
>
> v4: Minor cleanup & rebase. (Tvrtko)
>
> Signed-off-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> Signed-off-by: Akash Goel <akash.goel@intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 44 ++++++++++++++++++++-
> drivers/gpu/drm/i915/i915_guc_submission.c | 62 ++++++++++++++++++++++++++++++
> drivers/gpu/drm/i915/intel_guc.h | 1 +
> 3 files changed, 106 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index aaa51bc..bfc22bf 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -2626,6 +2626,47 @@ static int i915_guc_log_dump(struct seq_file *m, void *data)
> return 0;
> }
>
> +static int i915_guc_log_control_get(void *data, u64 *val)
> +{
> + struct drm_device *dev = data;
> + struct drm_i915_private *dev_priv = to_i915(dev);
> +
> + if (!dev_priv->guc.log.vma)
> + return -EINVAL;
> +
> + *val = i915.guc_log_level;
> +
> + return 0;
> +}
> +
> +static int i915_guc_log_control_set(void *data, u64 val)
> +{
> + struct drm_device *dev = data;
> + struct drm_i915_private *dev_priv = to_i915(dev);
> + int ret;
> +
> + ret = mutex_lock_interruptible(&dev->struct_mutex);
> + if (ret)
> + return ret;
> +
> + if (!dev_priv->guc.log.vma) {
> + ret = -EINVAL;
> + goto end;
> + }
> +
> + intel_runtime_pm_get(dev_priv);
> + ret = i915_guc_log_control(dev_priv, val);
> + intel_runtime_pm_put(dev_priv);
> +
> +end:
> + mutex_unlock(&dev->struct_mutex);
> + return ret;
> +}
> +
> +DEFINE_SIMPLE_ATTRIBUTE(i915_guc_log_control_fops,
> + i915_guc_log_control_get, i915_guc_log_control_set,
> + "%lld\n");
> +
> static int i915_edp_psr_status(struct seq_file *m, void *data)
> {
> struct drm_info_node *node = m->private;
> @@ -5436,7 +5477,8 @@ static const struct i915_debugfs_files {
> {"i915_fbc_false_color", &i915_fbc_fc_fops},
> {"i915_dp_test_data", &i915_displayport_test_data_fops},
> {"i915_dp_test_type", &i915_displayport_test_type_fops},
> - {"i915_dp_test_active", &i915_displayport_test_active_fops}
> + {"i915_dp_test_active", &i915_displayport_test_active_fops},
> + {"i915_guc_log_control", &i915_guc_log_control_fops}
> };
>
> void intel_display_crc_init(struct drm_device *dev)
> diff --git a/drivers/gpu/drm/i915/i915_guc_submission.c b/drivers/gpu/drm/i915/i915_guc_submission.c
> index 85df2f3..be6c727 100644
> --- a/drivers/gpu/drm/i915/i915_guc_submission.c
> +++ b/drivers/gpu/drm/i915/i915_guc_submission.c
> @@ -195,6 +195,16 @@ static int host2guc_force_logbuffer_flush(struct intel_guc *guc)
> return host2guc_action(guc, data, 2);
> }
>
> +static int host2guc_logging_control(struct intel_guc *guc, u32 control_val)
> +{
> + u32 data[2];
> +
> + data[0] = HOST2GUC_ACTION_UK_LOG_ENABLE_LOGGING;
> + data[1] = control_val;
> +
> + return host2guc_action(guc, data, 2);
> +}
> +
> /*
> * Initialise, update, or clear doorbell data shared with the GuC
> *
> @@ -1585,3 +1595,55 @@ void i915_guc_register(struct drm_i915_private *dev_priv)
> guc_log_late_setup(&dev_priv->guc);
> mutex_unlock(&dev_priv->drm.struct_mutex);
> }
> +
> +int i915_guc_log_control(struct drm_i915_private *dev_priv, u64 control_val)
> +{
> + union guc_log_control log_param;
> + int ret;
> +
> + log_param.value = control_val;
> +
> + if (log_param.verbosity < GUC_LOG_VERBOSITY_MIN ||
> + log_param.verbosity > GUC_LOG_VERBOSITY_MAX)
> + return -EINVAL;
> +
> + /* This combination doesn't make sense & won't have any effect */
> + if (!log_param.logging_enabled && (i915.guc_log_level < 0))
> + return 0;
> +
> + ret = host2guc_logging_control(&dev_priv->guc, log_param.value);
> + if (ret < 0) {
> + DRM_DEBUG_DRIVER("host2guc action failed %d\n", ret);
> + return ret;
> + }
> +
> + i915.guc_log_level = log_param.verbosity;
> +
> + /* If log_level was set as -1 at boot time, then the relay channel file
> + * wouldn't have been created by now and interrupts also would not have
> + * been enabled.
> + */
> + if (!dev_priv->guc.log.relay_chan) {
> + ret = guc_log_late_setup(&dev_priv->guc);
> + if (!ret)
> + gen9_enable_guc_interrupts(dev_priv);
> + } else if (!log_param.logging_enabled) {
> + /* Once logging is disabled, GuC won't generate logs & send an
> + * interrupt. But there could be some data in the log buffer
> + * which is yet to be captured. So request GuC to update the log
> + * buffer state and then collect the left over logs.
> + */
> + i915_guc_flush_logs(dev_priv, true);
> +
> + /* GuC would have updated log buffer by now, so capture it */
> + i915_guc_capture_logs(dev_priv);
> +
> + /* As logging is disabled, update log level to reflect that */
> + i915.guc_log_level = -1;
> + } else {
> + /* In case interrupts were disabled, enable them now */
> + gen9_enable_guc_interrupts(dev_priv);
> + }
> +
> + return ret;
> +}
> diff --git a/drivers/gpu/drm/i915/intel_guc.h b/drivers/gpu/drm/i915/intel_guc.h
> index d7eda42..b56fe24 100644
> --- a/drivers/gpu/drm/i915/intel_guc.h
> +++ b/drivers/gpu/drm/i915/intel_guc.h
> @@ -185,5 +185,6 @@ void i915_guc_capture_logs(struct drm_i915_private *dev_priv);
> void i915_guc_flush_logs(struct drm_i915_private *dev_priv, bool can_wait);
> void i915_guc_register(struct drm_i915_private *dev_priv);
> void i915_guc_unregister(struct drm_i915_private *dev_priv);
> +int i915_guc_log_control(struct drm_i915_private *dev_priv, u64 control_val);
>
> #endif
>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-15 16:03 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 14:49 [PATCH v6 00/18] Support for sustained capturing of GuC firmware logs akash.goel
2016-08-15 14:49 ` [PATCH 01/18] drm/i915: Decouple GuC log setup from verbosity parameter akash.goel
2016-08-15 14:49 ` [PATCH 02/18] drm/i915: Add GuC ukernel logging related fields to fw interface file akash.goel
2016-08-15 14:49 ` [PATCH 03/18] drm/i915: New structure to contain GuC logging related fields akash.goel
2016-08-15 14:49 ` [PATCH 04/18] drm/i915: Add low level set of routines for programming PM IER/IIR/IMR register set akash.goel
2016-08-15 14:49 ` [PATCH 05/18] drm/i915: Support for GuC interrupts akash.goel
2016-08-15 14:54 ` Tvrtko Ursulin
2016-08-15 14:49 ` [PATCH 06/18] drm/i915: Handle log buffer flush interrupt event from GuC akash.goel
2016-08-15 15:20 ` Tvrtko Ursulin
2016-08-15 15:57 ` Goel, Akash
2016-08-15 16:06 ` Chris Wilson
2016-08-15 16:46 ` Goel, Akash
2016-08-15 16:56 ` Chris Wilson
2016-08-16 5:37 ` Goel, Akash
2016-08-15 14:49 ` [PATCH 07/18] relay: Use per CPU constructs for the relay channel buffer pointers akash.goel
2016-08-15 14:49 ` [PATCH 08/18] drm/i915: Add a relay backed debugfs interface for capturing GuC logs akash.goel
2016-08-15 15:29 ` Tvrtko Ursulin
2016-08-15 16:02 ` Goel, Akash
2016-08-15 16:09 ` Chris Wilson
2016-08-15 16:12 ` Chris Wilson
2016-08-15 16:38 ` Goel, Akash
2016-08-15 16:47 ` Chris Wilson
2016-08-15 14:49 ` [PATCH 09/18] drm/i915: New lock to serialize the Host2GuC actions akash.goel
2016-08-15 14:49 ` [PATCH 10/18] drm/i915: Add stats for GuC log buffer flush interrupts akash.goel
2016-08-15 14:49 ` [PATCH 11/18] drm/i915: Optimization to reduce the sampling time of GuC log buffer akash.goel
2016-08-15 15:36 ` Tvrtko Ursulin
2016-08-15 16:13 ` Goel, Akash
2016-08-15 14:49 ` [PATCH 12/18] drm/i915: Increase GuC log buffer size to reduce flush interrupts akash.goel
2016-08-15 14:49 ` [PATCH 13/18] drm/i915: Augment i915 error state to include the dump of GuC log buffer akash.goel
2016-08-15 15:39 ` Tvrtko Ursulin
2016-08-15 14:49 ` [PATCH 14/18] drm/i915: Forcefully flush GuC log buffer on reset akash.goel
2016-08-15 15:48 ` Tvrtko Ursulin
2016-08-16 5:25 ` Goel, Akash
2016-08-16 9:25 ` Tvrtko Ursulin
2016-08-16 9:39 ` Goel, Akash
2016-08-16 9:42 ` Tvrtko Ursulin
2016-08-16 11:27 ` Tvrtko Ursulin
2016-08-16 12:19 ` Goel, Akash
2016-08-15 14:49 ` [PATCH 15/18] drm/i915: Debugfs support for GuC logging control akash.goel
2016-08-15 16:03 ` Tvrtko Ursulin [this message]
2016-08-15 14:49 ` [PATCH 16/18] drm/i915: Use uncached(WC) mapping for acessing the GuC log buffer akash.goel
2016-08-15 14:49 ` [PATCH 17/18] drm/i915: Use SSE4.1 movntdqa based memcpy for sampling " akash.goel
2016-08-15 14:49 ` [PATCH 18/18] drm/i915: Early creation of relay channel for capturing boot time logs akash.goel
2016-08-15 15:59 ` Tvrtko Ursulin
2016-08-15 15:10 ` ✗ Ro.CI.BAT: failure for Support for sustained capturing of GuC firmware logs (rev7) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2016-09-08 10:39 [PATCH v9 00/18] Support for sustained capturing of GuC firmware logs akash.goel
2016-09-08 10:39 ` [PATCH 15/18] drm/i915: Debugfs support for GuC logging control akash.goel
2016-10-12 16:24 [PATCH v10 00/18] Support for sustained capturing of GuC firmware logs akash.goel
2016-10-12 16:24 ` [PATCH 15/18] drm/i915: Debugfs support for GuC logging control akash.goel
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=57B1E7CD.5000709@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=akash.goel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox