Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Vinay Belgaumkar" <vinay.belgaumkar@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v5] drm/xe: Poll GT for C6 before D3
Date: Tue, 15 Sep 2026 21:20:50 +0000	[thread overview]
Message-ID: <20260915212050.8E5CB1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260915210113.2915363-1-vinay.belgaumkar@intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] drm/xe: D3cold runtime suspend always fails due to C6 check after GT PG disable
--

commit 691645f0da262033183939383983163842757c50
Author: Vinay Belgaumkar <vinay.belgaumkar@intel.com>

drm/xe: Poll GT for C6 before D3

This commit adds a check for GT C6 state before the D3 transition in the
runtime suspend flow, aborting and resuming if the check fails.

> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> index 00b2b5dfb8f6c..488745ce0473f 100644
> --- a/drivers/gpu/drm/xe/xe_pci.c
> +++ b/drivers/gpu/drm/xe/xe_pci.c
[ ... ]
> @@ -1394,6 +1394,17 @@ static int xe_pci_runtime_suspend(struct device *dev)
>  	if (err)
>  		return err;
>  
> +	err = xe_pm_check_device_idle(xe);
> +	if (err) {
> +		drm_dbg(&xe->drm, "Resuming - Device idle check failed!");
> +		ret = xe_pm_runtime_resume(xe);

[Severity: Medium]
Will this idle check always fail when D3cold is allowed?

Looking at the sequence, xe_pci_runtime_suspend() calls
xe_pm_runtime_suspend() right before this check. When D3cold is allowed,
xe_pm_runtime_suspend() executes xe_gt_suspend():

drivers/gpu/drm/xe/xe_pm.c:xe_pm_runtime_suspend() {
...
	for_each_gt(gt, xe, id) {
		err = xe->d3cold.allowed ? xe_gt_suspend(gt) : xe_gt_runtime_suspend(gt);
...
}

xe_gt_suspend() then prepares the GT for power removal by explicitly disabling
power gating:

drivers/gpu/drm/xe/xe_gt.c:xe_gt_suspend() {
...
	xe_gt_idle_disable_pg(gt);
...
}

Because xe_gt_idle_disable_pg() writes 0 to the POWERGATE_ENABLE register,
the hardware is prevented from entering the C6 power gating state. Won't
the subsequent poll for GT_IDLE_C6 in xe_pm_check_device_idle() always
timeout and return -EAGAIN, causing the device to constantly abort suspend
and immediately resume?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260915210113.2915363-1-vinay.belgaumkar@intel.com?part=1

  parent reply	other threads:[~2026-09-15 21:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 21:01 [PATCH v5] drm/xe: Poll GT for C6 before D3 Vinay Belgaumkar
2026-09-15 21:14 ` ✓ CI.KUnit: success for drm/xe: Poll GT for C6 before D3 (rev2) Patchwork
2026-09-15 21:20 ` sashiko-bot [this message]
2026-09-16 12:21   ` [PATCH v5] drm/xe: Poll GT for C6 before D3 Rodrigo Vivi
2026-09-16 18:50     ` Belgaumkar, Vinay
2026-09-15 21:51 ` ✓ Xe.CI.BAT: success for drm/xe: Poll GT for C6 before D3 (rev2) Patchwork
2026-09-16  4:04 ` ✓ Xe.CI.FULL: " Patchwork
2026-09-16 12:19 ` [PATCH v5] drm/xe: Poll GT for C6 before D3 Rodrigo Vivi
2026-09-16 15:05   ` Belgaumkar, Vinay
2026-09-16 15:44     ` Rodrigo Vivi
2026-09-16 17:06       ` Belgaumkar, Vinay

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=20260915212050.8E5CB1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vinay.belgaumkar@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