From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
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: victor.zhao@amd.com, haijun.chang@amd.com, Qing.Ma@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 v2 5/5] drm/amdgpu: do not resume device in thaw for normal hibernation
Date: Mon, 7 Jul 2025 07:58:27 +0530 [thread overview]
Message-ID: <5f944f42-d631-4435-985f-c47944f770bd@amd.com> (raw)
In-Reply-To: <c847783d-eb92-49aa-919c-447cbc34baed@amd.com>
On 7/7/2025 2:04 AM, Mario Limonciello wrote:
> On 7/4/2025 6:12 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.
>
> Since you have the measurements would you mind including them in the
> commit message for reference?
>
>>
>> For cancelled hibernation, GPU need to be resumed.
>
> If I'm following right you are actually handling two different things in
> this patch aren't you?
>
> 1) A change in thaw() to only resume on aborted hibernation
> 2) A change in shutdown() to skip running if the in s4 when shutdown()
> is called.
>
> So I think it would be more logical to split this into two patches.
>
This is doing only one thing - Keep the device in suspended state for
thaw() operation during a successful hibernation. Splitting into two
could break hibernation during integration of the first part - it will
attempt another suspend during shutdown. I think we don't take care of
consecutive suspend calls.
Thanks,
Lijo
>>
>> Signed-off-by: Samuel Zhang <guoqing.zhang@amd.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c b/drivers/gpu/
>> drm/amd/amdgpu/amdgpu_drv.c
>> index 4f8632737574..e064816aae4d 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
>> @@ -2655,6 +2659,10 @@ static int amdgpu_pmops_thaw(struct device *dev)
>> {
>> struct drm_device *drm_dev = dev_get_drvdata(dev);
>> + /* do not resume device for normal hibernation */
>> + if (pm_transition.event == PM_EVENT_THAW)
>> + return 0;
>> +
>
> Without digging into pm.h documentation I think it's not going to be
> very obvious next time we look at this code that amdgpu_device_resume()
> is only intended for the aborted case.
>
> How would you feel about a switch/case?
>
> Something like this:
>
> switch (pm_transition.event) {
> /* normal hibernation */
> case PM_EVENT_THAW:
> return 0;
> /* for aborted hibernation */
> case PM_EVENT_RECOVER:
> return amdgpu_device_resume(drm_dev, true);
> default:
> return -EOPNOTSUP;
> }
>
>
>> return amdgpu_device_resume(drm_dev, true);
>> }
>>
>
next prev parent reply other threads:[~2025-07-07 2:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 10:12 [PATCH v2 0/5] reduce system memory requirement for hibernation Samuel Zhang
2025-07-04 10:12 ` [PATCH v2 1/5] drm/ttm: add ttm_device_prepare_hibernation() api Samuel Zhang
2025-07-06 20:44 ` Mario Limonciello
2025-07-07 0:48 ` Matthew Brost
2025-07-07 9:13 ` Christian König
2025-07-04 10:12 ` [PATCH v2 2/5] drm/amdgpu: move GTT to shmem after eviction for hibernation Samuel Zhang
2025-07-06 20:41 ` Mario Limonciello
2025-07-07 9:16 ` Christian König
2025-07-04 10:12 ` [PATCH v2 3/5] PM: hibernate: shrink shmem pages after dev_pm_ops.prepare() Samuel Zhang
2025-07-07 18:45 ` Rafael J. Wysocki
2025-07-04 10:12 ` [PATCH v2 4/5] PM: hibernate: export variable pm_transition Samuel Zhang
2025-07-06 20:40 ` Mario Limonciello
2025-07-07 19:17 ` Rafael J. Wysocki
2025-07-04 10:12 ` [PATCH v2 5/5] drm/amdgpu: do not resume device in thaw for normal hibernation Samuel Zhang
2025-07-06 20:34 ` Mario Limonciello
2025-07-07 2:28 ` Lazar, Lijo [this message]
2025-07-07 2:29 ` Mario Limonciello
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=5f944f42-d631-4435-985f-c47944f770bd@amd.com \
--to=lijo.lazar@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=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mario.limonciello@amd.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
all inboxes | Powered by JetHome®