Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp884366yba; Thu, 16 May 2019 10:23:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqyVm6M/1MxmapBO1FA0yfaHUeb+RHWDspORAXMSt8430z+shohKUVICEwcoQpkAhMTC654h X-Received: by 2002:a62:198e:: with SMTP id 136mr37052457pfz.180.1558027401361; Thu, 16 May 2019 10:23:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558027401; cv=none; d=google.com; s=arc-20160816; b=LdgdhcpxRSySJmUupFZjKkC1uaOd5SEPlLPYdldV5BbQBhg4lUAIyuQWhljd9BWot1 P/qt6TIBscEMLlzdKodklI3KK1KooseNCoIEyoGdgllNMju5bMMPAhB3BaNpQBGi2OmB Qw7WzTcieIQGUWTKk6dPfoBgTPcW3WK0ZN6nC1QUMTsur5HzS1x+1QhiAqz6nV4vAK6s QqPeWM+ButDfYuZ9epLbVh4Uol57/ghTrnPEr2rRPnblUQjJi+dA7AdOLjBIKhlpGNQs Q5BUvzNRZnJFiPHrg9sYxI7wdh84a+/hBf9XNZ139Li+NM49Q97Y2ijLPcONAPyfMBuR 0c5w== 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=ExynalFlSTzLZa1JFg4UDCRbMhQxngq/fRxvmHAYg5k=; b=ykc3lJyFSSHou1GTImv873G+6YNETLP/wc6pn7oz9G04yDa+FJ2rSh/9VLWhncdzY6 FJGJ5QOvWPpf9RT7zOBqwoYkxSrK0y8d8SQq64PsehxwxXQ94+SP11l0io192OjF8F4Z R2jNfVhWSYXefzRMIuTxUiHVoEk096PjEJkvnBk9081/oPPa/zO5qftSg90Xt8m6vh/a OwFcVJ9AQmwC4KLlwWevh6t0zdGcxHj8IsjKT50pm4lhEKDe8ufUMiGER2WEfzd5gVCC QDMRwjQafFPF1/6NktGAcvhRb5akLXMLTujgLb6BDwJKjBohWykD9bB54/OWwxNeukb2 qIGQ== 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 z19si5684361pgi.180.2019.05.16.10.22.45; Thu, 16 May 2019 10:23:21 -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 S1727183AbfEPPwF (ORCPT + 99 others); Thu, 16 May 2019 11:52:05 -0400 Received: from mga14.intel.com ([192.55.52.115]:55405 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726381AbfEPPwE (ORCPT ); Thu, 16 May 2019 11:52:04 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 May 2019 08:52:03 -0700 X-ExtLoop1: 1 Received: from agluck-desk.sc.intel.com (HELO agluck-desk) ([10.3.52.160]) by orsmga005.jf.intel.com with ESMTP; 16 May 2019 08:52:02 -0700 Date: Thu, 16 May 2019 08:52:02 -0700 From: "Luck, Tony" To: "Ghannam, Yazen" Cc: "linux-edac@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "bp@suse.de" , "x86@kernel.org" Subject: Re: [PATCH v3 5/6] x86/MCE: Save MCA control bits that get set in hardware Message-ID: <20190516155202.GA11517@agluck-desk> References: <20190430203206.104163-1-Yazen.Ghannam@amd.com> <20190430203206.104163-6-Yazen.Ghannam@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190430203206.104163-6-Yazen.Ghannam@amd.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 On Tue, Apr 30, 2019 at 08:32:20PM +0000, Ghannam, Yazen wrote: > diff --git a/arch/x86/kernel/cpu/mce/core.c b/arch/x86/kernel/cpu/mce/core.c > index 986de830f26e..551366c155ef 100644 > --- a/arch/x86/kernel/cpu/mce/core.c > +++ b/arch/x86/kernel/cpu/mce/core.c > @@ -1567,10 +1567,13 @@ static void __mcheck_cpu_init_clear_banks(void) > for (i = 0; i < this_cpu_read(mce_num_banks); i++) { > struct mce_bank *b = &mce_banks[i]; > > - if (!b->init) > - continue; > - wrmsrl(msr_ops.ctl(i), b->ctl); > - wrmsrl(msr_ops.status(i), 0); > + if (b->init) { > + wrmsrl(msr_ops.ctl(i), b->ctl); > + wrmsrl(msr_ops.status(i), 0); > + } > + > + /* Save bits set in hardware. */ > + rdmsrl(msr_ops.ctl(i), b->ctl); > } > } This looks like it will be a problem for Intel CPUs. If we take a CPU offline, and then bring it back again, we ues "b->ctl" to reinitialize the register in mce_reenable_cpu(). But Intel SDM says at the end of section "15.3.2.1 IA32_MCi_CTL_MSRs" "P6 family processors only allow the writing of all 1s or all 0s to the IA32_MCi_CTL MSR." -Tony