From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x241.google.com (mail-oi0-x241.google.com [IPv6:2607:f8b0:4003:c06::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id D60AC225264A9 for ; Wed, 4 Apr 2018 20:00:54 -0700 (PDT) Received: by mail-oi0-x241.google.com with SMTP id q71-v6so21217031oic.6 for ; Wed, 04 Apr 2018 20:00:54 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180405095755.58b3891f@roar.ozlabs.ibm.com> References: <20180404231943.29581-1-bsingharora@gmail.com> <20180404231943.29581-3-bsingharora@gmail.com> <20180405095755.58b3891f@roar.ozlabs.ibm.com> From: Dan Williams Date: Wed, 4 Apr 2018 20:00:52 -0700 Message-ID: Subject: Re: [RESEND 2/3] powerpc/memcpy: Add memcpy_mcsafe for pmem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Nicholas Piggin Cc: "Luck, Tony" , Matthew Wilcox , Michael Ellerman , linux-nvdimm , linuxppc-dev , Christoph Hellwig List-ID: [ adding Matthew, Christoph, and Tony ] On Wed, Apr 4, 2018 at 4:57 PM, Nicholas Piggin wrote: > On Thu, 5 Apr 2018 09:19:42 +1000 > Balbir Singh wrote: > >> The pmem infrastructure uses memcpy_mcsafe in the pmem >> layer so as to convert machine check excpetions into >> a return value on failure in case a machine check >> exception is encoutered during the memcpy. >> >> This patch largely borrows from the copyuser_power7 >> logic and does not add the VMX optimizations, largely >> to keep the patch simple. If needed those optimizations >> can be folded in. > > So memcpy_mcsafe doesn't return number of bytes copied? > Huh, well that makes it simple. Well, not in current kernels, but we need to add that support or remove the direct call to copy_to_iter() in fs/dax.c. I'm looking right now to add "bytes remaining" support to the x86 memcpy_mcsafe(), but for copy_to_user we also need to handle bytes remaining for write faults. That fix is hopefully something that can land in an early 4.17-rc, but it won't be ready for -rc1. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm