Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753346AbbKKW2w (ORCPT ); Wed, 11 Nov 2015 17:28:52 -0500 Received: from mail.skyhub.de ([78.46.96.112]:42396 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752805AbbKKW2u (ORCPT ); Wed, 11 Nov 2015 17:28:50 -0500 Date: Wed, 11 Nov 2015 23:28:47 +0100 From: Borislav Petkov To: "Luck, Tony" Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org, x86@kernel.org Subject: Re: [RFC PATCH 0/3] Machine check recovery when kernel accesses poison Message-ID: <20151111222847.GM22512@pd.tnic> References: <20151110112101.GB19187@pd.tnic> <20151110215546.GA28172@agluck-desk.sc.intel.com> <20151111204157.GL22512@pd.tnic> <20151111214803.GA11052@agluck-desk.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20151111214803.GA11052@agluck-desk.sc.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 887 Lines: 24 On Wed, Nov 11, 2015 at 01:48:04PM -0800, Luck, Tony wrote: > No flag. We can search MCi_ADDR across the ranges to see whether this > was a normal RAM error on non-volatile. But that doesn't make this patch > moot. We still need to change the return address to go to the fixup code > instead of back to the place where we hit the error. Why? If you know that it is in the nvdimm range, you can grade the error with lower severity... Or do you mean that without the exception table we'll return back to the insn causing the error and loop indefinitely this way? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/