Re: [PATCH v2 1/4] mm: don't special case !MMU for is_zero_pfn() and my_zero_pfn()
"David Hildenbrand (Arm)" <[email protected]>
| Newsgroups | gmane.linux.uml.devel,gmane.linux.ports.alpha,gmane.linux.kernel,gmane.linux.kernel.arc,gmane.linux.ports.arm.kernel,gmane.linux.ports.hexagon,gmane.linux.ports.parisc,gmane.linux.ports.ppc64.devel,gmane.linux.ports.riscv,gmane.linux.ports.sh.devel,gmane.linux.ports.sparc,gmane.linux.kernel.mm |
|---|---|
| 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