From mboxrd@z Thu Jan  1 00:00:00 1970
From: Haozhong Zhang <haozhong.zhang@intel.com>
Subject: Re: [PATCH 0/2] add vNVDIMM support for Xen
Date: Tue, 5 Jan 2016 09:22:49 +0800
Message-ID: <20160105012249.GE3619@hz-desktop.sh.intel.com>
References: <1451388527-18009-1-git-send-email-haozhong.zhang@intel.com>
	<5682A2BC.6030204@linux.intel.com>
	<alpine.DEB.2.02.1601041557250.27577@kaball.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1601041557250.27577@kaball.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Xiao Guangrong <guangrong.xiao@linux.intel.com>, Eduardo Habkost <ehabkost@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>, Igor Mammedov <imammedo@redhat.com>, Richard Henderson <rth@twiddle.net>
List-Id: xen-devel@lists.xenproject.org

On 01/04/16 15:57, Stefano Stabellini wrote:
> On Tue, 29 Dec 2015, Xiao Guangrong wrote:
> > 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.
> 
> I agree
>
Yes, I'm looking at how to make the file-backend device work for Xen.

Haozhong