From: Rik van Riel <riel@surriel.com>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, bp@alien8.de, peterz@infradead.org,
dave.hansen@linux.intel.com, zhengqi.arch@bytedance.com,
nadav.amit@gmail.com, thomas.lendacky@amd.com,
kernel-team@meta.com, linux-mm@kvack.org,
akpm@linux-foundation.org, jannh@google.com,
mhklinux@outlook.com, andrew.cooper3@citrix.com,
Rik van Riel <riel@surriel.com>
Subject: [PATCH v7 07/12] x86/mm: use INVLPGB in flush_tlb_all
Date: Wed, 22 Jan 2025 23:23:26 -0500 [thread overview]
Message-ID: <20250123042447.2259648-8-riel@surriel.com> (raw)
In-Reply-To: <20250123042447.2259648-1-riel@surriel.com>
The flush_tlb_all() function is not used a whole lot, but we might
as well use broadcast TLB flushing there, too.
Signed-off-by: Rik van Riel <riel@surriel.com>
---
arch/x86/mm/tlb.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/arch/x86/mm/tlb.c b/arch/x86/mm/tlb.c
index 2c9e9b7482dd..e2a0b7fc5fed 100644
--- a/arch/x86/mm/tlb.c
+++ b/arch/x86/mm/tlb.c
@@ -1065,6 +1065,19 @@ void flush_tlb_mm_range(struct mm_struct *mm, unsigned long start,
}
+static bool broadcast_flush_tlb_all(void)
+{
+ if (!IS_ENABLED(CONFIG_X86_BROADCAST_TLB_FLUSH))
+ return false;
+
+ if (!cpu_feature_enabled(X86_FEATURE_INVLPGB))
+ return false;
+
+ guard(preempt)();
+ invlpgb_flush_all();
+ return true;
+}
+
static void do_flush_tlb_all(void *info)
{
count_vm_tlb_event(NR_TLB_REMOTE_FLUSH_RECEIVED);
@@ -1073,6 +1086,8 @@ static void do_flush_tlb_all(void *info)
void flush_tlb_all(void)
{
+ if (broadcast_flush_tlb_all())
+ return;
count_vm_tlb_event(NR_TLB_REMOTE_FLUSH);
on_each_cpu(do_flush_tlb_all, NULL, 1);
}
--
2.47.1
next prev parent reply other threads:[~2025-01-23 4:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 4:23 [PATCH v7 00/12] AMD broadcast TLB invalidation Rik van Riel
2025-01-23 4:23 ` [PATCH v7 01/12] x86/mm: make MMU_GATHER_RCU_TABLE_FREE unconditional Rik van Riel
2025-01-23 4:23 ` [PATCH v7 02/12] x86/mm: remove pv_ops.mmu.tlb_remove_table call Rik van Riel
2025-01-23 4:23 ` [PATCH v7 03/12] x86/mm: consolidate full flush threshold decision Rik van Riel
2025-01-23 4:23 ` [PATCH v7 04/12] x86/mm: get INVLPGB count max from CPUID Rik van Riel
2025-01-23 4:23 ` [PATCH v7 05/12] x86/mm: add INVLPGB support code Rik van Riel
2025-01-23 4:23 ` [PATCH v7 06/12] x86/mm: use INVLPGB for kernel TLB flushes Rik van Riel
2025-01-23 4:23 ` Rik van Riel [this message]
2025-01-23 4:23 ` [PATCH v7 08/12] x86/mm: use broadcast TLB flushing for page reclaim TLB flushing Rik van Riel
2025-01-23 4:23 ` [PATCH v7 09/12] x86/mm: enable broadcast TLB invalidation for multi-threaded processes Rik van Riel
2025-01-30 5:39 ` Manali Shukla
2025-01-23 4:23 ` [PATCH v7 10/12] x86/mm: do targeted broadcast flushing from tlbbatch code Rik van Riel
2025-01-23 4:23 ` [PATCH v7 11/12] x86/mm: enable AMD translation cache extensions Rik van Riel
2025-01-23 4:23 ` [PATCH v7 12/12] x86/mm: only invalidate final translations with INVLPGB Rik van Riel
2025-01-28 11:00 ` [PATCH v7 00/12] AMD broadcast TLB invalidation Manali Shukla
2025-02-22 12:29 ` Ingo Molnar
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=20250123042447.2259648-8-riel@surriel.com \
--to=riel@surriel.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jannh@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhklinux@outlook.com \
--cc=nadav.amit@gmail.com \
--cc=peterz@infradead.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
--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