From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <matthew.brost@intel.com>,
<michal.wajdeczko@intel.com>, <badal.nilawar@intel.com>,
<karthik.poosa@intel.com>, <matthew.d.roper@intel.com>,
<dev@lankhorst.se>
Subject: Re: [PATCH v1] drm/xe/pm: Handle GT resume failure
Date: Wed, 17 Dec 2025 12:25:32 -0500 [thread overview]
Message-ID: <aULnjAabXkM9jVfX@intel.com> (raw)
In-Reply-To: <20251217131909.1226331-1-raag.jadav@intel.com>
On Wed, Dec 17, 2025 at 06:49:09PM +0530, Raag Jadav wrote:
> We've been historically ignoring GT resume failure. Since the function
> can return error, handle it properly.
I probably had a reason for it, but since I didn't document and
cannot remember it, let's go forward and make the clean flow.
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pm.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
> index 4390ba69610d..a8b50091d62e 100644
> --- a/drivers/gpu/drm/xe/xe_pm.c
> +++ b/drivers/gpu/drm/xe/xe_pm.c
> @@ -260,8 +260,11 @@ int xe_pm_resume(struct xe_device *xe)
>
> xe_irq_resume(xe);
>
> - for_each_gt(gt, xe, id)
> - xe_gt_resume(gt);
> + for_each_gt(gt, xe, id) {
> + err = xe_gt_resume(gt);
> + if (err)
> + goto err;
> + }
>
> xe_display_pm_resume(xe);
>
> @@ -656,8 +659,11 @@ int xe_pm_runtime_resume(struct xe_device *xe)
>
> xe_irq_resume(xe);
>
> - for_each_gt(gt, xe, id)
> - xe->d3cold.allowed ? xe_gt_resume(gt) : xe_gt_runtime_resume(gt);
> + for_each_gt(gt, xe, id) {
> + err = xe->d3cold.allowed ? xe_gt_resume(gt) : xe_gt_runtime_resume(gt);
> + if (err)
> + goto out;
> + }
>
> xe_display_pm_runtime_resume(xe);
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-12-17 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 13:19 [PATCH v1] drm/xe/pm: Handle GT resume failure Raag Jadav
2025-12-17 15:00 ` ✓ CI.KUnit: success for " Patchwork
2025-12-17 15:37 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-17 17:25 ` Rodrigo Vivi [this message]
2025-12-17 17:38 ` [PATCH v1] " Matt Roper
2025-12-18 11:12 ` Raag Jadav
2025-12-18 18:46 ` Matt Roper
2025-12-19 5:04 ` Raag Jadav
2025-12-19 16:08 ` Rodrigo Vivi
2025-12-19 18:00 ` Raag Jadav
2025-12-19 18:53 ` Rodrigo Vivi
2025-12-18 12:59 ` ✗ Xe.CI.Full: failure for " 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=aULnjAabXkM9jVfX@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=badal.nilawar@intel.com \
--cc=dev@lankhorst.se \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=matthew.brost@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=raag.jadav@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