From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752349AbdBTU1v (ORCPT ); Mon, 20 Feb 2017 15:27:51 -0500 Received: from mail.skyhub.de ([78.46.96.112]:32897 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751418AbdBTU1d (ORCPT ); Mon, 20 Feb 2017 15:27:33 -0500 Date: Mon, 20 Feb 2017 21:26:54 +0100 From: Borislav Petkov To: xlpang@redhat.com Cc: x86@kernel.org, linux-kernel@vger.kernel.org, kexec@lists.infradead.org, Tony Luck , Ingo Molnar , Dave Young , Prarit Bhargava , Junichi Nomura , Kiyoshi Ueda , Naoya Horiguchi Subject: Re: [PATCH v2] x86/mce: Don't participate in rendezvous process once nmi_shootdown_cpus() was made Message-ID: <20170220202654.kakjxgmxrlhak6q3@pd.tnic> References: <1487571037-10821-1-git-send-email-xlpang@redhat.com> <20170220110941.vwcm3je3e4kkei6o@pd.tnic> <58AAEF34.9000303@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <58AAEF34.9000303@redhat.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 Mon, Feb 20, 2017 at 09:29:24PM +0800, Xunlei Pang wrote: > There is a small window between crash and kdump kernel boot, so > if a SRAO comes within this window it will also cause the mce > synchronization problem on the crashing cpu if we don't bail out the > crashing cpu. You mean, in the window between, kdump kernel starts writing out memory and the second, kexec-ed kernel? If so, please add that information to the place in do_machine_check() where we check crashing_cpu so that we know why we're doing this temporary ignore of #MC. Thanks. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.