From patchwork Mon Jan 20 02:40:08 2025 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Rik van Riel X-Patchwork-Id: 13944699 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 782F7C0218A for ; Mon, 20 Jan 2025 02:42:31 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 054AE6B0092; Sun, 19 Jan 2025 21:42:30 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id EB5F66B0088; Sun, 19 Jan 2025 21:42:29 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id CA9AD280001; Sun, 19 Jan 2025 21:42:29 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id 9F1F76B0089 for ; Sun, 19 Jan 2025 21:42:29 -0500 (EST) Received: from smtpin03.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id 5E93B1627B4 for ; Mon, 20 Jan 2025 02:42:29 +0000 (UTC) X-FDA: 83026281618.03.F06B464 Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) by imf24.hostedemail.com (Postfix) with ESMTP id F3C17180008 for ; Mon, 20 Jan 2025 02:42:26 +0000 (UTC) Authentication-Results: imf24.hostedemail.com; dkim=none; spf=pass (imf24.hostedemail.com: domain of riel@shelob.surriel.com designates 96.67.55.147 as permitted sender) smtp.mailfrom=riel@shelob.surriel.com; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1737340948; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-transfer-encoding:content-transfer-encoding: in-reply-to:references; bh=12bY4OfPn0hOJgPrnZKA4kMkAQS2pECsTA3FajczaGs=; b=WStxXwVC20J3BkKNg7wKFsRV4yHJ5dFZFAF6pO74yPeLGnUlQSoU6fFHiV6RteqeSwmRyT d/nbt/eI4dO2RwbV967xviTXBDOyvlCE9p6V+eTVw9RKmqsIjay+a4S2Mf0x8RCdmFuPJv Qq0Rgv6UkmVMik5wnvNesrNGqUN62NM= ARC-Authentication-Results: i=1; imf24.hostedemail.com; dkim=none; spf=pass (imf24.hostedemail.com: domain of riel@shelob.surriel.com designates 96.67.55.147 as permitted sender) smtp.mailfrom=riel@shelob.surriel.com; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1737340948; a=rsa-sha256; cv=none; b=xjGmf/gSS0TL6TZy4x4+cjUWr7AJZU/w9UumLszXcc0tQPzMMXOVxTowD95cLLPD9tjJ9W KePPv0Ky7mxLCTGO0bzTuGc+qGpvhLpZtgmfyzk1lJdqXtxB1w/grCnMyUH+3mfHVcyFdI 2GH5BnFArpOvdPd/Eeq6Eox3RqAtdtE= Received: from fangorn.home.surriel.com ([10.0.13.7]) by shelob.surriel.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1tZhis-000000002w5-0WJd; Sun, 19 Jan 2025 21:41:06 -0500 From: Rik van Riel 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 Subject: [PATCH v6 00/12] AMD broadcast TLB invalidation Date: Sun, 19 Jan 2025 21:40:08 -0500 Message-ID: <20250120024104.1924753-1-riel@surriel.com> X-Mailer: git-send-email 2.47.1 MIME-Version: 1.0 X-Rspam-User: X-Rspamd-Server: rspam09 X-Rspamd-Queue-Id: F3C17180008 X-Stat-Signature: 8uqry18goir3hownw8go3e88kasgh1wf X-HE-Tag: 1737340946-505589 X-HE-Meta: U2FsdGVkX1+VBdqy4r7o8CqZereCWKzduHPzHSEQaqW2i0DAFawQQpxJIK5ZWy++UBYAdKuXGzU4eE9ldO78mfyKsobqYrlwPpWGdh3B4NLBuuz/PBqYm/N4yy7am3UAY8RsjnSxUFf862Y3ZdtQTFt2G02Z8gLuICcCHzAtSBZ7Z/yjZM1c54Qzql2QwyhqMAVsipY1C/uFIMIQm6EKtHDXEW3rnWMgP2kM75HH5ekXw32q3HNio+hXTdiuw5F5GGv20If+PGs+YelAd+x79/NBVD9gCX7I2hSVJI5VJXTviCZOjDkqbmY6UaL7Kr9XK95extKsr0FG+qAUyafaHEJzCGOrQe41us6qvw2cA1D4dIMGJ+a12xTXMgO6IdGcuJP7JzDHwHLdHPeW/yH3hS4rVwUximpfHjJWfCS8ads0rjFQ4yOQqaPlAw+miugDuQgWCB2LRFADdvWMRJEZxRlBkVpe94A+9V+DvhrEXjsoDCqdh8ZXQE/c76KuUrI/qWObQKROYut6GlG2H5ya2HYqs9lWpU+bn/UACTLQDVXWJgMQBc+cOMsGfKHf7NapOoYym4zS7BhhpZWzIXInY8/MKIpg4x+xRoOBhJrU5Sq7mNXqahbjCJV5Q9M8jg4ESAE0cA2OBBs8s4Z4/JTnkYZs4iJC6FxMVrRUq0X8fuibgK/wbYUV0DxX32bcyIbJ/Ae+2VTn44hm3hXL5gREEotNHxzyGWFeV7ViJ8ozhijuENA+msEG34kH3QRLusUXhauoV+X2unccNIrLlihNmQb+24YMqsxWTYaIvJXLeSuMuRlolj9y7SPd/AhjRyLthcK/S+C3EXwNf/QTDmwecvcp3zfyeTZnhskfNCtyx8ylSQtDz8uBTuaoXM+yxgaB2UFJ4PCxI85/6Ovc65PC7/PXgjkGXwewTXAW4UO1T1Ik7BECq0TMJQuCV4/GHDkO5kfKzw2duLYYGLkaNno WoSmiSVi oQEIQ89foQAzGSDU+KX+Q2BloLjBLDX4PbvyxGauqq9SwhXIRFNo7woP6KGlA+8Mjceej3RFwz0iKrXFe077r0TGkEtNjaVuqE1QTZnP1cVyW3KvDOOL0VRkH6iq9Kz7+k7ksqggBHEmY+FzkCRhlfDf2AQIA/4bEvQ0FSMbW4KICAsFiS+tk9P9w3bv24eERGlA7tSpMxZsA/fo3/EdcaaroWh/5FIWzV09/TuD0VBDWO2fRDpAuXCG85I1h2c+tX0SUj2P6lrqQ+BDZ1HeTDp4xYADO5vHpe1O39ctJvBVid9mrl7mYOXMpsvFb4bwYW3QEgeU39WzQCA+514VhPdhwxxZp30l6BiN/fNKhTTcxdH1bNSHMEEjHyQ5gdKxl5azLEaeqkbYluh/Q1cKzJ/DlQwmHZUT5HPqlwXi/3rOMzGe3jqJCXdXpjrr+eDy2nV5y X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: Add support for broadcast TLB invalidation using AMD's INVLPGB instruction. This allows the kernel to invalidate TLB entries on remote CPUs without needing to send IPIs, without having to wait for remote CPUs to handle those interrupts, and with less interruption to what was running on those CPUs. Because x86 PCID space is limited, and there are some very large systems out there, broadcast TLB invalidation is only used for processes that are active on 3 or more CPUs, with the threshold being gradually increased the more the PCID space gets exhausted. Combined with the removal of unnecessary lru_add_drain calls (see https://lkml.org/lkml/2024/12/19/1388) this results in a nice performance boost for the will-it-scale tlb_flush2_threads test on an AMD Milan system with 36 cores: - vanilla kernel: 527k loops/second - lru_add_drain removal: 731k loops/second - only INVLPGB: 527k loops/second - lru_add_drain + INVLPGB: 1157k loops/second Profiling with only the INVLPGB changes showed while TLB invalidation went down from 40% of the total CPU time to only around 4% of CPU time, the contention simply moved to the LRU lock. Fixing both at the same time about doubles the number of iterations per second from this case. Some numbers closer to real world performance can be found at Phoronix, thanks to Michael: https://www.phoronix.com/news/AMD-INVLPGB-Linux-Benefits My current plan is to implement support for Intel's RAR (Remote Action Request) TLB flushing in a follow-up series, after this thing has been merged into -tip. Making things any larger would just be unwieldy for reviewers. v6: - fix info->end check in flush_tlb_kernel_range (Michael) - disable broadcast TLB flushing on 32 bit x86 v5: - use byte assembly for compatibility with older toolchains (Borislav, Michael) - ensure a panic on an invalid number of extra pages (Dave, Tom) - add cant_migrate() assertion to tlbsync (Jann) - a bunch more cleanups (Nadav) - key TCE enabling off X86_FEATURE_TCE (Andrew) - fix a race between reclaim and ASID transition (Jann) v4: - Use only bitmaps to track free global ASIDs (Nadav) - Improved AMD initialization (Borislav & Tom) - Various naming and documentation improvements (Peter, Nadav, Tom, Dave) - Fixes for subtle race conditions (Jann) v3: - Remove paravirt tlb_remove_table call (thank you Qi Zheng) - More suggested cleanups and changelog fixes by Peter and Nadav v2: - Apply suggestions by Peter and Borislav (thank you!) - Fix bug in arch_tlbbatch_flush, where we need to do both the TLBSYNC, and flush the CPUs that are in the cpumask. - Some updates to comments and changelogs based on questions. Tested-by: Michael Kelley