Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp2676340imm; Mon, 16 Jul 2018 12:06:29 -0700 (PDT) X-Google-Smtp-Source: AAOMgpct4pgO3c13TWrI5hMzqvDK0s+FLnnYXbTV63jS7En0e2+UftQ36rkCGjPlld4v0QbcYgo6 X-Received: by 2002:a63:e452:: with SMTP id i18-v6mr16301768pgk.185.1531767989362; Mon, 16 Jul 2018 12:06:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531767989; cv=none; d=google.com; s=arc-20160816; b=HKHVFs66nYUXSnLlkPLt94CPsydw8V3a2VpoGHIWj2zRUz0SND6NzS/GIYZEia7Uz2 ZcoS6Ivm/irWiGJmwEw9SkreXxJLeCLL8ZnnbYto7/qzKxiSE+pvlHtTPpG1PCExD0uD pjGBu3B87SHGiMd36tRt83XNTBvcg7SnwRaW8w0oaYO9zPerQ9o2SdWoyiCCiqIyRUQm CeG+JMGS4CNWFxH7c4mG2I0MJU+V9TjRJ9PEcVT4R5X2D8S8bj4RDFwfM3zVK+Iy5SkR cj+sJaYhnN0z6anN1+b8ycS347GOAT3NUA5KnWjRnVtoNteIcexO4Vy2FmNHlIQ4wOE3 C2pQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:arc-authentication-results; bh=Lsczm3Bcy/zDbq8XPEIloRs7mz+xjr+xEHbGFB1Jxvk=; b=juuQ5u6EFnOfUTc/hjxZIvPbqvNYBCENw2k1TypyxhdKoDRSLSym4/okqQqXVFx2+R POQxWNS5xuWqsnGC3PZKw3vy7PPYRHDMlCHQOVw2fEudBjZfKQcuSzUkSHw4QPOg1spL qZI5nbdXvlBQHnP2fLF155yz6ZYe/dVzKeTIyZx+q/weTXZcyKsOr5DK4+0G3EsNf3lp SUss/4jxwKrG4O2cB7OcgeOCnG8zPUiUvo1eb+yrQoEveQNrAGon0AoXaEfZL7rwSrnY 4jaCARiCwK8AsNQkVNyaLJurzxwUNxDe0dfVMfqDicOIUodeY9BWA1r0jiGkh4IPyu7b 367Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d33-v6si31673751pla.57.2018.07.16.12.06.14; Mon, 16 Jul 2018 12:06:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730008AbeGPTcg (ORCPT + 99 others); Mon, 16 Jul 2018 15:32:36 -0400 Received: from shelob.surriel.com ([96.67.55.147]:36116 "EHLO shelob.surriel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728470AbeGPTcf (ORCPT ); Mon, 16 Jul 2018 15:32:35 -0400 Received: from imladris.surriel.com ([96.67.55.152]) by shelob.surriel.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ff8ma-0003RH-Kl; Mon, 16 Jul 2018 15:03:40 -0400 From: Rik van Riel To: linux-kernel@vger.kernel.org Cc: x86@kernel.org, luto@kernel.org, efault@gmx.de, kernel-team@fb.com, mingo@kernel.org, dave.hansen@intel.com, Rik van Riel Subject: [PATCH 6/7] x86,mm: always use lazy TLB mode Date: Mon, 16 Jul 2018 15:03:36 -0400 Message-Id: <20180716190337.26133-7-riel@surriel.com> X-Mailer: git-send-email 2.14.4 In-Reply-To: <20180716190337.26133-1-riel@surriel.com> References: <20180716190337.26133-1-riel@surriel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Now that CPUs in lazy TLB mode no longer receive TLB shootdown IPIs, except at page table freeing time, and idle CPUs will no longer get shootdown IPIs for things like mprotect and madvise, we can always use lazy TLB mode. Signed-off-by: Rik van Riel Acked-by: Dave Hansen Tested-by: Song Liu --- arch/x86/include/asm/tlbflush.h | 16 ---------------- arch/x86/mm/tlb.c | 15 +-------------- 2 files changed, 1 insertion(+), 30 deletions(-) diff --git a/arch/x86/include/asm/tlbflush.h b/arch/x86/include/asm/tlbflush.h index 3aa3204b5dc0..511bf5fae8b8 100644 --- a/arch/x86/include/asm/tlbflush.h +++ b/arch/x86/include/asm/tlbflush.h @@ -148,22 +148,6 @@ static inline unsigned long build_cr3_noflush(pgd_t *pgd, u16 asid) #define __flush_tlb_one_user(addr) __native_flush_tlb_one_user(addr) #endif -static inline bool tlb_defer_switch_to_init_mm(void) -{ - /* - * If we have PCID, then switching to init_mm is reasonably - * fast. If we don't have PCID, then switching to init_mm is - * quite slow, so we try to defer it in the hopes that we can - * avoid it entirely. The latter approach runs the risk of - * receiving otherwise unnecessary IPIs. - * - * This choice is just a heuristic. The tlb code can handle this - * function returning true or false regardless of whether we have - * PCID. - */ - return !static_cpu_has(X86_FEATURE_PCID); -} - struct tlb_context { u64 ctx_id; u64 tlb_gen; diff --git a/arch/x86/mm/tlb.c b/arch/x86/mm/tlb.c index e4156e37aa71..493559cae2d5 100644 --- a/arch/x86/mm/tlb.c +++ b/arch/x86/mm/tlb.c @@ -379,20 +379,7 @@ void enter_lazy_tlb(struct mm_struct *mm, struct task_struct *tsk) if (this_cpu_read(cpu_tlbstate.loaded_mm) == &init_mm) return; - if (tlb_defer_switch_to_init_mm()) { - /* - * There's a significant optimization that may be possible - * here. We have accurate enough TLB flush tracking that we - * don't need to maintain coherence of TLB per se when we're - * lazy. We do, however, need to maintain coherence of - * paging-structure caches. We could, in principle, leave our - * old mm loaded and only switch to init_mm when - * tlb_remove_page() happens. - */ - this_cpu_write(cpu_tlbstate.is_lazy, true); - } else { - switch_mm(NULL, &init_mm, NULL); - } + this_cpu_write(cpu_tlbstate.is_lazy, true); } /* -- 2.14.4