Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1564499pxb; Tue, 26 Oct 2021 11:20:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy5dfxjPs6lOLtIRDjLuIWxxPYVoNrDv8d/CM88EekGmLxW6YzpjLbjaIxXJw9sM/5/HUsu X-Received: by 2002:a62:8496:0:b0:47b:d189:5ce9 with SMTP id k144-20020a628496000000b0047bd1895ce9mr24722324pfd.19.1635272412135; Tue, 26 Oct 2021 11:20:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635272412; cv=none; d=google.com; s=arc-20160816; b=cgouAw40I8IX430CmHwjo9jqCJivNizicSEKYJlJ0DdI/yJ2LKzzvnB76Y0xZx03HN lmeN0d8MivLNBBnaITD+/AuWuqY0mCRBV3zsb8QC1Ta/DQCS62Zj24I/vhfHFqe8IiAp DUSySwOF23Xh1WPO8F78tbRz1R0Sb3G7UVFHxx/UuU1Ev1FxX53rEgMKAAX98DcxXiwb e7+xSG1gCr9QRqBVpvN4+55JTMMAY0bWh5uI39ID4AXFhoyTuL9lPT75bpS5JCnhGHJW +ODR0OnBeKIgi+uaIT/3lUQAuUZVUfxT5Kv8UUUEDNeD0pdaep5o/jMiYCj9XKMzNahJ 9GuQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=/VEIBCWf8eZkwgfgrE3MrvMN5GhRK8VB75123ohWZZA=; b=KA1EYmNUKe3rZXr3u1z0U0V0ZiN2jco6Z954OJSdy0B8XEOsWMZoquz+4luuiLprGg aqKB6E8PAU9f/dxrnkl9MJTnmAa37D/5zqcr//dJl01hBlWjhk+Rb6Q7pMStHOxOaWUs TRJ7XP85K2vHFHGw6Mb098jqYu6/3Y8F+rBjrFtZOADdT98bxGvWOnk4YTxMsAulD43l IqM2NZxK8cpyVWWnqQT9al59iLYag67g1FDrnZdwC9KENlNThI8CXZoaEW64r09Ko95X gaw1bBhKCJ6vLPBaBlUnSRqaPnYNK7X6IHBndvCGlC9+QKzcOPwqgPDmWbpd791dwmw+ I4xw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=JHIidcQT; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x5si1792374pja.161.2021.10.26.11.19.58; Tue, 26 Oct 2021 11:20:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=JHIidcQT; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236721AbhJZOiC (ORCPT + 99 others); Tue, 26 Oct 2021 10:38:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56938 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236724AbhJZOh7 (ORCPT ); Tue, 26 Oct 2021 10:37:59 -0400 Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 97115C061767 for ; Tue, 26 Oct 2021 07:35:35 -0700 (PDT) Received: by mail-pj1-x1030.google.com with SMTP id oa4so11106338pjb.2 for ; Tue, 26 Oct 2021 07:35:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=/VEIBCWf8eZkwgfgrE3MrvMN5GhRK8VB75123ohWZZA=; b=JHIidcQTgtvRlKoZnFFQ9pFiNKgWZ1jqztS+TLVf9yvD6DmdLgn/hQTNn4qTjk8v0I u/02BwPsNp0+vrm05U2jVHkcpDoryONI8EFxuBRmbuMy4LP5yNE+T/XhTGjf2qhsStjQ lap6KjuXb7sjLYMKJKf8ScStAYOXm0IgCuvFbuw6ERsv6UyDc8qgYaRFLkbpIJ95N//D qxE8XzaAyp4AOpNRESWuWlcrv+sbcSP/o/lhUpBB/XOUe8EoeqU4nuIn4UP7bswXIRUm SSB5+ecttCzx3qoNcvj6sVIU86dNVKiVdpNxTmRcxMr5K/PSa9HwQHi3oMyWPkgYw68n tK3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=/VEIBCWf8eZkwgfgrE3MrvMN5GhRK8VB75123ohWZZA=; b=dz63V63q95M29+GFCIJQCSItOYj39IVdKtzPAtMN0Ga4LZdWAI31eSatKAj5jPwnnJ bWeYpnjfuMhbSyCbOC0oOHscktEva73IvVsQ12bPGuDqv6fzPQUkwKZurRNI940E/dem QtfsEVllA/1cP9TzE9R7l8aU8S3Saq7Ispn0ymACRRjm06DbplJHEKHEXCvWutEfc89X tJZwxfTql0qJTibExWO291e2Wzt145jsrZ+7NcwH9A1v3z8oVYjr41ZpQ0+nA7A3i9yj bUhWiPkHcnPj2kZZs0kIyVZNnjl0qG1XSmfltujjCr8XBc8wZFZi5plWT5xmCwPFFK7U Vv5w== X-Gm-Message-State: AOAM531OG3ImfSNuaOk6DKrQv27j3pKIrJAVfVZoVAoiwQUxsKF4otgu WOA4yA5TbjgBW76xj3GeO5wqMBPNRFs= X-Received: by 2002:a17:90a:488d:: with SMTP id b13mr22776824pjh.152.1635258934976; Tue, 26 Oct 2021 07:35:34 -0700 (PDT) Received: from localhost ([47.88.5.130]) by smtp.gmail.com with ESMTPSA id q18sm25457485pfj.46.2021.10.26.07.35.33 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Oct 2021 07:35:34 -0700 (PDT) From: Lai Jiangshan To: linux-kernel@vger.kernel.org Cc: x86@kernel.org, Lai Jiangshan , Peter Zijlstra , Andy Lutomirski , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H. Peter Anvin" Subject: [PATCH V4 32/50] x86/entry: Skip CR3 write when the saved CR3 is kernel CR3 in RESTORE_CR3 Date: Tue, 26 Oct 2021 22:34:18 +0800 Message-Id: <20211026143436.19071-7-jiangshanlai@gmail.com> X-Mailer: git-send-email 2.19.1.6.gb485710b In-Reply-To: <20211026141420.17138-1-jiangshanlai@gmail.com> References: <20211026141420.17138-1-jiangshanlai@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Lai Jiangshan When the original CR3 is kernel CR3, paranoid_entry() hasn't changed the CR3, so the CR3 doesn't need to restored when paranoid_exit() in the this case. Cc: Peter Zijlstra Signed-off-by: Lai Jiangshan --- arch/x86/entry/calling.h | 15 ++++----------- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git a/arch/x86/entry/calling.h b/arch/x86/entry/calling.h index 996b041e92d2..9065c31d2875 100644 --- a/arch/x86/entry/calling.h +++ b/arch/x86/entry/calling.h @@ -231,14 +231,11 @@ For 32-bit we have the following conventions - kernel is built with .macro RESTORE_CR3 scratch_reg:req save_reg:req ALTERNATIVE "jmp .Lend_\@", "", X86_FEATURE_PTI - ALTERNATIVE "jmp .Lwrcr3_\@", "", X86_FEATURE_PCID - - /* - * KERNEL pages can always resume with NOFLUSH as we do - * explicit flushes. - */ + /* No need to restore when the saved CR3 is kernel CR3. */ bt $PTI_USER_PGTABLE_BIT, \save_reg - jnc .Lnoflush_\@ + jnc .Lend_\@ + + ALTERNATIVE "jmp .Lwrcr3_\@", "", X86_FEATURE_PCID /* * Check if there's a pending flush for the user ASID we're @@ -256,10 +253,6 @@ For 32-bit we have the following conventions - kernel is built with SET_NOFLUSH_BIT \save_reg .Lwrcr3_\@: - /* - * The CR3 write could be avoided when not changing its value, - * but would require a CR3 read *and* a scratch register. - */ movq \save_reg, %cr3 .Lend_\@: .endm -- 2.19.1.6.gb485710b