From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45003) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e2mRz-0003r2-SZ for qemu-devel@nongnu.org; Thu, 12 Oct 2017 18:59:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e2mRz-0006b1-19 for qemu-devel@nongnu.org; Thu, 12 Oct 2017 18:59:35 -0400 Received: from mail-oi0-x232.google.com ([2607:f8b0:4003:c06::232]:47246) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e2mRy-0006al-Os for qemu-devel@nongnu.org; Thu, 12 Oct 2017 18:59:34 -0400 Received: by mail-oi0-x232.google.com with SMTP id h200so10877842oib.4 for ; Thu, 12 Oct 2017 15:59:34 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1111804283.19946669.1507848765955.JavaMail.zimbra@redhat.com> References: <20171012155027.3277-1-pagupta@redhat.com> <20171012155027.3277-3-pagupta@redhat.com> <1567317495.19940236.1507843517318.JavaMail.zimbra@redhat.com> <1363955128.19944709.1507846719987.JavaMail.zimbra@redhat.com> <1507847249.21121.207.camel@redhat.com> <1111804283.19946669.1507848765955.JavaMail.zimbra@redhat.com> From: Dan Williams Date: Thu, 12 Oct 2017 15:59:33 -0700 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pankaj Gupta Cc: Rik van Riel , "linux-kernel@vger.kernel.org" , KVM list , Qemu Developers , linux-nvdimm , Linux MM , Jan Kara , Stefan Hajnoczi , Haozhong Zhang , Nitesh Narayan Lal , Kevin Wolf , Paolo Bonzini , Ross Zwisler , David Hildenbrand , Xiao Guangrong On Thu, Oct 12, 2017 at 3:52 PM, Pankaj Gupta wrote: > Dan, > > I have a query regarding below patch [*]. My assumption is its halted > because of memory hotplug restructuring work? Anything I am missing > here? > > [*] https://www.mail-archive.com/linux-nvdimm@lists.01.org/msg02978.html It's fallen to the back of my queue since the original driving need of platform firmware changing offsets from boot-to-boot is no longer an issue. However, it does mean that you need to arrange for 128MB aligned devm_memremap_pages() ranges for the foreseeable future.