From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by kanga.kvack.org (Postfix) with ESMTP id 8209E6B0032 for ; Wed, 24 Jun 2015 08:08:23 -0400 (EDT) Received: by wiwl6 with SMTP id l6so93345857wiw.0 for ; Wed, 24 Jun 2015 05:08:23 -0700 (PDT) Received: from newverein.lst.de (verein.lst.de. [213.95.11.211]) by mx.google.com with ESMTPS id v4si2469331wif.107.2015.06.24.05.08.21 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jun 2015 05:08:21 -0700 (PDT) Date: Wed, 24 Jun 2015 14:08:20 +0200 From: Christoph Hellwig Subject: Re: [PATCH v5 6/6] arch, x86: pmem api for ensuring durability of persistent memory updates Message-ID: <20150624120820.GA17542@lst.de> References: <20150622081028.35954.89885.stgit@dwillia2-desk3.jf.intel.com> <20150622082449.35954.91411.stgit@dwillia2-desk3.jf.intel.com> <20150622161754.GC8240@lst.de> <5589374D.9060009@nod.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5589374D.9060009@nod.at> Sender: owner-linux-mm@kvack.org List-ID: To: Richard Weinberger Cc: Christoph Hellwig , Dan Williams , arnd@arndb.de, mingo@redhat.com, bp@alien8.de, hpa@zytor.com, tglx@linutronix.de, ross.zwisler@linux.intel.com, akpm@linux-foundation.org, jgross@suse.com, x86@kernel.org, toshi.kani@hp.com, linux-nvdimm@lists.01.org, benh@kernel.crashing.org, mcgrof@suse.com, konrad.wilk@oracle.com, linux-kernel@vger.kernel.org, stefan.bader@canonical.com, luto@amacapital.net, linux-mm@kvack.org, geert@linux-m68k.org, ralf@linux-mips.org, hmh@hmh.eng.br, mpe@ellerman.id.au, tj@kernel.org, paulus@samba.org On Tue, Jun 23, 2015 at 12:39:09PM +0200, Richard Weinberger wrote: > Not sure if I understand this correctly, is the plan to support pmem also on UML? > At least drivers/block/pmem.c cannot work on UML as it depends on io memory. > > Only x86 seems to have ARCH_HAS_NOCACHE_UACCESS, if UML would offer these methods > what drivers need them? I'm still not sure where it would make sense on UML as > uaccess on UML means ptrace() between host and guest process. Ok, that makese snese. Dan, how about just moving the new pmem helpers from cacheflush.h to a new asm/pmem.h to avoid having them dragged into the um build? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org