From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,sj@kernel.org,david@kernel.org,baolin.wang@linux.alibaba.com,qin.yuA@h3c.com,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-page_idlec-remove-redundant-mmu-notifier-in-aging-code.patch removed from -mm tree
Date: Tue, 24 Mar 2026 14:42:57 -0700 [thread overview]
Message-ID: <20260324214258.04799C2BC9E@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/page_idle.c: remove redundant mmu notifier in aging code
has been removed from the -mm tree. Its filename was
mm-page_idlec-remove-redundant-mmu-notifier-in-aging-code.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: qinyu <qin.yuA@h3c.com>
Subject: mm/page_idle.c: remove redundant mmu notifier in aging code
Date: Tue, 3 Feb 2026 18:26:49 +0800
Now we have mmu_notifier_clear_young immediately follows
pmdp_clear_young_notify which internally calls mmu_notifier_clear_young,
this is redundant. change it with non-notify variant and keep consistent
with ptep aging code.
Link: https://lkml.kernel.org/r/20260203102649.2486836-1-qin.yuA@h3c.com
Signed-off-by: qinyu <qin.yuA@h3c.com>
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
Reviewed-by: SeongJae Park <sj@kernel.org>
Acked-by: David Hildenbrand (arm) <david@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/page_idle.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/page_idle.c~mm-page_idlec-remove-redundant-mmu-notifier-in-aging-code
+++ a/mm/page_idle.c
@@ -74,7 +74,7 @@ static bool page_idle_clear_pte_refs_one
pmd_t pmdval = pmdp_get(pvmw.pmd);
if (likely(pmd_present(pmdval)))
- referenced |= pmdp_clear_young_notify(vma, addr, pvmw.pmd);
+ referenced |= pmdp_test_and_clear_young(vma, addr, pvmw.pmd);
referenced |= mmu_notifier_clear_young(vma->vm_mm, addr, addr + PMD_SIZE);
} else {
/* unexpected pmd-mapped page? */
_
Patches currently in -mm which might be from qin.yuA@h3c.com are
reply other threads:[~2026-03-24 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260324214258.04799C2BC9E@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=qin.yuA@h3c.com \
--cc=sj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.