All of lore.kernel.org
 help / color / mirror / Atom feed
From: Haozhong Zhang <haozhong.zhang@intel.com>
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>
Subject: Re: [PATCH 0/2] add vNVDIMM support for Xen
Date: Tue, 5 Jan 2016 09:22:49 +0800	[thread overview]
Message-ID: <20160105012249.GE3619@hz-desktop.sh.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1601041557250.27577@kaball.uk.xensource.com>

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

  reply	other threads:[~2016-01-05  1:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-29 11:28 [PATCH 0/2] add vNVDIMM support for Xen Haozhong Zhang
2015-12-29 11:28 ` [PATCH 1/2] pc-nvdimm: implement pc-nvdimm device abstract Haozhong Zhang
2015-12-29 11:28 ` [PATCH 2/2] pc-nvdimm acpi: build ACPI tables for pc-nvdimm devices Haozhong Zhang
2016-01-04 16:01   ` Stefano Stabellini
2016-01-04 21:10     ` Konrad Rzeszutek Wilk
2016-01-05 11:00       ` Stefano Stabellini
2016-01-05 14:01         ` Haozhong Zhang
2016-01-06 14:50           ` Konrad Rzeszutek Wilk
2016-01-06 15:24             ` Haozhong Zhang
2016-01-05  2:14     ` Haozhong Zhang
2015-12-29 15:11 ` [PATCH 0/2] add vNVDIMM support for Xen Xiao Guangrong
2016-01-04 15:57   ` Stefano Stabellini
2016-01-05  1:22     ` Haozhong Zhang [this message]
2016-01-04 15:56 ` Stefano Stabellini
2016-01-05  1:33   ` Haozhong Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160105012249.GE3619@hz-desktop.sh.intel.com \
    --to=haozhong.zhang@intel.com \
    --cc=ehabkost@redhat.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=imammedo@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rth@twiddle.net \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.