From: Evangelos Petrongonas <epetron@amazon.de>
To: Mike Rapoport <rppt@kernel.org>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Alexander Graf <graf@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jason Miu <jasonmiu@google.com>, <linux-kernel@vger.kernel.org>,
<kexec@lists.infradead.org>, <linux-mm@kvack.org>,
<nh-open-source@amazon.com>
Subject: Re: [PATCH] kho: add support for deferred struct page init
Date: Thu, 5 Feb 2026 09:39:48 +0000 [thread overview]
Message-ID: <20260205093948.GA96044@dev-dsk-epetron-1c-1d4d9719.eu-west-1.amazon.com> (raw)
In-Reply-To: <aYOToJvAUU0dmW94@kernel.org>
On Wed, Feb 04, 2026 at 08:44:48PM +0200 Mike Rapoport wrote:
> Hi Evangelos,
>
> Are you planning to send a v2?
>
> On Tue, Dec 16, 2025 at 08:49:12AM +0000, Evangelos Petrongonas wrote:
Hi Mike,
I am leaving soon for some AFK time, therefore I don't believe I will
post a v2 anytime before the beginning of March. Feel free (you or
anyone else) to send a patch. If a patch is sent until then I am happy,
to test it when I am back.
> > When `CONFIG_DEFERRED_STRUCT_PAGE_INIT` is enabled, struct page
> > initialization is deferred to parallel kthreads that run later
> > in the boot process.
> >
> > During KHO restoration, `deserialize_bitmap()` writes metadata for
> > each preserved memory region. However, if the struct page has not been
> > initialized, this write targets uninitialized memory, potentially
> > leading to errors like:
> > ```
> > BUG: unable to handle page fault for address: ...
> > ```
> >
> > Fix this by introducing `kho_get_preserved_page()`, which ensures
> > all struct pages in a preserved region are initialized by calling
> > `init_deferred_page()` which is a no-op when deferred init is disabled
> > or when the struct page is already initialized.
> >
> > Fixes: 8b66ed2c3f42 ("kho: mm: don't allow deferred struct page with KHO")
> > Signed-off-by: Evangelos Petrongonas <epetron@amazon.de>
> > ---
> > ### Notes
> > @Jason, this patch should act as a temporary fix to make KHO play nice
> > with deferred struct page init until you post your ideas about splitting
> > "Physical Reservation" from "Metadata Restoration".
> >
> > ### Testing
> > In order to test the fix, I modified the KHO selftest, to allocate more
> > memory and do so from higher memory to trigger the incompatibility. The
> > branch with those changes can be found in:
> > https://git.infradead.org/?p=users/vpetrog/linux.git;a=shortlog;h=refs/heads/kho-deferred-struct-page-init
> >
> > In future patches, we might want to enhance the selftest to cover
> > this case as well. However, properly adopting the test for this
> > is much more work than the actual fix, therefore it can be deferred to a
> > follow-up series.
> >
> > In addition attempting to run the selftest for arm (without my changes)
> > fails with:
> > ```
> > ERROR:target/arm/internals.h:767:regime_is_user: code should not be reached
> > Bail out! ERROR:target/arm/internals.h:767:regime_is_user: code should not be reached
> > ./tools/testing/selftests/kho/vmtest.sh: line 113: 61609 Aborted
> > ```
> > I have not looked it up further, but can also do so as part of a
> > selftest follow-up.
> >
> > kernel/liveupdate/Kconfig | 2 --
> > kernel/liveupdate/kexec_handover.c | 19 ++++++++++++++++++-
> > 2 files changed, 18 insertions(+), 3 deletions(-)
> >
> > diff --git a/kernel/liveupdate/Kconfig b/kernel/liveupdate/Kconfig
> > index d2aeaf13c3ac..9394a608f939 100644
> > --- a/kernel/liveupdate/Kconfig
> > +++ b/kernel/liveupdate/Kconfig
> > @@ -1,12 +1,10 @@
> > # SPDX-License-Identifier: GPL-2.0-only
> >
> > menu "Live Update and Kexec HandOver"
> > - depends on !DEFERRED_STRUCT_PAGE_INIT
> >
> > config KEXEC_HANDOVER
> > bool "kexec handover"
> > depends on ARCH_SUPPORTS_KEXEC_HANDOVER && ARCH_SUPPORTS_KEXEC_FILE
> > - depends on !DEFERRED_STRUCT_PAGE_INIT
> > select MEMBLOCK_KHO_SCRATCH
> > select KEXEC_FILE
> > select LIBFDT
> > diff --git a/kernel/liveupdate/kexec_handover.c b/kernel/liveupdate/kexec_handover.c
> > index 9dc51fab604f..78cfe71e6107 100644
> > --- a/kernel/liveupdate/kexec_handover.c
> > +++ b/kernel/liveupdate/kexec_handover.c
> > @@ -439,6 +439,23 @@ static int kho_mem_serialize(struct kho_out *kho_out)
> > return err;
> > }
> >
> > +/*
> > + * With CONFIG_DEFERRED_STRUCT_PAGE_INIT, struct pages in higher memory
> > + * regions may not be initialized yet at the time KHO deserializes preserved
> > + * memory. This function ensures all struct pages in the region are initialized.
> > + */
> > +static struct page *__init kho_get_preserved_page(phys_addr_t phys,
> > + unsigned int order)
> > +{
> > + unsigned long pfn = PHYS_PFN(phys);
> > + int nid = early_pfn_to_nid(pfn);
> > +
> > + for (int i = 0; i < (1 << order); i++)
> > + init_deferred_page(pfn + i, nid);
> > +
> > + return pfn_to_page(pfn);
> > +}
> > +
> > static void __init deserialize_bitmap(unsigned int order,
> > struct khoser_mem_bitmap_ptr *elm)
> > {
> > @@ -449,7 +466,7 @@ static void __init deserialize_bitmap(unsigned int order,
> > int sz = 1 << (order + PAGE_SHIFT);
> > phys_addr_t phys =
> > elm->phys_start + (bit << (order + PAGE_SHIFT));
> > - struct page *page = phys_to_page(phys);
> > + struct page *page = kho_get_preserved_page(phys, order);
> > union kho_page_info info;
> >
> > memblock_reserve(phys, sz);
> > --
> > 2.43.0
> >
> >
> >
> >
> > Amazon Web Services Development Center Germany GmbH
> > Tamara-Danz-Str. 13
> > 10243 Berlin
> > Geschaeftsfuehrung: Christof Hellmis, Andreas Stieger
> > Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
> > Sitz: Berlin
> > Ust-ID: DE 365 538 597
> >
>
> --
> Sincerely yours,
> Mike.
--
Kind Regards,
Evangelos
Amazon Web Services Development Center Germany GmbH
Tamara-Danz-Str. 13
10243 Berlin
Geschaeftsfuehrung: Christof Hellmis, Andreas Stieger
Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
Sitz: Berlin
Ust-ID: DE 365 538 597
next prev parent reply other threads:[~2026-02-05 9:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 8:49 Evangelos Petrongonas
2025-12-16 10:53 ` Pasha Tatashin
2025-12-16 11:57 ` Mike Rapoport
2025-12-16 14:26 ` Evangelos Petrongonas
2025-12-16 15:05 ` Pasha Tatashin
2025-12-16 15:19 ` Mike Rapoport
2025-12-16 15:36 ` Pasha Tatashin
2025-12-16 15:51 ` Pasha Tatashin
2025-12-20 2:27 ` Pratyush Yadav
2025-12-19 9:19 ` Mike Rapoport
2025-12-19 16:28 ` Pasha Tatashin
2025-12-20 3:20 ` Pratyush Yadav
2025-12-20 14:49 ` Pasha Tatashin
2025-12-22 15:33 ` Pratyush Yadav
2025-12-22 15:55 ` Pasha Tatashin
2025-12-22 16:24 ` Pratyush Yadav
2025-12-23 17:37 ` Pasha Tatashin
2025-12-29 21:03 ` Pratyush Yadav
2025-12-30 16:05 ` Pasha Tatashin
2025-12-30 16:16 ` Mike Rapoport
2025-12-30 16:18 ` Pasha Tatashin
2025-12-30 17:18 ` Mike Rapoport
2025-12-30 18:21 ` Pasha Tatashin
2025-12-31 9:46 ` Mike Rapoport
2026-01-02 14:24 ` Pratyush Yadav
2026-01-02 14:05 ` Pratyush Yadav
2025-12-30 16:14 ` Mike Rapoport
2026-01-03 5:23 ` Jason Miu
2026-02-04 18:44 ` Mike Rapoport
2026-02-05 9:39 ` Evangelos Petrongonas [this message]
2025-12-24 7:34 Fadouse
2025-12-29 21:09 ` Pratyush Yadav
2025-12-30 15:05 ` Pasha Tatashin
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=20260205093948.GA96044@dev-dsk-epetron-1c-1d4d9719.eu-west-1.amazon.com \
--to=epetron@amazon.de \
--cc=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--cc=jasonmiu@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nh-open-source@amazon.com \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@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