[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250922142308.144ac7bd7bbcb9f5a68ac3a1@linux-foundation.org>
Date: Mon, 22 Sep 2025 14:23:08 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Pasha Tatashin <pasha.tatashin@...een.com>
Cc: Mike Rapoport <rppt@...nel.org>, Alexander Graf <graf@...zon.com>,
Baoquan He <bhe@...hat.com>, Changyuan Lyu <changyuanl@...gle.com>, Chris
Li <chrisl@...nel.org>, Jason Gunthorpe <jgg@...dia.com>, Pratyush Yadav
<pratyush@...nel.org>, kexec@...ts.infradead.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 3/4] kho: add support for preserving vmalloc
allocations
On Mon, 22 Sep 2025 10:17:56 -0400 Pasha Tatashin <pasha.tatashin@...een.com> wrote:
> > +struct page *kho_restore_pages(phys_addr_t phys, unsigned int nr_pages)
> > +{
> > + const unsigned long start_pfn = PHYS_PFN(phys);
> > + const unsigned long end_pfn = start_pfn + nr_pages;
> > + unsigned long pfn = start_pfn;
> > +
> > + while (pfn < end_pfn) {
> > + const unsigned int order =
> > + min(count_trailing_zeros(pfn), ilog2(end_pfn - pfn));
> > + struct page *page = kho_restore_page(PFN_PHYS(pfn));
>
> This line breaks linux-next build because, kho_restore_page has a prototype:
> void kho_restore_page(struct page *page, unsigned int order).
Thanks. I think that's all fixed up in mm.git's current mm-nonmm-unstable branch.
Powered by blists - more mailing lists