Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-xe@lists.freedesktop.org
Cc: francois.dugast@intel.com
Subject: Re: [PATCH 2/2] drm/xe: Add dbg messages on the suspend resume functions.
Date: Mon, 18 Mar 2024 18:12:44 +0000	[thread overview]
Message-ID: <8f2a95fa-2acc-46ba-8618-c7e784f69d25@intel.com> (raw)
In-Reply-To: <20240318180141.267458-2-rodrigo.vivi@intel.com>

On 18/03/2024 18:01, Rodrigo Vivi wrote:
> In case of the suspend/resume flow getting locked up we
> can get reports with some useful hints on where it might
> get locked and if that has failed.
> 
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

Makes sense. What about maybe also adding that to the rpm versions? 
Those can also be fun, and so would be useful to get hints when inside 
the callbacks.

> ---
>   drivers/gpu/drm/xe/xe_pm.c | 22 +++++++++++++++++-----
>   1 file changed, 17 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> index 9fbb6f6c598a..cc650a92c2fc 100644
> --- a/drivers/gpu/drm/xe/xe_pm.c
> +++ b/drivers/gpu/drm/xe/xe_pm.c
> @@ -80,13 +80,15 @@ int xe_pm_suspend(struct xe_device *xe)
>   	u8 id;
>   	int err;
>   
> +	drm_dbg(&xe->drm, "Suspending device\n");
> +
>   	for_each_gt(gt, xe, id)
>   		xe_gt_suspend_prepare(gt);
>   
>   	/* FIXME: Super racey... */
>   	err = xe_bo_evict_all(xe);
>   	if (err)
> -		return err;
> +		goto err;
>   
>   	xe_display_pm_suspend(xe);
>   
> @@ -94,7 +96,7 @@ int xe_pm_suspend(struct xe_device *xe)
>   		err = xe_gt_suspend(gt);
>   		if (err) {
>   			xe_display_pm_resume(xe);
> -			return err;
> +			goto err;
>   		}
>   	}
>   
> @@ -102,7 +104,11 @@ int xe_pm_suspend(struct xe_device *xe)
>   
>   	xe_display_pm_suspend_late(xe);
>   
> +	drm_dbg(&xe->drm, "Device suspended\n");
>   	return 0;
> +err:
> +	drm_dbg(&xe->drm, "Device suspend failed %d\n", err);
> +	return err;
>   }
>   
>   /**
> @@ -118,13 +124,15 @@ int xe_pm_resume(struct xe_device *xe)
>   	u8 id;
>   	int err;
>   
> +	drm_dbg(&xe->drm, "Resuming device\n");
> +
>   	for_each_tile(tile, xe, id)
>   		xe_wa_apply_tile_workarounds(tile);
>   
>   	for_each_gt(gt, xe, id) {
>   		err = xe_pcode_init(gt);
>   		if (err)
> -			return err;
> +			goto err;
>   	}
>   
>   	xe_display_pm_resume_early(xe);
> @@ -135,7 +143,7 @@ int xe_pm_resume(struct xe_device *xe)
>   	 */
>   	err = xe_bo_restore_kernel(xe);
>   	if (err)
> -		return err;
> +		goto err;
>   
>   	xe_irq_resume(xe);
>   
> @@ -146,9 +154,13 @@ int xe_pm_resume(struct xe_device *xe)
>   
>   	err = xe_bo_restore_user(xe);
>   	if (err)
> -		return err;
> +		goto err;
>   
> +	drm_dbg(&xe->drm, "Device resumed\n");
>   	return 0;
> +err:
> +	drm_dbg(&xe->drm, "Device resume failed %d\n", err);
> +	return err;
>   }
>   
>   static bool xe_pm_pci_d3cold_capable(struct xe_device *xe)

  reply	other threads:[~2024-03-18 18:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 18:01 [PATCH 1/2] drm/xe: Convert gt suspend/resume messages to debug Rodrigo Vivi
2024-03-18 18:01 ` [PATCH 2/2] drm/xe: Add dbg messages on the suspend resume functions Rodrigo Vivi
2024-03-18 18:12   ` Matthew Auld [this message]
2024-03-18 19:48     ` Rodrigo Vivi
2024-03-19  9:38       ` Matthew Auld
2024-03-19 14:23         ` Rodrigo Vivi
2024-03-19 17:05           ` Matthew Auld
2024-03-18 18:13 ` [PATCH 1/2] drm/xe: Convert gt suspend/resume messages to debug Matthew Auld
2024-03-19  0:13 ` ✓ CI.Patch_applied: success for series starting with [1/2] " Patchwork
2024-03-19  0:13 ` ✓ CI.checkpatch: " Patchwork
2024-03-19  0:14 ` ✓ CI.KUnit: " Patchwork
2024-03-19  0:24 ` ✓ CI.Build: " Patchwork
2024-03-19  0:27 ` ✓ CI.Hooks: " Patchwork
2024-03-19  0:28 ` ✓ CI.checksparse: " Patchwork
2024-03-19  0:53 ` ✗ 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=8f2a95fa-2acc-46ba-8618-c7e784f69d25@intel.com \
    --to=matthew.auld@intel.com \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@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