From: Pankaj Gupta <pagupta@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
qemu-devel@nongnu.org, linux-nvdimm@ml01.01.org,
linux-mm@kvack.org, jack@suse.cz,
dan j williams <dan.j.williams@intel.com>,
riel@redhat.com, haozhong zhang <haozhong.zhang@intel.com>,
nilal@redhat.com, kwolf@redhat.com, pbonzini@redhat.com,
ross zwisler <ross.zwisler@intel.com>,
david@redhat.com,
xiaoguangrong eric <xiaoguangrong.eric@gmail.com>
Subject: Re: [Qemu-devel] [RFC] KVM "fake DAX" device flushing
Date: Thu, 12 Oct 2017 06:39:48 -0400 (EDT) [thread overview]
Message-ID: <1776453018.19707347.1507804788144.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20171012085031.GA1959@stefanha-x1.localdomain>
> On Thu, Oct 12, 2017 at 12:21:46AM +0530, Pankaj Gupta wrote:
> > We are sharing the prototype version of 'fake DAX' flushing
> > interface for the initial feedback. This is still work in progress
> > and not yet ready for merging.
> >
> > Protoype right now just implements basic functionality without advanced
> > features with two major parts:
> >
> > - Qemu virtio-pmem device
> > It exposes a persistent memory range to KVM guest which at host side is
> > file
> > backed memory and works as persistent memory device. In addition to this
> > it
> > provides a virtio flushing interface for KVM guest to do a Qemu side sync
> > for
> > guest DAX persistent memory range.
>
> Please post a draft VIRTIO device specification.
Sure! will prepare and share.
Thanks,
Pankaj
>
> The VIRTIO Technical Committee resources and mailing lists are here:
>
> https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=virtio#feedback
>
> Stefan
>
prev parent reply other threads:[~2017-10-12 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 18:51 [Qemu-devel] [RFC] KVM "fake DAX" device flushing Pankaj Gupta
2017-10-11 19:22 ` Dan Williams
2017-10-12 8:50 ` Stefan Hajnoczi
2017-10-12 10:39 ` Pankaj Gupta [this message]
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=1776453018.19707347.1507804788144.JavaMail.zimbra@redhat.com \
--to=pagupta@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=haozhong.zhang@intel.com \
--cc=jack@suse.cz \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=nilal@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riel@redhat.com \
--cc=ross.zwisler@intel.com \
--cc=stefanha@redhat.com \
--cc=xiaoguangrong.eric@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).