All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: John Harrison <john.c.harrison@intel.com>
Cc: Intel-GFX@Lists.FreeDesktop.Org, DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/guc: Allow for very slow GuC loading
Date: Mon, 13 Mar 2023 16:55:36 -0700	[thread overview]
Message-ID: <87r0tskxzb.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <eeb90b3c-dbfe-a045-468d-9bf5456096dd@intel.com>

On Fri, 10 Mar 2023 17:01:42 -0800, John Harrison wrote:
>
> >> +	for (count = 0; count < 20; count++) {
> >> +		ret = wait_for(guc_load_done(uncore, &status, &success), 1000);
> >
> > Isn't 20 secs a bit too long for an in-place wait? I get that if the GuC
> > doesn't load (or fail to) within a few secs the HW is likely toast, but
> > still that seems a bit too long to me. What's the worst case load time
> > ever observed? I suggest reducing the wait to 3 secs as a compromise, if
> > that's bigger than the worst case.
>
> I can drop it to 3 for normal builds and keep 20 for
> CONFIG_DRM_I915_DEBUG_GEM builds. However, that won't actually be long
> enough for all slow situations. We have seen times of at least 11s when the
> GPU is running at minimum frequency. So, for CI runs we definitely want to
> keep the 20s limit. For end users? Is it better to wait for up to 20s or to
> boot in display only fallback mode? And note that this is a timeout only. A
> functional system will still complete in tens of milliseconds.

Just FYI, in this related patch:

https://patchwork.freedesktop.org/series/115003/#rev2

I am holding a mutex across GuC FW load, so very unlikely, but worst case a
thread can get blocked for the duration of the GuC reset/FW load.

Ashutosh

WARNING: multiple messages have this Message-ID (diff)
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: John Harrison <john.c.harrison@intel.com>
Cc: Intel-GFX@Lists.FreeDesktop.Org, "Ceraolo Spurio,
	Daniele" <daniele.ceraolospurio@intel.com>,
	DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/guc: Allow for very slow GuC loading
Date: Mon, 13 Mar 2023 16:55:36 -0700	[thread overview]
Message-ID: <87r0tskxzb.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <eeb90b3c-dbfe-a045-468d-9bf5456096dd@intel.com>

On Fri, 10 Mar 2023 17:01:42 -0800, John Harrison wrote:
>
> >> +	for (count = 0; count < 20; count++) {
> >> +		ret = wait_for(guc_load_done(uncore, &status, &success), 1000);
> >
> > Isn't 20 secs a bit too long for an in-place wait? I get that if the GuC
> > doesn't load (or fail to) within a few secs the HW is likely toast, but
> > still that seems a bit too long to me. What's the worst case load time
> > ever observed? I suggest reducing the wait to 3 secs as a compromise, if
> > that's bigger than the worst case.
>
> I can drop it to 3 for normal builds and keep 20 for
> CONFIG_DRM_I915_DEBUG_GEM builds. However, that won't actually be long
> enough for all slow situations. We have seen times of at least 11s when the
> GPU is running at minimum frequency. So, for CI runs we definitely want to
> keep the 20s limit. For end users? Is it better to wait for up to 20s or to
> boot in display only fallback mode? And note that this is a timeout only. A
> functional system will still complete in tens of milliseconds.

Just FYI, in this related patch:

https://patchwork.freedesktop.org/series/115003/#rev2

I am holding a mutex across GuC FW load, so very unlikely, but worst case a
thread can get blocked for the duration of the GuC reset/FW load.

Ashutosh

  reply	other threads:[~2023-03-13 23:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 23:47 [Intel-gfx] [PATCH 0/2] Improvements to GuC load failure handling John.C.Harrison
2023-02-17 23:47 ` John.C.Harrison
2023-02-17 23:47 ` [Intel-gfx] [PATCH 1/2] drm/i915/guc: Improve GuC load error reporting John.C.Harrison
2023-02-17 23:47   ` John.C.Harrison
2023-03-03 19:09   ` [Intel-gfx] " Ceraolo Spurio, Daniele
2023-02-17 23:47 ` [Intel-gfx] [PATCH 2/2] drm/i915/guc: Allow for very slow GuC loading John.C.Harrison
2023-02-17 23:47   ` John.C.Harrison
2023-03-03 19:20   ` [Intel-gfx] " Ceraolo Spurio, Daniele
2023-03-11  1:01     ` John Harrison
2023-03-13 23:55       ` Dixit, Ashutosh [this message]
2023-03-13 23:55         ` Dixit, Ashutosh
2023-03-15 21:30       ` Ceraolo Spurio, Daniele
2023-02-18  0:51 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Improvements to GuC load failure handling Patchwork
2023-02-18  1:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-02-18 14:46 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87r0tskxzb.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=DRI-Devel@Lists.FreeDesktop.Org \
    --cc=Intel-GFX@Lists.FreeDesktop.Org \
    --cc=john.c.harrison@intel.com \
    /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.