From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Samuel Zhang <guoqing.zhang@amd.com>,
"open list:RADEON and AMDGPU DRM DRIVERS"
<amd-gfx@lists.freedesktop.org>,
"open list:HIBERNATION (aka Software Suspend,
aka swsusp)" <linux-pm@vger.kernel.org>,
Ionut Nechita <ionut_n2001@yahoo.com>,
Kenneth Crudup <kenny@panix.com>
Subject: Re: [PATCH v2 1/3] PM: hibernate: Fix hybrid-sleep
Date: Thu, 25 Sep 2025 13:03:46 -0500 [thread overview]
Message-ID: <1b204004-03c1-48b5-abc3-eef5084ba680@kernel.org> (raw)
In-Reply-To: <CAJZ5v0irbKvO-tFaQWa8E0dLikN6d=y6yOxJfzQvpDVPe-TaTw@mail.gmail.com>
On 9/25/2025 12:55 PM, Rafael J. Wysocki wrote:
> On Thu, Sep 25, 2025 at 7:51 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
>>
>> On Thu, Sep 25, 2025 at 7:47 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
>>>
>>> On Thu, Sep 25, 2025 at 5:59 PM Mario Limonciello (AMD)
>>> <superm1@kernel.org> wrote:
>>>>
>>>> Hybrid sleep will hibernate the system followed by running through
>>>> the suspend routine. Since both the hibernate and the suspend routine
>>>> will call pm_restrict_gfp_mask(), pm_restore_gfp_mask() must be called
>>>> before starting the suspend sequence.
>>>>
>>>> Add an explicit call to pm_restore_gfp_mask() to power_down() before
>>>> the suspend sequence starts. Don't call pm_restore_gfp_mask() when
>>>> exiting suspend sequence it is already called:
>>>>
>>>> ```
>>>> power_down()
>>>> ->suspend_devices_and_enter()
>>>> -->dpm_resume_end()
>>>> ```
>>>>
>>>> Reported-by: Ionut Nechita <ionut_n2001@yahoo.com>
>>>> Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4573
>>>> Tested-by: Ionut Nechita <ionut_n2001@yahoo.com>
>>>> Fixes: 12ffc3b1513eb ("PM: Restrict swap use to later in the suspend sequence")
>>>> Tested-by: Kenneth Crudup <kenny@panix.com>
>>>> Acked-by: Alex Deucher <alexander.deucher@amd.com>
>>>> Signed-off-by: Mario Limonciello (AMD) <superm1@kernel.org>
>>>> ---
>>>> v2:
>>>> * Move under CONFIG_SUSPEND scope (LKP robot)
>>>> * Add tags
>>>> ---
>>>> kernel/power/hibernate.c | 11 ++++++++++-
>>>> 1 file changed, 10 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/kernel/power/hibernate.c b/kernel/power/hibernate.c
>>>> index 2f66ab4538231..52c1818749724 100644
>>>> --- a/kernel/power/hibernate.c
>>>> +++ b/kernel/power/hibernate.c
>>>> @@ -695,6 +695,7 @@ static void power_down(void)
>>>>
>>>> #ifdef CONFIG_SUSPEND
>>>> if (hibernation_mode == HIBERNATION_SUSPEND) {
>>>> + pm_restore_gfp_mask();
>>>> error = suspend_devices_and_enter(mem_sleep_current);
>>>> if (error) {
>>>> hibernation_mode = hibernation_ops ?
>>>> @@ -862,7 +863,15 @@ int hibernate(void)
>>>> power_down();
>>>> }
>>>> in_suspend = 0;
>>>> - pm_restore_gfp_mask();
>>>> + switch (hibernation_mode) {
>>>> +#ifdef CONFIG_SUSPEND
>>>> + case HIBERNATION_SUSPEND:
>>>> + break;
>>>> +#endif
>>>> + default:
>>>> + pm_restore_gfp_mask();
>>>> + break;
>>>> + }
>>>
>>> You're breaking HIBERNATION_TEST_RESUME here AFAICS
>>
>> Well, not really because of the hibernation_mode check.
>>
>>> and power_down() doesn't return.
>>
>> But this still is true.
>
> Well, except when it does HIBERNATION_SUSPEND.
>
> But can you just make power_down() call pm_restrict_gfp_mask() before
> returning and leave the code in hibernate() as is?
Ah good suggestion. I believe so. I'll test it and get out updated
patches if that works.
next prev parent reply other threads:[~2025-09-25 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 15:59 [PATCH v2 0/3] Fixes for hybrid sleep Mario Limonciello (AMD)
2025-09-25 15:59 ` [PATCH v2 1/3] PM: hibernate: Fix hybrid-sleep Mario Limonciello (AMD)
2025-09-25 17:47 ` Rafael J. Wysocki
2025-09-25 17:51 ` Rafael J. Wysocki
2025-09-25 17:55 ` Rafael J. Wysocki
2025-09-25 18:03 ` Mario Limonciello (AMD) (kernel.org) [this message]
2025-09-25 15:59 ` [PATCH v2 2/3] PM: hibernate: Add pm_hibernation_mode_is_suspend() Mario Limonciello (AMD)
2025-09-25 15:59 ` [PATCH v2 3/3] drm/amd: Fix hybrid sleep Mario Limonciello (AMD)
2025-09-25 16:09 ` [PATCH v2 0/3] Fixes for " Rafael J. Wysocki
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=1b204004-03c1-48b5-abc3-eef5084ba680@kernel.org \
--to=superm1@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=guoqing.zhang@amd.com \
--cc=ionut_n2001@yahoo.com \
--cc=kenny@panix.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
/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