From: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
To: Alan Previn <alan.previn.teres.alexis@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: Vivi@freedesktop.org, Gupta@freedesktop.org,
dri-devel@lists.freedesktop.org, Rodrigo <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gsc: Fix the Driver-FLR completion
Date: Wed, 22 Feb 2023 17:41:55 -0800 [thread overview]
Message-ID: <8ff51add-8879-ca17-11e1-381e03303b39@intel.com> (raw)
In-Reply-To: <20230222210120.407780-1-alan.previn.teres.alexis@intel.com>
On 2/22/2023 1:01 PM, Alan Previn wrote:
> The Driver-FLR flow may inadvertently exit early before the full
> completion of the re-init of the internal HW state if we only poll
> GU_DEBUG Bit31 (polling for it to toggle from 0 -> 1). Instead
> we need a two-step completion wait-for-completion flow that also
> involves GU_CNTL. See the patch and new code comments for detail.
> This is new direction from HW architecture folks.
>
> v2: - Add error message for the teardown timeout (Anshuman)
> - Don't duplicate code in comments (Jani)
LGTM,
Tested-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>
> Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
> Fixes: 5a44fcd73498 ("drm/i915/gsc: Do a driver-FLR on unload if GSC was loaded")
> ---
> drivers/gpu/drm/i915/intel_uncore.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
> index f018da7ebaac..f3c46352db89 100644
> --- a/drivers/gpu/drm/i915/intel_uncore.c
> +++ b/drivers/gpu/drm/i915/intel_uncore.c
> @@ -2749,14 +2749,25 @@ static void driver_initiated_flr(struct intel_uncore *uncore)
> /* Trigger the actual Driver-FLR */
> intel_uncore_rmw_fw(uncore, GU_CNTL, 0, DRIVERFLR);
>
> + /* Wait for hardware teardown to complete */
> + ret = intel_wait_for_register_fw(uncore, GU_CNTL,
> + DRIVERFLR_STATUS, 0,
> + flr_timeout_ms);
> + if (ret) {
> + drm_err(&i915->drm, "Driver-FLR-teardown wait completion failed! %d\n", ret);
> + return;
> + }
> +
> + /* Wait for hardware/firmware re-init to complete */
> ret = intel_wait_for_register_fw(uncore, GU_DEBUG,
> DRIVERFLR_STATUS, DRIVERFLR_STATUS,
> flr_timeout_ms);
> if (ret) {
> - drm_err(&i915->drm, "wait for Driver-FLR completion failed! %d\n", ret);
> + drm_err(&i915->drm, "Driver-FLR-reinit wait completion failed! %d\n", ret);
> return;
> }
>
> + /* Clear sticky completion status */
> intel_uncore_write_fw(uncore, GU_DEBUG, DRIVERFLR_STATUS);
> }
>
next prev parent reply other threads:[~2023-02-23 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 21:01 [PATCH] drm/i915/gsc: Fix the Driver-FLR completion Alan Previn
2023-02-23 1:41 ` Belgaumkar, Vinay [this message]
2023-02-23 21:48 ` Teres Alexis, Alan Previn
2023-02-23 23:49 ` Ceraolo Spurio, Daniele
2023-02-24 0:05 ` Teres Alexis, Alan Previn
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=8ff51add-8879-ca17-11e1-381e03303b39@intel.com \
--to=vinay.belgaumkar@intel.com \
--cc=Gupta@freedesktop.org \
--cc=Vivi@freedesktop.org \
--cc=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox