From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: akash.goel@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 18/18] drm/i915: Early creation of relay channel for capturing boot time logs
Date: Mon, 15 Aug 2016 16:59:25 +0100 [thread overview]
Message-ID: <57B1E6DD.5030905@linux.intel.com> (raw)
In-Reply-To: <1471272599-14586-19-git-send-email-akash.goel@intel.com>
On 15/08/16 15:49, akash.goel@intel.com wrote:
> From: Akash Goel <akash.goel@intel.com>
>
> As per the current i915 Driver load sequence, debugfs registration is done
> at the end and so the relay channel debugfs file is also created after that
> but the GuC firmware is loaded much earlier in the sequence.
> As a result Driver could miss capturing the boot-time logs of GuC firmware
> if there are flush interrupts from the GuC side.
> Relay has a provision to support early logging where initially only relay
> channel can be created, to have buffers for storing logs, and later on
> channel can be associated with a debugfs file at appropriate time.
> Have availed that, which allows Driver to capture boot time logs also,
> which can be collected once Userspace comes up.
>
> v2:
> - Remove the couple of FIXMEs, as now the relay channel will be created
> early before enabling the flush interrupts, so no possibility of relay
> channel pointer being modified & read at the same time from 2 different
> execution contexts.
> - Rebase.
>
> Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Akash Goel <akash.goel@intel.com>
> ---
> drivers/gpu/drm/i915/i915_guc_submission.c | 66 +++++++++++++++++++++---------
> 1 file changed, 46 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_guc_submission.c b/drivers/gpu/drm/i915/i915_guc_submission.c
> index 8733c19..34e4335 100644
> --- a/drivers/gpu/drm/i915/i915_guc_submission.c
> +++ b/drivers/gpu/drm/i915/i915_guc_submission.c
> @@ -937,13 +937,39 @@ static void guc_remove_log_relay_file(struct intel_guc *guc)
> relay_close(guc->log.relay_chan);
> }
>
> -static int guc_create_log_relay_file(struct intel_guc *guc)
> +static int guc_create_relay_channel(struct intel_guc *guc)
> {
> struct drm_i915_private *dev_priv = guc_to_i915(guc);
> struct rchan *guc_log_relay_chan;
> - struct dentry *log_dir;
> size_t n_subbufs, subbuf_size;
>
> + /* Keep the size of sub buffers same as shared log buffer */
> + subbuf_size = guc->log.vma->obj->base.size;
> +
> + /* Store up to 8 snapshots, which is large enough to buffer sufficient
> + * boot time logs and provides enough leeway to User, in terms of
> + * latency, for consuming the logs from relay. Also doesn't take
> + * up too much memory.
> + */
> + n_subbufs = 8;
> +
> + guc_log_relay_chan = relay_open(NULL, NULL, subbuf_size,
> + n_subbufs, &relay_callbacks, dev_priv);
> + if (!guc_log_relay_chan) {
> + DRM_ERROR("Couldn't create relay chan for GuC logging\n");
> + return -ENOMEM;
> + }
> +
> + guc->log.relay_chan = guc_log_relay_chan;
> + return 0;
> +}
> +
> +static int guc_create_log_relay_file(struct intel_guc *guc)
> +{
> + struct drm_i915_private *dev_priv = guc_to_i915(guc);
> + struct dentry *log_dir;
> + int ret;
> +
> /* For now create the log file in /sys/kernel/debug/dri/0 dir */
> log_dir = dev_priv->drm.primary->debugfs_root;
>
> @@ -963,25 +989,12 @@ static int guc_create_log_relay_file(struct intel_guc *guc)
> return -ENODEV;
> }
>
> - /* Keep the size of sub buffers same as shared log buffer */
> - subbuf_size = guc->log.vma->obj->base.size;
> -
> - /* Store up to 8 snapshots, which is large enough to buffer sufficient
> - * boot time logs and provides enough leeway to User, in terms of
> - * latency, for consuming the logs from relay. Also doesn't take
> - * up too much memory.
> - */
> - n_subbufs = 8;
> -
> - guc_log_relay_chan = relay_open("guc_log", log_dir, subbuf_size,
> - n_subbufs, &relay_callbacks, dev_priv);
> - if (!guc_log_relay_chan) {
> - DRM_ERROR("Couldn't create relay chan for GuC logging\n");
> - return -ENOMEM;
> + ret = relay_late_setup_files(guc->log.relay_chan, "guc_log", log_dir);
> + if (ret) {
> + DRM_ERROR("Couldn't associate relay chan with file %d\n", ret);
> + return ret;
> }
>
> - /* FIXME: Cover the update under a lock ? */
> - guc->log.relay_chan = guc_log_relay_chan;
> return 0;
> }
>
> @@ -1001,7 +1014,6 @@ static void guc_move_to_next_buf(struct intel_guc *guc)
>
> static void *guc_get_write_buffer(struct intel_guc *guc)
> {
> - /* FIXME: Cover the check under a lock ? */
> if (!guc->log.relay_chan)
> return NULL;
>
> @@ -1227,6 +1239,16 @@ static int guc_create_log_extras(struct intel_guc *guc)
> guc->log.buf_addr = vaddr;
> }
>
> + if (!guc->log.relay_chan) {
> + /* Create a relay channel, so that we have buffers for storing
> + * the GuC firmware logs, the channel will be linked with a file
> + * later on when debugfs is registered.
> + */
> + ret = guc_create_relay_channel(guc);
> + if (ret)
> + return ret;
> + }
> +
> if (!guc->log.flush_wq) {
> INIT_WORK(&guc->log.flush_work, guc_capture_logs_work);
>
> @@ -1314,6 +1336,10 @@ static int guc_log_late_setup(struct intel_guc *guc)
> if (ret)
> goto err;
>
> + /* Parent debugfs dir should be available by now, associate the already
> + * opened relay channel with a debugfs file, which will then allow User
> + * to pull the logs.
> + */
> ret = guc_create_log_relay_file(guc);
> if (ret)
> goto err;
>
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 15:59 UTC|newest]
Thread overview: 45+ 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
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 [this message]
2016-08-15 15:10 ` ✗ Ro.CI.BAT: failure for Support for sustained capturing of GuC firmware logs (rev7) 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=57B1E6DD.5030905@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