From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754740AbcKJJAt (ORCPT ); Thu, 10 Nov 2016 04:00:49 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:60770 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752646AbcKJJAr (ORCPT ); Thu, 10 Nov 2016 04:00:47 -0500 Date: Thu, 10 Nov 2016 10:00:38 +0100 From: Sebastian Andrzej Siewior To: "Luck, Tony" , Borislav Petkov Cc: "linux-kernel@vger.kernel.org" , "rt@linutronix.de" , "linux-edac@vger.kernel.org" , "x86@kernel.org" , Thomas Gleixner Subject: Re: [PATCH 22/25] x86/mcheck: Do the init in one place Message-ID: <20161110090037.apohiqnqgbymbq6j@linutronix.de> References: <20161103145021.28528-1-bigeasy@linutronix.de> <20161103145021.28528-23-bigeasy@linutronix.de> <20161107184532.xj6wzdjlzwhshcmf@pd.tnic> <20161107185524.GA2536@intel.com> <20161107201224.7xazmhgm7bogkrw5@pd.tnic> <20161108092302.wraci5m2cxqozlew@pd.tnic> <20161109142221.3r6xwhkxbckuv3bh@linutronix.de> <20161109153807.7mv7b5f4oqfijq2h@pd.tnic> <3908561D78D1C84285E8C5FCA982C28F3A229E6C@ORSMSX114.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F3A229E6C@ORSMSX114.amr.corp.intel.com> User-Agent: NeoMutt/20161014 (1.7.1) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016-11-09 18:37:23 [+0000], Luck, Tony wrote: > > That's why the hotplug callback mce_disable_cpu() doesn't fiddle with > > CR4 - it only clears the bits in MCi_CTL. And I think we should remain > > that way. > > N.B. See vendor_disable_error_reporting() ... on Intel we don't clear MCi_CTL. okay. So I had a discussion with Boris and we agreed that we don't do the init part in one place only the timer stuff will be moved. If I understand Tony correctly then we undo something in vendor_disable_error_reporting() (on !INTEL CPUs) that we enable in identify_cpu(). Boris, if my understanding is correct, what now? Do move the whole hotplug init part to an earlier stage? Or do we drop vendor_disable_error_reporting()? > -Tony Sebastian