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.
- Guest virtio-pmem driver
Reads persistent memory range from paravirt device and reserves system memory map.
It also allocates a block device corresponding to the pmem range which is accessed
by DAX capable file systems. (file system support is still pending).
We shared the project idea for 'fake DAX' flushing interface here .
Based on suggestions here , we implemented guest 'virtio-pmem'
driver and Qemu paravirt device.
Work yet to be done:
- Separate out the common code used by ACPI pmem interface and
- In pmem device memmap allocation and working. There is some parallel work
going on upstream related to 'memory_hotplug restructuring'  and also
a memory section alignment issue .
- Provide DAX capable file-system(ext4 & XFS) support.
- Qemu device flush functionality.
- Qemu live migration work when host page cache is used.
- Multiple virtio-pmem disks support.
Prototype implementation for feedback:
Qemu : https://github.com/pagupta/qemu/commit/9c428db1e1076970e097e2b0ef8afe5250...
Please provide feedback. Also, I would be attending KVM Forum in Prague from (25-27 Oct).
If you are attending KVM forum/Linux conference, I would love to have a discussion on
and future work.