From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757604AbdJLXHe (ORCPT ); Thu, 12 Oct 2017 19:07:34 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58334 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753671AbdJLXHa (ORCPT ); Thu, 12 Oct 2017 19:07:30 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 0940A5F298C Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=pagupta@redhat.com Date: Thu, 12 Oct 2017 19:07:27 -0400 (EDT) From: Pankaj Gupta To: Dan Williams 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 Message-ID: <1755911209.19947416.1507849647657.JavaMail.zimbra@redhat.com> In-Reply-To: References: <20171012155027.3277-1-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> Subject: Re: [RFC 2/2] KVM: add virtio-pmem driver MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.116.29, 10.4.195.6] Thread-Topic: add virtio-pmem driver Thread-Index: OPXMJQIyOLMgTTJdGJa018FITcSt1A== X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Thu, 12 Oct 2017 23:07:30 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > 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. o.k I will provide 128MB aligned pages to devm_memremap_pages() function. Thanks, Pankaj