From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751956AbdFRI2q (ORCPT ); Sun, 18 Jun 2017 04:28:46 -0400 Received: from verein.lst.de ([213.95.11.211]:51360 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750968AbdFRI2n (ORCPT ); Sun, 18 Jun 2017 04:28:43 -0400 Date: Sun, 18 Jun 2017 10:28:41 +0200 From: Christoph Hellwig To: Dan Williams Cc: linux-nvdimm@lists.01.org, Jan Kara , dm-devel@redhat.com, Toshi Kani , Matthew Wilcox , x86@kernel.org, linux-kernel@vger.kernel.org, hch@lst.de, Jeff Moyer , Ingo Molnar , viro@zeniv.linux.org.uk, "H. Peter Anvin" , linux-fsdevel@vger.kernel.org, Thomas Gleixner , Ross Zwisler Subject: Re: [PATCH v3 01/14] x86, uaccess: introduce copy_from_iter_flushcache for pmem / cache-bypass operations Message-ID: <20170618082841.GA26456@lst.de> References: <149703982465.20620.14881139332926778446.stgit@dwillia2-desk3.amr.corp.intel.com> <149703983098.20620.14791162611225792317.stgit@dwillia2-desk3.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <149703983098.20620.14791162611225792317.stgit@dwillia2-desk3.amr.corp.intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 09, 2017 at 01:23:51PM -0700, Dan Williams wrote: > Implement a __copy_from_user_inatomic_flushcache, memcpy_page_flushcache, and > memcpy_flushcache, that guarantee that the destination buffer is not dirty in > the cpu cache on completion. The new copy_from_iter_flushcache and sub-routines Wouldn't writethrough be a better name? > will be used to replace the "pmem api" (include/linux/pmem.h + > arch/x86/include/asm/pmem.h). The availability of copy_from_iter_flushcache() > and memcpy_flushcache() are gated by the CONFIG_ARCH_HAS_UACCESS_FLUSHCACHE > config symbol, and fallback to copy_from_iter_nocache() and plain memcpy() > otherwise. What is UACCESS about memcpy_flushcache?