From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751878AbdAXCb2 (ORCPT ); Mon, 23 Jan 2017 21:31:28 -0500 Received: from mx1.redhat.com ([209.132.183.28]:39688 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751388AbdAXCb1 (ORCPT ); Mon, 23 Jan 2017 21:31:27 -0500 Reply-To: xlpang@redhat.com Subject: Re: [PATCH] x86/mce: Keep quiet in case of broadcasted mce after system panic References: <1485158511-22374-1-git-send-email-xlpang@redhat.com> <20170123125157.u2kefedwpvgcdyfo@pd.tnic> <588606B9.3070604@redhat.com> <20170123145056.fyraeehjfnwmmfb6@pd.tnic> <20170123174008.GA4945@intel.com> <20170123175130.l7c7mnmu74ln5v6h@pd.tnic> <20170123180153.GA5646@intel.com> <20170123181437.xbjbsdjfcn7b67dh@pd.tnic> To: Borislav Petkov , "Luck, Tony" Cc: Prarit Bhargava , Kiyoshi Ueda , xlpang@redhat.com, x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Ingo Molnar , Junichi Nomura , Naoya Horiguchi , Dave Young From: Xunlei Pang Message-ID: <5886BCF6.9070006@redhat.com> Date: Tue, 24 Jan 2017 10:33:26 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20170123181437.xbjbsdjfcn7b67dh@pd.tnic> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Tue, 24 Jan 2017 02:31:27 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/24/2017 at 02:14 AM, Borislav Petkov wrote: > On Mon, Jan 23, 2017 at 10:01:53AM -0800, Luck, Tony wrote: >> will ignore the machine check on the other cpus ... assuming >> that "cpu_is_offline(smp_processor_id())" does the right thing >> in the kexec case where this is an "old" cpu that isn't online >> in the new kernel. > Nice. And kdump did do the dumping on one CPU, AFAIR. So we should be > good there. > "nr_cpus=N" will consume more memory, using very large N is almost impossible for kdump to boot with considering the limited crash memory reserved. For some large machine, nr_cpus=1 might not be enough, we have to use nr_cpus=4 or more, it is also helpful for the vmcore parallel dumping :-) Regards, Xunlei