From: Mike Rapoport <rppt@kernel.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Graf <graf@amazon.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] kho: fix restoring of contiguous ranges of order-0 pages
Date: Mon, 1 Dec 2025 08:54:37 +0200 [thread overview]
Message-ID: <aS07racwRsh4ep_L@kernel.org> (raw)
In-Reply-To: <mafs0pl96w7hk.fsf@kernel.org>
Hi Pratyush,
On Tue, Nov 25, 2025 at 02:45:59PM +0100, Pratyush Yadav wrote:
> On Tue, Nov 25 2025, Mike Rapoport wrote:
...
> > @@ -243,11 +243,16 @@ static struct page *kho_restore_page(phys_addr_t phys)
> > /* Head page gets refcount of 1. */
> > set_page_count(page, 1);
> >
> > - /* For higher order folios, tail pages get a page count of zero. */
> > + /*
> > + * For higher order folios, tail pages get a page count of zero.
> > + * For physically contiguous order-0 pages every pages gets a page
> > + * count of 1
> > + */
> > + ref_cnt = is_folio ? 0 : 1;
> > for (unsigned int i = 1; i < nr_pages; i++)
> > - set_page_count(page + i, 0);
> > + set_page_count(page + i, ref_cnt);
> >
> > - if (info.order > 0)
> > + if (is_folio && info.order)
>
> This is getting a bit difficult to parse. Let's separate out folio and
> page initialization to separate helpers:
Sorry, I've missed this earlier and now the patches are in akpm's -stable
branch.
Let's postpone these changes for the next cycle, maybe along with support
for deferred initialization of struct page.
> /* Initalize 0-order KHO pages */
> static void kho_init_page(struct page *page, unsigned int nr_pages)
> {
> for (unsigned int i = 0; i < nr_pages; i++)
> set_page_count(page + i, 1);
> }
>
> static void kho_init_folio(struct page *page, unsigned int order)
> {
> unsigned int nr_pages = (1 << order);
>
> /* Head page gets refcount of 1. */
> set_page_count(page, 1);
>
> /* For higher order folios, tail pages get a page count of zero. */
> for (unsigned int i = 1; i < nr_pages; i++)
> set_page_count(page + i, 0);
>
> if (order > 0)
> prep_compound_page(page, order);
> }
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-12-01 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 11:09 [PATCH 0/2] kho: fixes for vmalloc restoration Mike Rapoport
2025-11-25 11:09 ` [PATCH 1/2] kho: kho_restore_vmalloc: fix initialization of pages array Mike Rapoport
2025-11-25 13:18 ` Pratyush Yadav
2025-11-25 11:09 ` [PATCH 2/2] kho: fix restoring of contiguous ranges of order-0 pages Mike Rapoport
2025-11-25 13:45 ` Pratyush Yadav
2025-12-01 6:54 ` Mike Rapoport [this message]
2025-12-01 13:23 ` Pratyush Yadav
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=aS07racwRsh4ep_L@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@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