All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "Gupta, Anshuman" <anshuman.gupta@intel.com>,
	"Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/gsc: Fix the Driver-FLR completion
Date: Thu, 23 Feb 2023 21:48:00 +0000	[thread overview]
Message-ID: <d3cc0c080892df52d0a99471335e3135645a4aa7.camel@intel.com> (raw)
In-Reply-To: <20230222210120.407780-1-alan.previn.teres.alexis@intel.com>

On Wed, 2023-02-22 at 13:01 -0800, Teres Alexis, 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)
> 
> 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 */

So i got offline feedback from Daniele during internal reviews before this went upstream that a runtime-pm
ought to be taken, although not required functionally speaking during unload, should be there
so we don't get complains from uncore when hitting up those registers. I'll recheck with Daniele.

alan:snip

WARNING: multiple messages have this Message-ID (diff)
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gsc: Fix the Driver-FLR completion
Date: Thu, 23 Feb 2023 21:48:00 +0000	[thread overview]
Message-ID: <d3cc0c080892df52d0a99471335e3135645a4aa7.camel@intel.com> (raw)
In-Reply-To: <20230222210120.407780-1-alan.previn.teres.alexis@intel.com>

On Wed, 2023-02-22 at 13:01 -0800, Teres Alexis, 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)
> 
> 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 */

So i got offline feedback from Daniele during internal reviews before this went upstream that a runtime-pm
ought to be taken, although not required functionally speaking during unload, should be there
so we don't get complains from uncore when hitting up those registers. I'll recheck with Daniele.

alan:snip

  parent reply	other threads:[~2023-02-23 21:48 UTC|newest]

Thread overview: 14+ 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-22 21:01 ` [Intel-gfx] " Alan Previn
2023-02-22 21:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-02-22 23:16 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-02-23  1:41 ` [Intel-gfx] [PATCH] " Belgaumkar, Vinay
2023-02-23 21:48 ` Teres Alexis, Alan Previn [this message]
2023-02-23 21:48   ` Teres Alexis, Alan Previn
2023-02-23 23:49 ` Ceraolo Spurio, Daniele
2023-02-23 23:49   ` [Intel-gfx] " Ceraolo Spurio, Daniele
2023-02-24  0:05   ` Teres Alexis, Alan Previn
2023-02-24  0:05     ` [Intel-gfx] " Teres Alexis, Alan Previn
2023-02-23 22:04 Alan Previn
2023-02-23 23:35 ` Ceraolo Spurio, Daniele
2023-02-24  0:17 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=d3cc0c080892df52d0a99471335e3135645a4aa7.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=daniele.ceraolospurio@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 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.