From: David Hildenbrand <david@redhat.com>
To: Pankaj Gupta <pagupta@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
qemu-devel@nongnu.org, linux-nvdimm@ml01.01.org
Cc: jack@suse.cz, stefanha@redhat.com, dan.j.williams@intel.com,
riel@surriel.com, haozhong.zhang@intel.com, nilal@redhat.com,
kwolf@redhat.com, pbonzini@redhat.com, ross.zwisler@intel.com,
xiaoguangrong.eric@gmail.com, hch@infradead.org, mst@redhat.com,
niteshnarayanlal@hotmail.com, lcapitulino@redhat.com,
imammedo@redhat.com, eblake@redhat.com
Subject: Re: [RFC v3 0/2] kvm "fake DAX" device flushing
Date: Tue, 28 Aug 2018 14:13:24 +0200 [thread overview]
Message-ID: <1328e543-0276-8f33-1744-8baa053023c4@redhat.com> (raw)
In-Reply-To: <20180713075232.9575-1-pagupta@redhat.com>
On 13.07.2018 09:52, Pankaj Gupta wrote:
> This is RFC V3 for 'fake DAX' flushing interface sharing
> for review. This patchset has two parts:
>
> - Guest virtio-pmem driver
> Guest driver reads persistent memory range from paravirt device
> and registers with 'nvdimm_bus'. 'nvdimm/pmem' driver uses this
> information to allocate persistent memory range. Also, we have
> implemented guest side of VIRTIO flushing interface.
>
> - 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 virtio device handling of flushing
> interface. KVM guest performs Qemu side asynchronous sync using
> this interface.
>
> Changes from RFC v2:
> - Add flush function in the nd_region in place of switching
> on a flag - Dan & Stefan
> - Add flush completion function with proper locking and wait
> for host side flush completion - Stefan & Dan
> - Keep userspace API in uapi header file - Stefan, MST
> - Use LE fields & New device id - MST
> - Indentation & spacing suggestions - MST & Eric
> - Remove extra header files & add licensing - Stefan
>
> Changes from RFC v1:
> - Reuse existing 'pmem' code for registering persistent
> memory and other operations instead of creating an entirely
> new block driver.
> - Use VIRTIO driver to register memory information with
> nvdimm_bus and create region_type accordingly.
> - Call VIRTIO flush from existing pmem driver.
>
> Details of project idea for 'fake DAX' flushing interface is
> shared [2] & [3].
>
> Pankaj Gupta (2):
> Add virtio-pmem guest driver
> pmem: device flush over VIRTIO
>
> [1] https://marc.info/?l=linux-mm&m=150782346802290&w=2
> [2] https://www.spinics.net/lists/kvm/msg149761.html
> [3] https://www.spinics.net/lists/kvm/msg153095.html
>
> drivers/nvdimm/nd.h | 1
> drivers/nvdimm/pmem.c | 4
> drivers/nvdimm/region_devs.c | 24 +++-
> drivers/virtio/Kconfig | 9 +
> drivers/virtio/Makefile | 1
> drivers/virtio/virtio_pmem.c | 190 +++++++++++++++++++++++++++++++++++++++
> include/linux/libnvdimm.h | 5 -
> include/linux/virtio_pmem.h | 44 +++++++++
> include/uapi/linux/virtio_ids.h | 1
> include/uapi/linux/virtio_pmem.h | 40 ++++++++
> 10 files changed, 310 insertions(+), 9 deletions(-)
>
Hi Pankaj,
do you have a branch for the QEMU part somewhere available? I want to
see how this works with MemoryDevice changes.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2018-08-28 12:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 7:52 [RFC v3 0/2] kvm "fake DAX" device flushing Pankaj Gupta
2018-07-13 7:52 ` [RFC v3 1/2] libnvdimm: Add flush callback for virtio pmem Pankaj Gupta
2018-07-13 20:35 ` Luiz Capitulino
2018-07-16 8:13 ` Pankaj Gupta
2018-07-13 7:52 ` [RFC v3 2/2] virtio-pmem: Add virtio pmem driver Pankaj Gupta
2018-07-13 20:38 ` Luiz Capitulino
2018-07-16 11:46 ` [Qemu-devel] " Pankaj Gupta
2018-07-16 14:03 ` Luiz Capitulino
2018-07-16 15:11 ` Pankaj Gupta
2018-07-17 13:11 ` Stefan Hajnoczi
2018-07-18 7:05 ` Pankaj Gupta
2018-07-13 7:52 ` [RFC v3] qemu: Add virtio pmem device Pankaj Gupta
2018-07-18 12:55 ` Luiz Capitulino
2018-07-19 5:48 ` [Qemu-devel] " Pankaj Gupta
2018-07-19 12:16 ` Stefan Hajnoczi
2018-07-19 12:48 ` Luiz Capitulino
2018-07-19 12:57 ` Luiz Capitulino
2018-07-20 13:04 ` Pankaj Gupta
2018-07-19 13:58 ` David Hildenbrand
2018-07-19 15:48 ` Luiz Capitulino
2018-07-20 13:02 ` Pankaj Gupta
2018-07-19 12:39 ` Luiz Capitulino
2018-07-24 16:13 ` Eric Blake
2018-07-25 5:01 ` [Qemu-devel] " Pankaj Gupta
2018-07-25 12:19 ` Eric Blake
2018-07-25 12:47 ` Pankaj Gupta
2018-08-28 12:13 ` David Hildenbrand [this message]
2018-08-28 12:39 ` [Qemu-devel] [RFC v3 0/2] kvm "fake DAX" device flushing Pankaj Gupta
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=1328e543-0276-8f33-1744-8baa053023c4@redhat.com \
--to=david@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=eblake@redhat.com \
--cc=haozhong.zhang@intel.com \
--cc=hch@infradead.org \
--cc=imammedo@redhat.com \
--cc=jack@suse.cz \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=mst@redhat.com \
--cc=nilal@redhat.com \
--cc=niteshnarayanlal@hotmail.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riel@surriel.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).