Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754620AbbK0KQp (ORCPT ); Fri, 27 Nov 2015 05:16:45 -0500 Received: from mail-wm0-f49.google.com ([74.125.82.49]:35443 "EHLO mail-wm0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751248AbbK0KQP (ORCPT ); Fri, 27 Nov 2015 05:16:15 -0500 Date: Fri, 27 Nov 2015 11:16:11 +0100 From: Ingo Molnar To: "Luck, Tony" Cc: Borislav Petkov , linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org, x86@kernel.org Subject: Re: [PATCH 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks Message-ID: <20151127101611.GA1087@gmail.com> References: <02ef9e0e0b73591aa8ec37aae2409274d108af60.1447093569.git.tony.luck@intel.com> <20151112075313.GA5984@gmail.com> <20151112200106.GA32073@agluck-desk.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151112200106.GA32073@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: 927 Lines: 26 * Luck, Tony wrote: > On Thu, Nov 12, 2015 at 08:53:13AM +0100, Ingo Molnar wrote: > > > +extern phys_addr_t mcsafe_memcpy(void *dst, const void __user *src, > > > + unsigned size); > > > > So what's the longer term purpose, where will mcsafe_memcpy() be used? > > The initial plan is to use this for file systems backed by NVDIMMs. They will > have a large amount of memory, and we have a practical recovery path - return > -EIO just like legacy h/w. > > We can look for other places in the kernel where we read large amounts of memory > and have some idea how to recover if the memory turns out to be bad. I see, that's sensible! Thanks, Ingo -- 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/