All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Xin Wang <x.wang@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <karthik.poosa@intel.com>,
	<james.xiong@intel.com>, <stuart.summers@intel.com>,
	<shuicheng.lin@intel.com>
Subject: Re: [PATCH 2/2] drm/xe: Ensure GT is in C0 during resumes
Date: Fri, 22 Aug 2025 16:17:54 -0400	[thread overview]
Message-ID: <aKjQcpFAIN1ojvSX@intel.com> (raw)
In-Reply-To: <20250822195340.1246075-3-x.wang@intel.com>

On Fri, Aug 22, 2025 at 12:53:40PM -0700, Xin Wang wrote:
> This patch ensures the gt will be awake for the entire duration
> of the resume sequences until GuCRC takes over and GT-C6 gets
> re-enabled.

Differently of the previous patch this tells what, but doesn't tell why.
Perhaps we should add:

Before suspending GT-C6 is kept enabled, but upon resume, GuCRC
is not yet alive to properly control the exits and some cases of
instability and corruption related to GT-C6 can be observed.

Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/4037

> Suggested-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Xin Wang <x.wang@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_pm.c | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> index 51934d5dc44f..a2e85030b7f4 100644
> --- a/drivers/gpu/drm/xe/xe_pm.c
> +++ b/drivers/gpu/drm/xe/xe_pm.c
> @@ -18,7 +18,7 @@
>  #include "xe_device.h"
>  #include "xe_ggtt.h"
>  #include "xe_gt.h"
> -#include "xe_guc.h"
> +#include "xe_gt_idle.h"
>  #include "xe_i2c.h"
>  #include "xe_irq.h"
>  #include "xe_pcode.h"
> @@ -177,6 +177,9 @@ int xe_pm_resume(struct xe_device *xe)
>  	drm_dbg(&xe->drm, "Resuming device\n");
>  	trace_xe_pm_resume(xe, __builtin_return_address(0));
>  
> +	for_each_gt(gt, xe, id)
> +		xe_gt_idle_disable_c6(gt);
> +
>  	for_each_tile(tile, xe, id)
>  		xe_wa_apply_tile_workarounds(tile);
>  
> @@ -533,6 +536,9 @@ int xe_pm_runtime_resume(struct xe_device *xe)
>  
>  	xe_rpm_lockmap_acquire(xe);
>  
> +	for_each_gt(gt, xe, id)
> +		xe_gt_idle_disable_c6(gt);
> +
>  	if (xe->d3cold.allowed) {
>  		err = xe_pcode_ready(xe, true);
>  		if (err)
> -- 
> 2.43.0
> 

  reply	other threads:[~2025-08-22 20:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22 19:53 [PATCH 0/2] Ensure GT is in C0 during resumes Xin Wang
2025-08-22 19:53 ` [PATCH 1/2] drm/xe: make xe_gt_idle_disable_c6() handle the forcewake internally Xin Wang
2025-08-22 20:13   ` Rodrigo Vivi
2025-08-22 21:26   ` Lin, Shuicheng
2025-08-22 19:53 ` [PATCH 2/2] drm/xe: Ensure GT is in C0 during resumes Xin Wang
2025-08-22 20:17   ` Rodrigo Vivi [this message]
2025-08-22 20:01 ` ✓ CI.KUnit: success for " Patchwork
2025-08-22 20:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-08-23 10:24 ` ✗ Xe.CI.Full: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-08-25 16:57 [PATCH 0/2] " Xin Wang
2025-08-25 16:57 ` [PATCH 2/2] drm/xe: " Xin Wang
2025-08-25 18:19   ` Rodrigo Vivi
2025-08-27  0:06 [PATCH 0/2] " Xin Wang
2025-08-27  0:06 ` [PATCH 2/2] drm/xe: " Xin Wang
2025-09-04 13:45   ` Poosa, Karthik

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=aKjQcpFAIN1ojvSX@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=james.xiong@intel.com \
    --cc=karthik.poosa@intel.com \
    --cc=shuicheng.lin@intel.com \
    --cc=stuart.summers@intel.com \
    --cc=x.wang@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.