Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753390AbbFXMgX (ORCPT ); Wed, 24 Jun 2015 08:36:23 -0400 Received: from a.ns.miles-group.at ([95.130.255.143]:65275 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752762AbbFXMgK (ORCPT ); Wed, 24 Jun 2015 08:36:10 -0400 Message-ID: <558AA42B.2050505@nod.at> Date: Wed, 24 Jun 2015 14:35:55 +0200 From: Richard Weinberger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Christoph Hellwig CC: 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@ml01.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 Subject: Re: [PATCH v5 6/6] arch, x86: pmem api for ensuring durability of persistent memory updates 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> <20150624120820.GA17542@lst.de> In-Reply-To: <20150624120820.GA17542@lst.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1144 Lines: 25 Am 24.06.2015 um 14:08 schrieb Christoph Hellwig: > 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? If UML does not build for whatever reason, please CC me. I'll happily help out. Historically UML includes a lot stuff it should not. So, untangling header dependencies does often wonders. :-) Thanks, //richard -- 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/