From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753278AbbKLUE6 (ORCPT ); Thu, 12 Nov 2015 15:04:58 -0500 Received: from mail-ob0-f180.google.com ([209.85.214.180]:34289 "EHLO mail-ob0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752820AbbKLUE4 (ORCPT ); Thu, 12 Nov 2015 15:04:56 -0500 MIME-Version: 1.0 In-Reply-To: <20151112194422.GA31228@agluck-desk.sc.intel.com> References: <5bf6f812a7dd2b619487c57987e29b3884c6c4ec.1447093568.git.tony.luck@intel.com> <56441240.6000607@kernel.org> <20151112194422.GA31228@agluck-desk.sc.intel.com> From: Andy Lutomirski Date: Thu, 12 Nov 2015 12:04:36 -0800 Message-ID: Subject: Re: [PATCH 1/3] x86, ras: Add new infrastructure for machine check fixup tables To: "Luck, Tony" Cc: Andy Lutomirski , Borislav Petkov , "linux-kernel@vger.kernel.org" , linux-edac , X86 ML , DanWilliamsdan.j.williams@intel.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 12, 2015 at 11:44 AM, Luck, Tony wrote: > On Wed, Nov 11, 2015 at 08:14:56PM -0800, Andy Lutomirski wrote: >> On 11/06/2015 12:57 PM, Tony Luck wrote: >> >Copy the existing page fault fixup mechanisms to create a new table >> >to be used when fixing machine checks. Note: >> >1) At this time we only provide a macro to annotate assembly code >> >2) We assume all fixups will in code builtin to the kernel. >> >> Shouldn't the first step be to fixup failures during user memory access? > > We already have code to recover from machine checks encountered > while the processor is executing ring3 code. I meant failures during copy_from_user, copy_to_user, etc. --Andy