Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2150920yba; Fri, 17 May 2019 11:20:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqx+3pMNni7O61LS/DcCTIs2hsRj3PNhFJRsv0hfW5+qB2lys9IOa6kcOs0RpfCozYtuKgte X-Received: by 2002:a62:4351:: with SMTP id q78mr61276166pfa.86.1558117235814; Fri, 17 May 2019 11:20:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558117235; cv=none; d=google.com; s=arc-20160816; b=LxmmAZr5gj8Dg3P1UnXIIhrc7Xpz4gYl/3ReyEPBJ41smlzqq4pVLq5PSyOwBK6iio gfjowQWPs4lOmhWSUVlbnt5ps/FJBl+uukfS8SuSFV+Cf7MUFdIjepxSEnegVrCd7uiD lPK8BUxb3YunH9CPNiH4VC/XG6WZENdGVnfDBG+6gW2fnz4xx++xH1yKMBFNHeUCvl9C SV0vVB2nsxQb1tok9QGNCZrVh9BUcWCPRuY70vnEEZm8TvUYq+YBPugyTpC4vtDOwLWZ MgnfOvoYH12st3F+VYzaZUOwvuiOhOnH/JoonkjogXHsPGN98LxRMgqHfkuf6E3joqjH OPCQ== 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; bh=RpGDH5w8kbWt9gvXljcKFeG38Ir2yNlevItia7Rop6o=; b=uxo0L8e3HY7CKTtMc2ApEN8n3CHKrSiEn0I5DFvFcv3TfRitacz3R6AVi/SJ61jM2r vDYqseT2Beo68E+IanBbKfQgrnh2LKkaEVrbqqPJ4M1MBiLEHw2uUhjizaQLAlYKqO1g BzVN41EBd6I3ABxDrQIXMkXQGwNAzDrkU9Kf2WIP/ZBCflMKIJ2kgrZ7N+ZA/GvmGXgf 2vwK1t3dZCEHlGjYFQj/PksSqIZNn551k41VY+UDvR3jdgSAUqEXXK5IPSn5jicfg7dX eldg78sTBv+LVeXjLs9BENBKMbr9qopgzaWssXSRnFh3+3U9wafaQlPEB/lxW33tprnr ZYag== 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 g7si8717043pgb.109.2019.05.17.11.20.20; Fri, 17 May 2019 11:20:35 -0700 (PDT) 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 S1726876AbfEQR0u (ORCPT + 99 others); Fri, 17 May 2019 13:26:50 -0400 Received: from mga06.intel.com ([134.134.136.31]:33548 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725932AbfEQR0u (ORCPT ); Fri, 17 May 2019 13:26:50 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 May 2019 10:26:49 -0700 X-ExtLoop1: 1 Received: from agluck-desk.sc.intel.com (HELO agluck-desk) ([10.3.52.160]) by orsmga003.jf.intel.com with ESMTP; 17 May 2019 10:26:49 -0700 Date: Fri, 17 May 2019 10:26:49 -0700 From: "Luck, Tony" To: Borislav Petkov Cc: "Ghannam, Yazen" , "linux-edac@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "x86@kernel.org" Subject: Re: [PATCH v3 5/6] x86/MCE: Save MCA control bits that get set in hardware Message-ID: <20190517172648.GA18164@agluck-desk> References: <20190516165648.GB21857@zn.tnic> <20190516172117.GC21857@zn.tnic> <20190516203456.GD21857@zn.tnic> <20190516205943.GA3299@agluck-desk> <20190517101006.GA32065@zn.tnic> <20190517163729.GE13482@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190517163729.GE13482@zn.tnic> 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 On Fri, May 17, 2019 at 06:37:29PM +0200, Borislav Petkov wrote: > Now, the > > wrmsrl(msr_ops.ctl(i), -1) > rdmsrl(msr_ops.ctl(i), val); > > method of throwing all 1s to see what sticks is what Intel wants, as > Tony said. Is that going to be a problem on AMD? It is what we want in general ... but there is this: if (c->x86_vendor == X86_VENDOR_INTEL) { /* * SDM documents that on family 6 bank 0 should not be written * because it aliases to another special BIOS controlled * register. * But it's not aliased anymore on model 0x1a+ * Don't ignore bank 0 completely because there could be a * valid event later, merely don't write CTL0. */ if (c->x86 == 6 && c->x86_model < 0x1A && cfg->banks > 0) mce_banks[0].init = 0; Which is a quirk for some models where we don't want to do the "write all 1s and see what sticks" -Tony