Re: [PATCH v2 1/4] mm: don't special case !MMU for is_zero_pfn() and my_zero_pfn()
"David Hildenbrand (Arm)" <[email protected]> Mon, 23 Feb 2026 17:16:05 +0100
| Newsgroups | org.kernel.vger.linux-hexagon,dev.linux.lists.loongarch,org.infradead.lists.linux-riscv,org.infradead.lists.linux-snps-arc,org.infradead.lists.linux-um,org.kernel.vger.linux-alpha,org.kernel.vger.linux-csky,org.kernel.vger.linux-kernel,org.kernel.vger.linux-m68k,org.kernel.vger.linux-openrisc,org.kernel.vger.linux-parisc,org.kernel.vger.linux-sh,org.kernel.vger.sparclinux,org.kvack.linux-mm,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <[email protected]> |
On 2/9/26 15:40, Mike Rapoport wrote: > From: "Mike Rapoport (Microsoft)" <[email protected]> > > nommu architectures have empty_zero_page and define ZERO_PAGE() and > although they don't really use it to populate page tables, there is no > reason to hardwire !MMU implementation of is_zero_pfn() and my_zero_pfn() > to 0. > > Drop #ifdef CONFIG_MMU around implementations of is_zero_pfn() and > my_zero_pfn() and remove !MMU version. > > While on it, make zero_pfn __ro_after_init. > > Signed-off-by: Mike Rapoport (Microsoft) <[email protected]> Acked-by: David Hildenbrand (Arm) <[email protected]> -- Cheers, David