Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp3928442ybc; Thu, 21 Nov 2019 16:28:10 -0800 (PST) X-Google-Smtp-Source: APXvYqzkKS51Lc6ipbx83FWYmrFF5NCFl8LeHJh4foIoCCDqefOPjOx+W6u4a1a2+QMZ+rqzawqo X-Received: by 2002:a17:906:f255:: with SMTP id gy21mr18026926ejb.204.1574382490175; Thu, 21 Nov 2019 16:28:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574382490; cv=none; d=google.com; s=arc-20160816; b=KSqwMwS/pYfauntwHFPCMm1ecJkLnPguCAiSn4qB/+LlGO5dYDPDduWIeAJTjtffOc KL0NjCobcBhWeyw8ZZNorUp/Iw1ejprDhtiPz/aNxLUULZoGCGIV+NfYAIRn9yjR0xt4 ycxXf0pPT7umUo4H2oDBNyEQ0mVLJ2lud2+PgMA9f+LSJoWDanno7lPMtXQZNEsuI+oY 2Na7D+U4Lx+yEhlyscT5CkBosbnts6xSpjAnWa+WzLNqzcGXoJwKbrATaF7ONjRfPbbl 9T0hn/dsh38PQ2eVMv+2lE+6KjuRfgYibMdRdmotXp0L3q387JEJNEwtdwib558jx0u7 HyXQ== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=bHBjBsEWy1nbZPZ27AsSBFFuLjyKYZQ8/NRQzNsQtOs=; b=x92I3oPl+sB86fNPwGTPiXA79yp5IkfAOd3/cOXCbBwGpZQTm/JLCwY8SD0NOmeB0r EjvUxvZUeVQpTO+PceCrpLR/SzHRon+AA4RSVNIvNz2OHf3PaizlHtnHurzVjr8ZL+hO mWt+wxz8L9AYbzpOtFzCug83lA6bQrnt7zLzFFS6VRCcj+3XSjOr291BPGmP+0LRR7q/ HGGDBBb/pMv0S4l1jMNoucaHldAq/VyyMfX1z9Kq+HMjFG64QbKikn2HCPatDjfdmj6P GDaOWLfzuka/g0QougaNtawOpxhiy4KedR7yO64cdGoW46+xl+cOGzbW6MMruFNvP8n1 XouQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w42si3690734edc.440.2019.11.21.16.27.46; Thu, 21 Nov 2019 16:28:10 -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; 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726568AbfKVAZx (ORCPT + 99 others); Thu, 21 Nov 2019 19:25:53 -0500 Received: from mga11.intel.com ([192.55.52.93]:13408 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726038AbfKVAZx (ORCPT ); Thu, 21 Nov 2019 19:25:53 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Nov 2019 16:25:44 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,227,1571727600"; d="scan'208";a="219280751" Received: from romley-ivt3.sc.intel.com ([172.25.110.60]) by orsmga002.jf.intel.com with ESMTP; 21 Nov 2019 16:25:44 -0800 Date: Thu, 21 Nov 2019 16:37:54 -0800 From: Fenghua Yu To: Andy Lutomirski Cc: Thomas Gleixner , Ingo Molnar , Borislav Petkov , H Peter Anvin , Peter Zijlstra , Tony Luck , Ashok Raj , Ravi V Shankar , linux-kernel , x86 Subject: Re: [PATCH v10 4/6] x86/split_lock: Enumerate split lock detection if the IA32_CORE_CAPABILITIES MSR is not supported Message-ID: <20191122003754.GF199273@romley-ivt3.sc.intel.com> References: <1574297603-198156-5-git-send-email-fenghua.yu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 21, 2019 at 02:07:38PM -0800, Andy Lutomirski wrote: > > > > On Nov 20, 2019, at 5:45 PM, Fenghua Yu wrote: > > > > Architecturally the split lock detection feature is enumerated by > > IA32_CORE_CAPABILITIES MSR and future CPU models will indicate presence > > of the feature by setting bit 5. But the feature is present in a few > > older models where split lock detection is enumerated by the CPU models. > > > > Use a "x86_cpu_id" table to list the older CPU models with the feature. > > > > This may need to be disabled if the HYPERVISOR bit is set. How about just keeping this patch set as basic enabling code and keep HYPERVISOR out of scope as of now? KVM folks will have better handling of split lock in KVM once this patch set is available in the kernel. Thanks. -Fenghua