Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp3503748ybc; Thu, 21 Nov 2019 09:16:12 -0800 (PST) X-Google-Smtp-Source: APXvYqyjTDlOQ4yLMDjgpq1gIC3l3HuJyE6kmyfLeohoeRlDWEjej0jV4T+3ZHmAmoJ+2K9N0x53 X-Received: by 2002:a17:906:4e99:: with SMTP id v25mr15459175eju.106.1574356572558; Thu, 21 Nov 2019 09:16:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574356572; cv=none; d=google.com; s=arc-20160816; b=YDEc+N7apABKASHoDMgcEK8GqOq+qgJxLoohA9NDpDhPY4AuWrpd62km2F2E73ZAHz EC8XlIfihBWFQu9uq4HpIOiCT8T+3kdEtz9jaHDKyxDs53mYfFje0R1oKP1J0zHKoBi3 0wM9o0KRmRIdJw8B2f5PJhBlwCHu9zTUMqcmTsVYfkksJIBijJ+KUIB4m8pIjZiS0rwc c6oP4YgGuGW0laXED/vQJ0l/RjQlM3ww355kLUjycSeKIG7A/ND+scy4YUaVpnyMUWXK SsUwZhd6rLW6nGDOZplszE0NQE0qCNtDCUPm+xIuI9lfMyF5fYvVprvyMgxMRXJUbHP4 ezKA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=i3dXbaeM8/fgEzXWHf4j73/qD2/JvKlKOG24q2kDLhU=; b=bnpW9ERRBaOkfhPka+7tgh39mPtoeGGXdKKt13dRPygYHdCRjdArLGgOTtV6knbF1B xxQhV0rEKCYUbQa+RZ7zsbdEpzu0y9C1eaqjeE4aPZ90OrpvB2tKjEpgiEv50et+85z8 YnqP0bfuZXiZ2XjcAjoc657Z3g1c724IwMGijWHUXSBnjElawM5gaz76wEzt5svIa/mw +GVRLWV/eis5iVYBtIGKFP2a1vhb5M54/Bq1/Jn0Gx7LP2/mC/woDPyhjgEYVgXFa0Vs 9RfxADTsHtA0Vzb7RdFkup42X3BQbW7QtUFIFYVuteK0/TWlFLf9IB54xKE2pGoWtg+o 8wzg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=GcLaoioc; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i15si2270073ejz.434.2019.11.21.09.15.48; Thu, 21 Nov 2019 09:16:12 -0800 (PST) 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; dkim=fail header.i=@gmail.com header.s=20161025 header.b=GcLaoioc; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727336AbfKUROI (ORCPT + 99 others); Thu, 21 Nov 2019 12:14:08 -0500 Received: from mail-wr1-f67.google.com ([209.85.221.67]:36644 "EHLO mail-wr1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726861AbfKUROG (ORCPT ); Thu, 21 Nov 2019 12:14:06 -0500 Received: by mail-wr1-f67.google.com with SMTP id z3so5401522wru.3 for ; Thu, 21 Nov 2019 09:14:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=i3dXbaeM8/fgEzXWHf4j73/qD2/JvKlKOG24q2kDLhU=; b=GcLaoiocTB43exyz2Sw7c1bE8QYr4ZxVv8UNC56FfbxP3Gkhhfz5i0jLfiYUPQCMoa AUGVKhWAFxYXZdN3aWMfWxjEZQOZ+8ggRIzXKkCUzea0eV45bxX5v+DssT28edUaD12Z ls5k4OgXVu/SKelNO5qo4NtGYWuTVY+CDVaN192Wx6SoGGJh1M7uWrQHTMZ6xM2lY9Le TD7KveNHoXLh5htI3rXzHQL5xCcrG9uSqeXNA/qgfqBCgssLx3zUQ5qRE39PwtS2f0qw OtPwq2v51cjIdhQJcex+IkJBSUZwEomo3oqSSjcKQp/m6LqYcKXAQgB9vzQnfk3F1RvE zrUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=i3dXbaeM8/fgEzXWHf4j73/qD2/JvKlKOG24q2kDLhU=; b=DV2Qt4gOt2kBjfo+XkbxfSJbEIkaDIKiL81r0yvDi6FeGLP5R/C4TjVsnhk4xesCEs 6S6RYfNHk17WYMa751aYLD+iTYoqWN0pN0pngBHNIXhzEfNGsdoFC6B5hoIQ+iHwGSlk yJQrIxM9iaNI5KNJRwzEJw6j4euEVMYKm2a84NIkbe85zCl+ha9xyNAG0ES/raXoK/aq 9ZuXSxqkZHAAvZDtjRdaMiQWiBqYipXyHUNpdEcM6rCU+lIFnuMbWNBgb27CWJyhCWwm YRNB0dRM9rk9PoIdKrA5v8m8vb3XuOx5Q123Etzzt5UDcBjdkZj4wD147Gi3RnT/04kl 1ZzA== X-Gm-Message-State: APjAAAV8MClJ4QAVW8pRV39wfYGb4zVySr9t6fpm07n74Q1fTc8JYc/s 1e3jBIQWipWMpNJLgVrA8uk= X-Received: by 2002:adf:eecc:: with SMTP id a12mr1519815wrp.363.1574356444030; Thu, 21 Nov 2019 09:14:04 -0800 (PST) Received: from gmail.com (54033286.catv.pool.telekom.hu. [84.3.50.134]) by smtp.gmail.com with ESMTPSA id v184sm297255wme.31.2019.11.21.09.14.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 21 Nov 2019 09:14:03 -0800 (PST) Date: Thu, 21 Nov 2019 18:14:01 +0100 From: Ingo Molnar To: Fenghua Yu Cc: Peter Zijlstra , Thomas Gleixner , Ingo Molnar , Borislav Petkov , H Peter Anvin , Tony Luck , Ashok Raj , Ravi V Shankar , linux-kernel , x86 Subject: Re: [PATCH v10 6/6] x86/split_lock: Enable split lock detection by kernel parameter Message-ID: <20191121171401.GE12042@gmail.com> References: <1574297603-198156-1-git-send-email-fenghua.yu@intel.com> <1574297603-198156-7-git-send-email-fenghua.yu@intel.com> <20191121060444.GA55272@gmail.com> <20191121130153.GS4097@hirez.programming.kicks-ass.net> <20191121161410.GA199273@romley-ivt3.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191121161410.GA199273@romley-ivt3.sc.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Fenghua Yu wrote: > > This feature MUST be default enabled, otherwise everything will > > be/remain broken and we'll end up in the situation where you can't > > use it even if you wanted to. > > The usage scope of this patch set is largely reduced to only real time. > The long split lock processing time (>1000 cycles) cannot be tolerated > by real time. > > Real time customers do want to use this feature to detect the fatal > split lock error. They don't want any split lock issue from BIOS/EFI/ > firmware/kerne/drivers/user apps. > > Real time can enable the feature (set bit 29 in TEST_CTRL MSR) in BIOS > and don't need OS to enable it. But, #AC handler cannot handle split > lock in the kernel and will return to the faulting instruction and > re-enter #AC. So current #AC handler doesn't provide useful information > for the customers. That's why we add the new #AC handler in this patch > set. Immaterial - for this feature to be useful it must be default-enabled, with reasonable quirk knobs offered to people who happen to be bitten by such bugs and cannot fix the software. But default-enabled is a must-have, as Peter said. Thanks, Ingo