From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Dave Gordon <david.s.gordon@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 3/5] drm/i915/guc: don't spinwait if the GuC's workqueue is full
Date: Fri, 29 Apr 2016 16:17:00 +0100 [thread overview]
Message-ID: <57237AEC.5080308@linux.intel.com> (raw)
In-Reply-To: <1461780195-17434-3-git-send-email-david.s.gordon@intel.com>
On 27/04/16 19:03, Dave Gordon wrote:
> Rather than wait to see whether more space becomes available in the GuC
> submission workqueue, we can just return -EAGAIN and let the caller try
> again in a little while. This gets rid of an uninterruptable sleep in
> the polling code :)
>
> We'll also add a counter to the GuC client statistics, to see how often
> we find the WQ full.
>
> Signed-off-by: Dave Gordon <david.s.gordon@intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 1 +
> drivers/gpu/drm/i915/i915_guc_submission.c | 16 +++++-----------
> drivers/gpu/drm/i915/intel_guc.h | 8 ++++----
> 3 files changed, 10 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 8b8d6f0..1024947 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -2509,6 +2509,7 @@ static void i915_guc_client_info(struct seq_file *m,
> seq_printf(m, "\tWQ size %d, offset: 0x%x, tail %d\n",
> client->wq_size, client->wq_offset, client->wq_tail);
>
> + seq_printf(m, "\tWork queue full: %u\n", client->no_wq_space);
> seq_printf(m, "\tFailed to queue: %u\n", client->q_fail);
> seq_printf(m, "\tFailed doorbell: %u\n", client->b_fail);
> seq_printf(m, "\tLast submission result: %d\n", client->retcode);
> diff --git a/drivers/gpu/drm/i915/i915_guc_submission.c b/drivers/gpu/drm/i915/i915_guc_submission.c
> index 66af5ce..6626eff 100644
> --- a/drivers/gpu/drm/i915/i915_guc_submission.c
> +++ b/drivers/gpu/drm/i915/i915_guc_submission.c
> @@ -453,27 +453,21 @@ static void guc_fini_ctx_desc(struct intel_guc *guc,
>
> int i915_guc_wq_check_space(struct drm_i915_gem_request *request)
> {
> - const size_t size = sizeof(struct guc_wq_item);
> + const size_t wqi_size = sizeof(struct guc_wq_item);
> struct i915_guc_client *gc = request->i915->guc.execbuf_client;
> struct guc_process_desc *desc;
> - int ret = -ETIMEDOUT, timeout_counter = 200;
>
> if (!gc)
> return 0;
Not part of this patch but spotted it - can this really happen, and if
so, does it warrant a WARN_ONCE, GEM_BUG_ON or something?
>
> desc = gc->client_base + gc->proc_desc_offset;
>
> - while (timeout_counter-- > 0) {
> - if (CIRC_SPACE(gc->wq_tail, desc->head, gc->wq_size) >= size) {
> - ret = 0;
> - break;
> - }
> + if (CIRC_SPACE(gc->wq_tail, desc->head, gc->wq_size) >= wqi_size)
> + return 0;
Could stick a likely here to lay out the code for the expected case but
it could be just OCD. :)
>
> - if (timeout_counter)
> - usleep_range(1000, 2000);
> - };
> + gc->no_wq_space += 1;
>
> - return ret;
> + return -EAGAIN;
I suppose it is OK to make userspace pay the cost since this should be
extremely rare, correct?
> }
>
> static int guc_add_workqueue_item(struct i915_guc_client *gc,
> diff --git a/drivers/gpu/drm/i915/intel_guc.h b/drivers/gpu/drm/i915/intel_guc.h
> index b37c731..436f2d6 100644
> --- a/drivers/gpu/drm/i915/intel_guc.h
> +++ b/drivers/gpu/drm/i915/intel_guc.h
> @@ -73,10 +73,10 @@ struct i915_guc_client {
>
> /* GuC submission statistics & status */
> uint64_t submissions[GUC_MAX_ENGINES_NUM];
> - uint32_t q_fail;
> - uint32_t b_fail;
> - int retcode;
> - int spare; /* pad to 32 DWords */
> + uint32_t no_wq_space; /* Space pre-check failed */
> + uint32_t q_fail; /* Failed to queue (MBZ) */
> + uint32_t b_fail; /* Doorbell failure (MBZ) */
> + int retcode; /* Result of last guc_submit() */
> };
>
> enum intel_guc_fw_status {
>
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-04-29 15:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 18:03 [PATCH v2 1/5] drm/i915/guc: add enable_guc_loading parameter Dave Gordon
2016-04-27 18:03 ` [PATCH v2 2/5] drm/i915/guc: pass request (not client) to i915_guc_{wq_check_space, submit}() Dave Gordon
2016-04-29 15:08 ` Tvrtko Ursulin
2016-05-03 19:22 ` Dave Gordon
2016-05-04 8:33 ` Tvrtko Ursulin
2016-04-27 18:03 ` [PATCH v2 3/5] drm/i915/guc: don't spinwait if the GuC's workqueue is full Dave Gordon
2016-04-29 15:17 ` Tvrtko Ursulin [this message]
2016-05-06 17:12 ` Dave Gordon
2016-04-29 15:45 ` Tvrtko Ursulin
2016-05-06 15:17 ` Dave Gordon
2016-05-10 14:44 ` Tvrtko Ursulin
2016-04-27 18:03 ` [PATCH v2 4/5] drm/i915/guc: rework guc_add_workqueue_item() Dave Gordon
2016-04-29 15:44 ` Tvrtko Ursulin
2016-04-29 16:10 ` Chris Wilson
2016-05-03 10:26 ` Tvrtko Ursulin
2016-05-05 18:38 ` Dave Gordon
2016-05-06 8:55 ` Tvrtko Ursulin
2016-05-06 15:06 ` Dave Gordon
2016-04-27 18:03 ` [PATCH v2 5/5] DO NOT MERGE: change default to using GuC submission if possible Dave Gordon
2016-04-28 6:24 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/5] drm/i915/guc: add enable_guc_loading parameter Patchwork
2016-04-29 15:03 ` [PATCH v2 1/5] " Tvrtko Ursulin
2016-05-06 16:39 ` Dave Gordon
2016-05-10 14:37 ` Tvrtko Ursulin
2016-05-13 14:36 ` Dave Gordon
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=57237AEC.5080308@linux.intel.com \
--to=tvrtko.ursulin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox