From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Baolin Wang <baolin.wang@linux.alibaba.com>, akpm@linux-foundation.org
Cc: catalin.marinas@arm.com, will@kernel.org,
lorenzo.stoakes@oracle.com, ryan.roberts@arm.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, riel@surriel.com,
harry.yoo@oracle.com, jannh@google.com, willy@infradead.org,
baohua@kernel.org, dev.jain@arm.com, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, hannes@cmpxchg.org,
zhengqi.arch@bytedance.com, shakeel.butt@linux.dev,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] mm: use inline helper functions instead of ugly macros
Date: Wed, 25 Feb 2026 14:56:26 +0100 [thread overview]
Message-ID: <1e90b26c-5934-47e4-a0ea-96fd8af45076@kernel.org> (raw)
In-Reply-To: <dc94552605926f9ce84f9fc2ddfe5f7d1319e41c.1771897150.git.baolin.wang@linux.alibaba.com>
On 2/24/26 02:56, Baolin Wang wrote:
> People have already complained that these *_clear_young_notify() related
> macros are very ugly, so let's use inline helpers to make them more readable.
Could it have been me :)
>
> In addition, I cannot implement these inline helper functions in the
"We cannot implement ..."
> mmu_notifier.h file, because some arch-specific files will include the
> mmu_notifier.h, which introduces header compilation dependencies and causes
> build errors (e.g., arch/arm64/include/asm/tlbflush.h). Moreover, since
> these functions are only used in the mm, implementing these inline helpers
> in the mm/internal.h header seems reasonable.
Agreed. if it compiles, all good.
>
> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> ---
> include/linux/mmu_notifier.h | 54 ------------------------------------
> mm/internal.h | 53 +++++++++++++++++++++++++++++++++++
> 2 files changed, 53 insertions(+), 54 deletions(-)
>
> diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h
> index 07a2bbaf86e9..93894b90c8c1 100644
> --- a/include/linux/mmu_notifier.h
> +++ b/include/linux/mmu_notifier.h
> @@ -515,55 +515,6 @@ static inline void mmu_notifier_range_init_owner(
> range->owner = owner;
> }
>
> -#define clear_flush_young_ptes_notify(__vma, __address, __ptep, __nr) \
> -({ \
> - int __young; \
> - struct vm_area_struct *___vma = __vma; \
> - unsigned long ___address = __address; \
> - unsigned int ___nr = __nr; \
> - __young = clear_flush_young_ptes(___vma, ___address, __ptep, ___nr); \
> - __young |= mmu_notifier_clear_flush_young(___vma->vm_mm, \
> - ___address, \
> - ___address + \
> - ___nr * PAGE_SIZE); \
> - __young; \
> -})
> -
> -#define pmdp_clear_flush_young_notify(__vma, __address, __pmdp) \
> -({ \
> - int __young; \
> - struct vm_area_struct *___vma = __vma; \
> - unsigned long ___address = __address; \
> - __young = pmdp_clear_flush_young(___vma, ___address, __pmdp); \
> - __young |= mmu_notifier_clear_flush_young(___vma->vm_mm, \
> - ___address, \
> - ___address + \
> - PMD_SIZE); \
> - __young; \
> -})
> -
> -#define ptep_clear_young_notify(__vma, __address, __ptep) \
> -({ \
> - int __young; \
> - struct vm_area_struct *___vma = __vma; \
> - unsigned long ___address = __address; \
> - __young = ptep_test_and_clear_young(___vma, ___address, __ptep);\
> - __young |= mmu_notifier_clear_young(___vma->vm_mm, ___address, \
> - ___address + PAGE_SIZE); \
> - __young; \
> -})
> -
> -#define pmdp_clear_young_notify(__vma, __address, __pmdp) \
> -({ \
> - int __young; \
> - struct vm_area_struct *___vma = __vma; \
> - unsigned long ___address = __address; \
> - __young = pmdp_test_and_clear_young(___vma, ___address, __pmdp);\
> - __young |= mmu_notifier_clear_young(___vma->vm_mm, ___address, \
> - ___address + PMD_SIZE); \
> - __young; \
> -})
> -
> #else /* CONFIG_MMU_NOTIFIER */
>
> struct mmu_notifier_range {
> @@ -651,11 +602,6 @@ static inline void mmu_notifier_subscriptions_destroy(struct mm_struct *mm)
>
> #define mmu_notifier_range_update_to_read_only(r) false
>
> -#define clear_flush_young_ptes_notify clear_flush_young_ptes
> -#define pmdp_clear_flush_young_notify pmdp_clear_flush_young
> -#define ptep_clear_young_notify ptep_test_and_clear_young
> -#define pmdp_clear_young_notify pmdp_test_and_clear_young
> -
> static inline void mmu_notifier_synchronize(void)
> {
> }
> diff --git a/mm/internal.h b/mm/internal.h
> index e0ef192b0be3..1ba175b8d4f1 100644
> --- a/mm/internal.h
> +++ b/mm/internal.h
> @@ -11,6 +11,7 @@
> #include <linux/khugepaged.h>
> #include <linux/mm.h>
> #include <linux/mm_inline.h>
> +#include <linux/mmu_notifier.h>
> #include <linux/pagemap.h>
> #include <linux/pagewalk.h>
> #include <linux/rmap.h>
> @@ -1789,4 +1790,56 @@ static inline int io_remap_pfn_range_complete(struct vm_area_struct *vma,
> return remap_pfn_range_complete(vma, addr, pfn, size, prot);
> }
>
> +#ifdef CONFIG_MMU_NOTIFIER
> +static inline int clear_flush_young_ptes_notify(struct vm_area_struct *vma,
> + unsigned long addr, pte_t *ptep,
> + unsigned int nr)
Two tabs indent on the second line makes this fit into two lines.
Same for the others.
With that
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
> +{
> + int young;
> +
> + young = clear_flush_young_ptes(vma, addr, ptep, nr);
> + young |= mmu_notifier_clear_flush_young(vma->vm_mm, addr,
> + addr + nr * PAGE_SIZE);
> + return young;
> +}
> +
> +static inline int pmdp_clear_flush_young_notify(struct vm_area_struct *vma,
> + unsigned long addr, pmd_t *pmdp)
> +{
> + int young;
> +
> + young = pmdp_clear_flush_young(vma, addr, pmdp);
> + young |= mmu_notifier_clear_flush_young(vma->vm_mm, addr, addr + PMD_SIZE);
> + return young;
> +}
> +
> +static inline int ptep_clear_young_notify(struct vm_area_struct *vma,
> + unsigned long addr, pte_t *ptep)
> +{
> + int young;
> +
> + young = ptep_test_and_clear_young(vma, addr, ptep);
> + young |= mmu_notifier_clear_young(vma->vm_mm, addr, addr + PAGE_SIZE);
> + return young;
> +}
> +
> +static inline int pmdp_clear_young_notify(struct vm_area_struct *vma,
> + unsigned long addr, pmd_t *pmdp)
> +{
> + int young;
> +
> + young = pmdp_test_and_clear_young(vma, addr, pmdp);
> + young |= mmu_notifier_clear_young(vma->vm_mm, addr, addr + PMD_SIZE);
> + return young;
> +}
Wonder why someone thought it would be a good idea to not include the
"test_and_", to make the function names inconsistent.
--
Cheers,
David
next prev parent reply other threads:[~2026-02-25 13:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 1:56 [PATCH 0/5] support batched checking of the young flag for MGLRU Baolin Wang
2026-02-24 1:56 ` [PATCH 1/5] mm: use inline helper functions instead of ugly macros Baolin Wang
2026-02-24 2:36 ` Rik van Riel
2026-02-24 7:09 ` Barry Song
2026-02-25 13:56 ` David Hildenbrand (Arm) [this message]
2026-02-24 1:56 ` [PATCH 2/5] mm: rmap: add a ZONE_DEVICE folio warning in folio_referenced() Baolin Wang
2026-02-24 2:38 ` Rik van Riel
2026-02-24 5:49 ` Baolin Wang
2026-02-25 13:57 ` David Hildenbrand (Arm)
2026-02-24 6:34 ` Alistair Popple
2026-02-24 1:56 ` [PATCH 3/5] mm: add a batched helper to clear the young flag for large folios Baolin Wang
2026-02-24 22:03 ` Rik van Riel
2026-02-25 2:05 ` Baolin Wang
2026-02-25 14:04 ` David Hildenbrand (Arm)
2026-02-24 1:56 ` [PATCH 4/5] mm: support batched checking of the young flag for MGLRU Baolin Wang
2026-02-24 22:12 ` Rik van Riel
2026-02-25 14:25 ` David Hildenbrand (Arm)
2026-02-24 1:56 ` [PATCH 5/5] arm64: mm: implement the architecture-specific test_and_clear_young_ptes() Baolin Wang
2026-02-25 0:23 ` Rik van Riel
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=1e90b26c-5934-47e4-a0ea-96fd8af45076@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=catalin.marinas@arm.com \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=weixugc@google.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yuanchu@google.com \
--cc=zhengqi.arch@bytedance.com \
/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