Re: [Qemu-devel] [RFC v2 0/2] kvm "fake DAX" device flushing

2018-06-04 Thread David Hildenbrand
On 01.06.2018 14:24, Igor Mammedov wrote: > On Wed, 25 Apr 2018 16:54:12 +0530 > Pankaj Gupta wrote: > > [...] >> - 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

Re: [Qemu-devel] [RFC v2 0/2] kvm "fake DAX" device flushing

2018-06-03 Thread Pankaj Gupta
Hi Igor, > > [...] > > - 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

Re: [Qemu-devel] [RFC v2 0/2] kvm "fake DAX" device flushing

2018-06-01 Thread Igor Mammedov
On Wed, 25 Apr 2018 16:54:12 +0530 Pankaj Gupta wrote: [...] > - 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

[Qemu-devel] [RFC v2 0/2] kvm "fake DAX" device flushing

2018-04-25 Thread Pankaj Gupta
This is RFC V2 for 'fake DAX' flushing interface sharing for review. This patchset has two main 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