From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-16.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A538AC6379D for ; Sat, 21 Nov 2020 02:36:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7ACB12240C for ; Sat, 21 Nov 2020 02:36:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726755AbgKUCgd (ORCPT ); Fri, 20 Nov 2020 21:36:33 -0500 Received: from mga14.intel.com ([192.55.52.115]:47086 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726389AbgKUCgc (ORCPT ); Fri, 20 Nov 2020 21:36:32 -0500 IronPort-SDR: FZZRgPpItxMwDU0eOreZ3teD20WqUki8bTIHAOni+5i1qwZ90Pr1/RXYlRRlAIfmKI+fLawzFP U1KMdn+sANyA== X-IronPort-AV: E=McAfee;i="6000,8403,9811"; a="170788359" X-IronPort-AV: E=Sophos;i="5.78,358,1599548400"; d="scan'208";a="170788359" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Nov 2020 18:36:32 -0800 IronPort-SDR: tMO5/dfiyoACOi+38Nf/TN0U9Pgak+DffhJ6VFrPjUUknSwMouIT2Zu3EzQzLkadvCJTKYyiWE 88Z7etQtV5/w== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.78,358,1599548400"; d="scan'208";a="431759873" Received: from otcwcpicx6.sc.intel.com ([172.25.55.29]) by fmsmga001.fm.intel.com with ESMTP; 20 Nov 2020 18:36:32 -0800 From: Fenghua Yu To: "Thomas Gleixner" , "Borislav Petkov" , "Ingo Molnar" , "Peter Zijlstra" , "Tony Luck" , "Randy Dunlap" , "Xiaoyao Li " , "Ravi V Shankar" Cc: "linux-kernel" , "x86" , Fenghua Yu Subject: [PATCH v3 0/4] x86/bus_lock: Enable bus lock detection Date: Sat, 21 Nov 2020 02:36:20 +0000 Message-Id: <20201121023624.3604415-1-fenghua.yu@intel.com> X-Mailer: git-send-email 2.29.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org A bus lock [1] is acquired through either split locked access to writeback (WB) memory or any locked access to non-WB memory. This is typically >1000 cycles slower than an atomic operation within a cache line. It also disrupts performance on other cores. Although split lock can be detected by #AC trap, the trap is triggered before the instruction acquires bus lock. This makes it difficult to mitigate bus lock (e.g. throttle the user application). Some CPUs have ability to notify the kernel by an #DB trap after a user instruction acquires a bus lock and is executed. This allows the kernel to enforce user application throttling or mitigations. #DB for bus lock detect fixes issues in #AC for split lock detect: 1) It's architectural ... just need to look at one CPUID bit to know it exists 2) The IA32_DEBUGCTL MSR, which reports bus lock in #DB, is per-thread. So each process or guest can have different behavior. 3) It has support for VMM/guests (new VMEXIT codes, etc). 4) It detects not only split locks but also bus locks from non-WB. Hardware only generates #DB for bus lock detect when CPL>0 to avoid nested #DB from multiple bus locks while the first #DB is being handled. Use the existing kernel command line option "split_lock_detect=" to handle #DB for bus lock: split_lock_detect= #AC for split lock #DB for bus lock off Do nothing Do nothing warn Kernel OOPs Warn once per task and Warn once per task and and continues to run. disable future checking When both features are supported, warn in #DB fatal Kernel OOPs Send SIGBUS to user. Send SIGBUS to user When both features are supported, split lock triggers #AC and bus lock from non-WB triggers #DB. ratelimit:N Do nothing Limit bus lock rate to N per second in the current non-root user. Default split_lock_detect is "warn". [1] Intel Instruction Set Extension Chapter 8: https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf Change Log: v3: - Enable Bus Lock Detection when fatal to handle bus lock from non-WB (PeterZ). - Add Acked-by: PeterZ in patch 2. v2: - Send SIGBUS in fatal case for bus lock #DB (PeterZ). v1: - Check bus lock bit by its positive polarity (Xiaoyao). - Fix a few wording issues in the documentation (Randy). [RFC v3 can be found at: https://lore.kernel.org/patchwork/cover/1329943/] RFC v3: - Remove DR6_RESERVED change (PeterZ). - Simplify the documentation (Randy). RFC v2: - Architecture changed based on feedback from Thomas and PeterZ. #DB is no longer generated for bus lock in ring0. - Split the one single patch into four patches. [RFC v1 can be found at: https://lore.kernel.org/lkml/1595021700-68460-1-git-send-email-fenghua.yu@intel.com/] Fenghua Yu (4): x86/cpufeatures: Enumerate #DB for bus lock detection x86/bus_lock: Handle warn and fatal in #DB for bus lock x86/bus_lock: Set rate limit for bus lock Documentation/admin-guide: Change doc for split_lock_detect parameter .../admin-guide/kernel-parameters.txt | 31 +++- arch/x86/include/asm/cpu.h | 9 +- arch/x86/include/asm/cpufeatures.h | 1 + arch/x86/include/asm/msr-index.h | 1 + arch/x86/include/uapi/asm/debugreg.h | 1 + arch/x86/kernel/cpu/common.c | 2 +- arch/x86/kernel/cpu/intel.c | 155 +++++++++++++++--- arch/x86/kernel/traps.c | 7 + include/linux/sched/user.h | 4 +- kernel/user.c | 7 + 10 files changed, 186 insertions(+), 32 deletions(-) -- 2.29.2