From: Mario Limonciello <mario.limonciello@amd.com>
To: Samuel Zhang <guoqing.zhang@amd.com>,
alexander.deucher@amd.com, christian.koenig@amd.com,
rafael@kernel.org, len.brown@intel.com, pavel@kernel.org,
gregkh@linuxfoundation.org, dakr@kernel.org, airlied@gmail.com,
simona@ffwll.ch, ray.huang@amd.com, matthew.auld@intel.com,
matthew.brost@intel.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de
Cc: lijo.lazar@amd.com, victor.zhao@amd.com, haijun.chang@amd.com,
Qing.Ma@amd.com, Owen.Zhang2@amd.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v5 5/5] drm/amdgpu: do not resume device in thaw for normal hibernation
Date: Wed, 9 Jul 2025 15:50:32 -0400 [thread overview]
Message-ID: <6963322b-d4e2-4d4d-b4b6-e2c44d49a94b@amd.com> (raw)
In-Reply-To: <20250709100512.3762063-6-guoqing.zhang@amd.com>
On 7/9/2025 6:05 AM, Samuel Zhang wrote:
> For normal hibernation, GPU do not need to be resumed in thaw since it is
> not involved in writing the hibernation image. Skip resume in this case
> can reduce the hibernation time.
>
> On VM with 8 * 192GB VRAM dGPUs, 98% VRAM usage and 1.7TB system memory,
> this can save 50 minutes.
>
> Signed-off-by: Samuel Zhang <guoqing.zhang@amd.com>
I hand modified the patches for other changes missing from linux-next in
your base.
I checked on an APU with an eDP display connected and from a VT
hibernate does keep the display off now so this is definitely an
improvement there too.
Tested-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> index 4f8632737574..b24c420983ef 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> @@ -2541,6 +2541,10 @@ amdgpu_pci_shutdown(struct pci_dev *pdev)
> if (amdgpu_ras_intr_triggered())
> return;
>
> + /* device maybe not resumed here, return immediately in this case */
> + if (adev->in_s4 && adev->in_suspend)
> + return;
> +
> /* if we are running in a VM, make sure the device
> * torn down properly on reboot/shutdown.
> * unfortunately we can't detect certain
> @@ -2557,6 +2561,10 @@ static int amdgpu_pmops_prepare(struct device *dev)
> struct drm_device *drm_dev = dev_get_drvdata(dev);
> struct amdgpu_device *adev = drm_to_adev(drm_dev);
>
> + /* device maybe not resumed here, return immediately in this case */
> + if (adev->in_s4 && adev->in_suspend)
> + return 0;
> +
Is this one right? Don't we still want to call prepare() for all the HW
IP blocks? The eviction call that happens in prepare() is a no-op but
there are other IP blocks with an prepare_suspend() callback like DCN.
That is I think you're destroying the optimization from commit
50e0bae34fa6b ("drm/amd/display: Add and use new dm_prepare_suspend()
callback") by adding this code here.
> /* Return a positive number here so
> * DPM_FLAG_SMART_SUSPEND works properly
> */
> @@ -2655,12 +2663,21 @@ static int amdgpu_pmops_thaw(struct device *dev)
> {
> struct drm_device *drm_dev = dev_get_drvdata(dev);
>
> + /* do not resume device if it's normal hibernation */
> + if (!pm_hibernate_is_recovering())
> + return 0;
> +
> return amdgpu_device_resume(drm_dev, true);
> }
>
> static int amdgpu_pmops_poweroff(struct device *dev)
> {
> struct drm_device *drm_dev = dev_get_drvdata(dev);
> + struct amdgpu_device *adev = drm_to_adev(drm_dev);
> +
> + /* device maybe not resumed here, return immediately in this case */
> + if (adev->in_s4 && adev->in_suspend)
> + return 0;
>
> return amdgpu_device_suspend(drm_dev, true);
> }
next prev parent reply other threads:[~2025-07-09 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 10:05 [PATCH v5 0/5] reduce system memory requirement for hibernation Samuel Zhang
2025-07-09 10:05 ` [PATCH v5 1/5] drm/ttm: add new api ttm_device_prepare_hibernation() Samuel Zhang
2025-07-09 16:41 ` Mario Limonciello
2025-07-09 10:05 ` [PATCH v5 2/5] drm/amdgpu: move GTT to shmem after eviction for hibernation Samuel Zhang
2025-07-09 10:05 ` [PATCH v5 3/5] PM: hibernate: shrink shmem pages after dev_pm_ops.prepare() Samuel Zhang
2025-07-09 16:08 ` Mario Limonciello
2025-07-09 10:05 ` [PATCH v5 4/5] PM: hibernate: add new api pm_hibernate_is_recovering() Samuel Zhang
2025-07-09 10:14 ` Rafael J. Wysocki
2025-07-09 16:11 ` Mario Limonciello
2025-07-09 10:05 ` [PATCH v5 5/5] drm/amdgpu: do not resume device in thaw for normal hibernation Samuel Zhang
2025-07-09 19:50 ` Mario Limonciello [this message]
2025-07-10 4:18 ` Lazar, Lijo
2025-07-10 6:18 ` Zhang, GuoQing (Sam)
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=6963322b-d4e2-4d4d-b4b6-e2c44d49a94b@amd.com \
--to=mario.limonciello@amd.com \
--cc=Owen.Zhang2@amd.com \
--cc=Qing.Ma@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=guoqing.zhang@amd.com \
--cc=haijun.chang@amd.com \
--cc=len.brown@intel.com \
--cc=lijo.lazar@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=victor.zhao@amd.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