From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiao Guangrong Subject: Re: [PATCH 0/2] add vNVDIMM support for Xen Date: Tue, 29 Dec 2015 23:11:56 +0800 Message-ID: <5682A2BC.6030204@linux.intel.com> References: <1451388527-18009-1-git-send-email-haozhong.zhang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1451388527-18009-1-git-send-email-haozhong.zhang@intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Haozhong Zhang , xen-devel@lists.xensource.com Cc: Eduardo Habkost , Stefano Stabellini , "Michael S. Tsirkin" , Paolo Bonzini , Igor Mammedov , Richard Henderson List-Id: xen-devel@lists.xenproject.org On 12/29/2015 07:28 PM, Haozhong Zhang wrote: > This patch series extends current vNVDIMM implementation to provide > vNVDIMM to HVM domains when QEMU is used as the device model of Xen. > > This patch series is based on upstream qemu rather of qemu-xen, > because vNVDIMM support has not been in qemu-xen (commit f165e58). > > * Following two problem that prevent Xen from directly using current > implementation are solved by this patch series. > > (1) The current way to allocate memory for pc-dimm based vNVDIMM > through file-backend device is not compatible with Xen. Patch 2 > adds another pc-nvdimm device to manage vNVDIMM's memory by > itself. > Let's figure a way to reuse current NVDIMM device mode, two modes completely make the implementation complex and unmaintainable. Also, the way reserving memory region for NVDIMM ACPI needs to be adjusted and that is i am currently working on.