From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753290AbdDJKeW (ORCPT ); Mon, 10 Apr 2017 06:34:22 -0400 Received: from mail.skyhub.de ([5.9.137.197]:56336 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752746AbdDJKeV (ORCPT ); Mon, 10 Apr 2017 06:34:21 -0400 Date: Mon, 10 Apr 2017 12:34:05 +0200 From: Borislav Petkov To: Piotr Luc Cc: linux-edac@vger.kernel.org, Tony Luck , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, Dave Hansen Subject: Re: [PATCH v1] x86/mce: enable PPIN for Knights Landing/Mill Message-ID: <20170410103405.q7xfjf5ohnzroz2l@pd.tnic> References: <20170408172004.8463-1-piotr.luc@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20170408172004.8463-1-piotr.luc@intel.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Apr 08, 2017 at 07:20:04PM +0200, Piotr Luc wrote: > Intel Xeon Phi processors (KNL and KNM) do support PPIN as well, so we > add their CPUIDs to the whitelist of supported processors. > PPIN is a unique number that allows to determine origin of the CPU, > from now on will be logged when an mce error occur. > > Signed-off-by: Piotr Luc > --- > arch/x86/kernel/cpu/mcheck/mce_intel.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/arch/x86/kernel/cpu/mcheck/mce_intel.c b/arch/x86/kernel/cpu/mcheck/mce_intel.c > index 190b3e6..f1c44c3 100644 > --- a/arch/x86/kernel/cpu/mcheck/mce_intel.c > +++ b/arch/x86/kernel/cpu/mcheck/mce_intel.c > @@ -481,6 +481,8 @@ static void intel_ppin_init(struct cpuinfo_x86 *c) > case INTEL_FAM6_BROADWELL_XEON_D: > case INTEL_FAM6_BROADWELL_X: > case INTEL_FAM6_SKYLAKE_X: > + case INTEL_FAM6_XEON_PHI_KNL: > + case INTEL_FAM6_XEON_PHI_KNM: > if (rdmsrl_safe(MSR_PPIN_CTL, &val)) > return; > > -- Applied, thanks. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.