From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753411AbdI0P0t (ORCPT ); Wed, 27 Sep 2017 11:26:49 -0400 Received: from mail.skyhub.de ([5.9.137.197]:40466 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753335AbdI0P0r (ORCPT ); Wed, 27 Sep 2017 11:26:47 -0400 Date: Wed, 27 Sep 2017 17:26:35 +0200 From: Borislav Petkov To: "Ghannam, Yazen" Cc: "linux-edac@vger.kernel.org" , Tony Luck , "x86@kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context Message-ID: <20170927152635.eihhaeumf43gprkq@pd.tnic> References: <1505830031-9630-1-git-send-email-Yazen.Ghannam@amd.com> <20170926120115.z7rorwli3idaxxyr@pd.tnic> <20170926222054.sshmh4t2tson3hyd@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: 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 Wed, Sep 27, 2017 at 03:17:51PM +0000, Ghannam, Yazen wrote: > Generally, we can use the IN_KERNEL_RECOV context to show that the error > is recoverable versus IN_KERNEL which we can consider unrecoverable. > > Specifically, the Intel SER and AMD SUCCOR features represent the same > thing (MCA Recovery). I'll send another patch for enabling recovery on > AMD SUCCOR systems. I want to keep this patch as just a bug fix. Ok, but then do not mention IN_KERNEL_RECOV here as it only confuses: is it a recoverable error or is it not? /me scratches head... > Sure, I'll do this in another patch. I want to keep this as a bug fix > to apply to the stable branches. Sure. Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.