From: Lance Yang <lance.yang@linux.dev>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>,
akpm@linux-foundation.org
Cc: will@kernel.org, aneesh.kumar@kernel.org, npiggin@gmail.com,
peterz@infradead.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, arnd@arndb.de, lorenzo.stoakes@oracle.com,
ziy@nvidia.com, baolin.wang@linux.alibaba.com,
Liam.Howlett@oracle.com, npache@redhat.com, ryan.roberts@arm.com,
dev.jain@arm.com, baohua@kernel.org, ioworker0@gmail.com,
shy828301@gmail.com, riel@surriel.com, jannh@google.com,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] mm: embed TLB flush IPI check in tlb_remove_table_sync_one()
Date: Wed, 31 Dec 2025 11:03:40 +0800 [thread overview]
Message-ID: <dafd2f83-c242-4d60-8270-8e52e2e066e6@linux.dev> (raw)
In-Reply-To: <f4d5548d-6045-47a3-b233-0a67702bb477@kernel.org>
On 2025/12/31 04:33, David Hildenbrand (Red Hat) wrote:
> On 12/29/25 15:52, Lance Yang wrote:
>> From: Lance Yang <lance.yang@linux.dev>
>>
>> Embed the tlb_table_flush_implies_ipi_broadcast() check directly inside
>> tlb_remove_table_sync_one() instead of requiring every caller to check
>> it explicitly. This relies on callers to do the right thing: flush with
>> freed_tables=true or unshared_tables=true beforehand.
>>
>> All existing callers satisfy this requirement:
>>
>> 1. mm/khugepaged.c:1188 (collapse_huge_page):
>>
>> pmdp_collapse_flush(vma, address, pmd)
>> -> flush_tlb_range(vma, address, address + HPAGE_PMD_SIZE)
>> -> flush_tlb_mm_range(mm, ..., freed_tables = true)
>> -> flush_tlb_multi(mm_cpumask(mm), info)
>>
>> So freed_tables=true before calling tlb_remove_table_sync_one().
>>
>> 2. include/asm-generic/tlb.h:861 (tlb_flush_unshared_tables):
>>
>> tlb_flush_mmu_tlbonly(tlb)
>> -> tlb_flush(tlb)
>> -> flush_tlb_mm_range(mm, ..., unshared_tables = true)
>> -> flush_tlb_multi(mm_cpumask(mm), info)
>>
>> unshared_tables=true (equivalent to freed_tables for sending IPIs).
>>
>> 3. mm/mmu_gather.c:341 (__tlb_remove_table_one):
>>
>> When we can't allocate a batch page in tlb_remove_table(), we do:
>>
>> tlb_table_invalidate(tlb)
>> -> tlb_flush_mmu_tlbonly(tlb)
>> -> flush_tlb_mm_range(mm, ..., freed_tables = true)
>> -> flush_tlb_multi(mm_cpumask(mm), info)
>>
>> Then:
>> tlb_remove_table_one(table)
>> -> __tlb_remove_table_one(table) // if !CONFIG_PT_RECLAIM
>> -> tlb_remove_table_sync_one()
>>
>> freed_tables=true, and this should work too.
>>
>> Why is tlb->freed_tables guaranteed? Because callers like
>> pte_free_tlb() (via free_pte_range) set freed_tables=true before
>> calling __pte_free_tlb(), which then calls tlb_remove_table().
>> We cannot free page tables without freed_tables=true.
>>
>> Note that tlb_remove_table_sync_one() was a NOP on bare metal x86
>> (CONFIG_MMU_GATHER_RCU_TABLE_FREE=n) before commit a37259732a7d
>> ("x86/mm: Make MMU_GATHER_RCU_TABLE_FREE unconditional").
>>
>> 4-5. mm/khugepaged.c:1683,1819 (pmdp_get_lockless_sync macro):
>>
>> Same as #1. These also use pmdp_collapse_flush() beforehand.
>>
>> Suggested-by: David Hildenbrand (Red Hat) <david@kernel.org>
>> Signed-off-by: Lance Yang <lance.yang@linux.dev>
>
> LGTM. I think we should document that somewhere. Can we add some
Thanks!
> kerneldoc for tlb_remove_table_sync_one() where we document that it
> doesn't to any sync if a previous TLB flush when removing/unsharing page
> tables would have already performed an IPI?
Fair point. Would something like this work?
---8<---
diff --git a/mm/mmu_gather.c b/mm/mmu_gather.c
index 7b588643cbae..9139f0a6b8bd 100644
--- a/mm/mmu_gather.c
+++ b/mm/mmu_gather.c
@@ -274,6 +274,20 @@ static void tlb_remove_table_smp_sync(void *arg)
/* Simply deliver the interrupt */
}
+/**
+ * tlb_remove_table_sync_one - Send IPI to synchronize page table
operations
+ *
+ * Sends an IPI to all CPUs to synchronize when freeing or unsharing page
+ * tables (e.g., to ensure concurrent GUP-fast walkers have completed).
+ *
+ * If a previous TLB flush (when removing/unsharing page tables) already
+ * broadcast IPIs to all CPUs, the redundant IPI is skipped. The
optimization
+ * relies on architectures implementing
tlb_table_flush_implies_ipi_broadcast()
+ * to indicate when their TLB flush provides sufficient synchronization.
+ *
+ * Note that callers must ensure that a TLB flush with freed_tables=true or
+ * unshared_tables=true has been performed before calling.
+ */
void tlb_remove_table_sync_one(void)
{
/* Skip the IPI if the TLB flush already synchronized with other CPUs. */
---
Cheers,
Lance
>
>> ---
>> mm/mmu_gather.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/mm/mmu_gather.c b/mm/mmu_gather.c
>> index 7468ec388455..7b588643cbae 100644
>> --- a/mm/mmu_gather.c
>> +++ b/mm/mmu_gather.c
>> @@ -276,6 +276,10 @@ static void tlb_remove_table_smp_sync(void *arg)
>> void tlb_remove_table_sync_one(void)
>> {
>> + /* Skip the IPI if the TLB flush already synchronized with other
>> CPUs. */
>> + if (tlb_table_flush_implies_ipi_broadcast())
>> + return;
>> +
>> /*
>> * This isn't an RCU grace period and hence the page-tables
>> cannot be
>> * assumed to be actually RCU-freed.
>
>
next prev parent reply other threads:[~2025-12-31 3:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 14:52 [PATCH v2 0/3] skip redundant TLB sync IPIs Lance Yang
2025-12-29 14:52 ` [PATCH v2 1/3] mm/tlb: allow architectures to " Lance Yang
2025-12-29 15:00 ` Lance Yang
2025-12-29 15:01 ` [PATCH v2 0/3] " Lance Yang
2025-12-30 20:31 ` [PATCH v2 1/3] mm/tlb: allow architectures to " David Hildenbrand (Red Hat)
2025-12-31 2:29 ` Lance Yang
2025-12-29 14:52 ` [PATCH v2 2/3] x86/mm: implement redundant IPI elimination for page table operations Lance Yang
2025-12-29 14:52 ` [PATCH v2 3/3] mm: embed TLB flush IPI check in tlb_remove_table_sync_one() Lance Yang
2025-12-30 20:33 ` David Hildenbrand (Red Hat)
2025-12-31 3:03 ` Lance Yang [this message]
2025-12-31 4:26 ` [PATCH v2 0/3] skip redundant TLB sync IPIs Dave Hansen
2025-12-31 12:33 ` David Hildenbrand (Red Hat)
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=dafd2f83-c242-4d60-8270-8e52e2e066e6@linux.dev \
--to=lance.yang@linux.dev \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=arnd@arndb.de \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hpa@zytor.com \
--cc=ioworker0@gmail.com \
--cc=jannh@google.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mingo@redhat.com \
--cc=npache@redhat.com \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=ziy@nvidia.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