From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915/guc: sleep on enable
Date: Mon, 15 Oct 2018 11:33:26 -0700 [thread overview]
Message-ID: <19e1444b-5ff1-5ade-189c-4694b45dfd0f@intel.com> (raw)
In-Reply-To: <20181014170202.3869-3-chris@chris-wilson.co.uk>
On 14/10/18 10:02, Chris Wilson wrote:
> Seems like there's a missing ack before the guc is ready for commands.
>
I'm assuming you're running without HuC since the HuC auth H2G comes
before this one.
What we're polling to indicate load completion (GS_UKERNEL_READY) is
definitely what the firmware uses to signal readiness. The other check
we do (GS_MIA_CORE_STATE) should only apply for rc6 scenarios. From what
I can see from the firmware code, all the initialization steps are done
before GS_UKERNEL_READY is written to the status register so there
shouldn't be any missing acks in principle.
Is the GuC returning anything in the scratch 0 register? It should be
printed out by the H2G error message. The value of the status register
(0xc000) could also provide interesting debug info.
Thanks,
Daniele
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> ---
> drivers/gpu/drm/i915/intel_guc_submission.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_guc_submission.c b/drivers/gpu/drm/i915/intel_guc_submission.c
> index fb0499f80b62..b7fd3422cb28 100644
> --- a/drivers/gpu/drm/i915/intel_guc_submission.c
> +++ b/drivers/gpu/drm/i915/intel_guc_submission.c
> @@ -1307,6 +1307,8 @@ int intel_guc_submission_enable(struct intel_guc *guc)
>
> GEM_BUG_ON(!guc->execbuf_client);
>
> + usleep_range(1000, 10000);
> +
> err = intel_guc_sample_forcewake(guc);
> if (err)
> return err;
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-15 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 17:02 [PATCH 1/3] drm/i915/guc: Clear preempt status before use Chris Wilson
2018-10-14 17:02 ` [PATCH 2/3] guc-send Chris Wilson
2018-10-14 17:02 ` [PATCH 3/3] drm/i915/guc: sleep on enable Chris Wilson
2018-10-15 18:33 ` Daniele Ceraolo Spurio [this message]
2018-10-15 19:23 ` Chris Wilson
2018-10-15 21:41 ` Daniele Ceraolo Spurio
2018-10-14 17:09 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915/guc: Clear preempt status before use Patchwork
2018-10-14 17:10 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-10-14 17:29 ` ✗ Fi.CI.BAT: failure " 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=19e1444b-5ff1-5ade-189c-4694b45dfd0f@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=chris@chris-wilson.co.uk \
--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