From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Zi Yan <ziy@nvidia.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [stable-6.6.y] mm: khugepaged refuses to freeze
Date: Fri, 6 Feb 2026 10:00:25 +0100 [thread overview]
Message-ID: <af21afa0-2a30-478e-ac9f-6bd431af6502@kernel.org> (raw)
In-Reply-To: <70ed2de7-3e66-4a23-85bb-e0a4c5b61088@linux.alibaba.com>
>> I recall that there is a notifier when the system is preparing to
>> sleep (pm notifier or something). Could we simply hook into that to
>> tell khugepaged to suspend+resume?
>
> Do you mean “struct dev_pm_ops”, which is used to register PM callbacks
> for devices? However, I don’t know how to use it with a kernel thread.
>
> Also look at how kswapd does it, kswapd also uses
> kthread_freezable_should_stop() to check the freeze state.
Right, mimicking what kswapd does sound reasonable!
--
Cheers,
David
next prev parent reply other threads:[~2026-02-06 9:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 2:47 Sergey Senozhatsky
2026-02-06 3:33 ` Baolin Wang
2026-02-06 3:38 ` Sergey Senozhatsky
2026-02-06 4:31 ` Sergey Senozhatsky
2026-02-06 5:12 ` Baolin Wang
2026-02-06 8:36 ` David Hildenbrand (Arm)
2026-02-06 8:55 ` Baolin Wang
2026-02-06 9:00 ` David Hildenbrand (Arm) [this message]
2026-02-10 3:21 ` Sergey Senozhatsky
2026-02-10 10:07 ` Baolin Wang
2026-02-10 10:12 ` Sergey Senozhatsky
2026-02-10 10:21 ` David Hildenbrand (Arm)
2026-02-11 1:03 ` Baolin Wang
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=af21afa0-2a30-478e-ac9f-6bd431af6502@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=senozhatsky@chromium.org \
--cc=ziy@nvidia.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