From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Ankur Arora <ankur.a.arora@oracle.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org
Cc: akpm@linux-foundation.org, david@kernel.org, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com, mingo@redhat.com,
mjguzik@gmail.com, luto@kernel.org, peterz@infradead.org,
tglx@linutronix.de, willy@infradead.org, raghavendra.kt@amd.com,
boris.ostrovsky@oracle.com, konrad.wilk@oracle.com
Subject: Re: [PATCH v9 2/7] mm: introduce clear_pages() and clear_user_pages()
Date: Sun, 23 Nov 2025 14:17:37 +0100 [thread overview]
Message-ID: <10a90b15-3e26-451a-bebf-f7ad8ba67d1b@kernel.org> (raw)
In-Reply-To: <20251121202352.494700-3-ankur.a.arora@oracle.com>
Le 21/11/2025 à 21:23, Ankur Arora a écrit :
> Introduce clear_pages(), to be overridden by architectures that
> support more efficient clearing of consecutive pages.
>
> Also introduce clear_user_pages(), however, we will not expect
> this function to be overridden anytime soon.
>
> We have to place the clear_user_pages() variant that uses
> clear_user_page() into mm/util.c for now to work around
> macro magic on sparc and m68k.
>
> Signed-off-by: Ankur Arora <ankur.a.arora@oracle.com>
> Acked-by: David Hildenbrand (Red Hat) <david@kernel.org>
> ---
>
> Notes:
> - Use macros clear_pages, clear_user_page, instead of __HAVE_ARCH_CLEAR_PAGES,
> __HAVE_ARCH_CLEAR_USER_PAGE.
>
> include/linux/mm.h | 41 +++++++++++++++++++++++++++++++++++++++++
> mm/util.c | 13 +++++++++++++
> 2 files changed, 54 insertions(+)
>
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index 6fa6c188f99a..c397ee2f6dd5 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -3879,6 +3879,26 @@ static inline void clear_page_guard(struct zone *zone, struct page *page,
> unsigned int order) {}
> #endif /* CONFIG_DEBUG_PAGEALLOC */
>
> +#ifndef clear_pages
> +/**
> + * clear_pages() - clear a page range for kernel-internal use.
> + * @addr: start address
> + * @npages: number of pages
> + *
> + * Use clear_user_pages() instead when clearing a page range to be
> + * mapped to user space.
> + *
> + * Does absolutely no exception handling.
> + */
> +static inline void clear_pages(void *addr, unsigned int npages)
> +{
> + do {
> + clear_page(addr);
> + addr += PAGE_SIZE;
> + } while (--npages);
Why a 'do while' instead of a 'while' ?
Are you certain that this function will never ever be called with a nul
npages ?
> +}
> +#endif
> +
> #ifndef clear_user_page
> /**
> * clear_user_page() - clear a page to be mapped to user space
> @@ -3901,6 +3921,27 @@ static inline void clear_user_page(void *addr, unsigned long vaddr, struct page
> }
> #endif
>
> +/**
> + * clear_user_pages() - clear a page range to be mapped to user space
> + * @addr: start address
> + * @vaddr: start address of the user mapping
> + * @page: start page
> + * @npages: number of pages
> + *
> + * Assumes that the region (@addr, +@npages) has been validated
> + * already so this does no exception handling.
> + */
> +#ifdef clear_user_pages
> +void clear_user_pages(void *addr, unsigned long vaddr,
> + struct page *page, unsigned int npages);
By doing this you forbid architectures to define it as a static inline,
is that wanted ?
> +#else
> +static inline void clear_user_pages(void *addr, unsigned long vaddr,
> + struct page *page, unsigned int npages)
> +{
> + clear_pages(addr, npages);
> +}
> +#endif
> +
> #ifdef __HAVE_ARCH_GATE_AREA
> extern struct vm_area_struct *get_gate_vma(struct mm_struct *mm);
> extern int in_gate_area_no_mm(unsigned long addr);
> diff --git a/mm/util.c b/mm/util.c
> index 8989d5767528..3c6cd44db1bd 100644
> --- a/mm/util.c
> +++ b/mm/util.c
> @@ -1344,3 +1344,16 @@ bool page_range_contiguous(const struct page *page, unsigned long nr_pages)
> }
> EXPORT_SYMBOL(page_range_contiguous);
> #endif
> +
> +#ifdef clear_user_page
> +void clear_user_pages(void *addr,
What happens if clear_user_page is defined but not clear_user_pages ? In
that case it seems like the definition in linux/mm.h will conflict.
unsigned long vaddr,
> + struct page *page, unsigned int npages)
> +{
> + do {
> + clear_user_page(addr, vaddr, page);
> + addr += PAGE_SIZE;
> + vaddr += PAGE_SIZE;
> + page++;
> + } while (--npages);
Same, are you sure npages will never be nul ?
> +}
> +#endif
next prev parent reply other threads:[~2025-11-23 13:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 20:23 [PATCH v9 0/7] mm: folio_zero_user: clear contiguous pages Ankur Arora
2025-11-21 20:23 ` [PATCH v9 1/7] treewide: provide a generic clear_user_page() variant Ankur Arora
2025-11-23 11:53 ` Christophe Leroy (CS GROUP)
2025-11-24 10:17 ` David Hildenbrand (Red Hat)
2025-11-24 14:02 ` David Hildenbrand (Red Hat)
2025-11-25 7:52 ` Ankur Arora
2025-11-27 23:57 ` Ankur Arora
2025-11-28 7:39 ` Christophe Leroy (CS GROUP)
2025-11-28 22:19 ` Ankur Arora
2025-11-21 20:23 ` [PATCH v9 2/7] mm: introduce clear_pages() and clear_user_pages() Ankur Arora
2025-11-23 13:17 ` Christophe Leroy (CS GROUP) [this message]
2025-11-24 10:26 ` David Hildenbrand (Red Hat)
2025-11-28 10:13 ` Lance Yang
2025-11-28 21:59 ` Ankur Arora
2025-11-21 20:23 ` [PATCH v9 3/7] mm/highmem: introduce clear_user_highpages() Ankur Arora
2025-11-21 20:23 ` [PATCH v9 4/7] x86/mm: Simplify clear_page_* Ankur Arora
2025-11-25 13:47 ` Borislav Petkov
2025-11-25 19:01 ` Ankur Arora
2025-11-26 10:01 ` Mateusz Guzik
2025-11-27 5:28 ` Ankur Arora
2025-11-21 20:23 ` [PATCH v9 5/7] x86/clear_page: Introduce clear_pages() Ankur Arora
2025-11-21 20:23 ` [PATCH v9 6/7] mm, folio_zero_user: support clearing page ranges Ankur Arora
2025-11-21 20:23 ` [PATCH v9 7/7] mm: folio_zero_user: cache neighbouring pages Ankur Arora
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=10a90b15-3e26-451a-bebf-f7ad8ba67d1b@kernel.org \
--to=chleroy@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ankur.a.arora@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mjguzik@gmail.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=x86@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