Re: [Qemu-devel] [RFC v2] qemu: Add virtio pmem device

2018-04-26 Thread no-reply
Hi, This series failed docker-build@min-glib build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180425112415.12327-4-pagu...@redhat.com Subject: [Qemu-devel] [RFC v2] qemu: Add

Re: [Qemu-devel] [RFC v2] qemu: Add virtio pmem device

2018-04-26 Thread Pankaj Gupta
> > +static void virtio_pmem_flush(VirtIODevice *vdev, VirtQueue *vq) > > +{ > > +VirtQueueElement *elem; > > +VirtIOPMEM *pmem = VIRTIO_PMEM(vdev); > > +HostMemoryBackend *backend = MEMORY_BACKEND(pmem->memdev); > > +int fd = memory_region_get_fd(>mr); > > + > > +elem =

Re: [Qemu-devel] [RFC v2] qemu: Add virtio pmem device

2018-04-26 Thread Stefan Hajnoczi
On Wed, Apr 25, 2018 at 04:54:15PM +0530, Pankaj Gupta wrote: > +static void virtio_pmem_flush(VirtIODevice *vdev, VirtQueue *vq) > +{ > +VirtQueueElement *elem; > +VirtIOPMEM *pmem = VIRTIO_PMEM(vdev); > +HostMemoryBackend *backend = MEMORY_BACKEND(pmem->memdev); > +int fd =

Re: [Qemu-devel] [RFC v2] qemu: Add virtio pmem device

2018-04-25 Thread Pankaj Gupta
> > On 04/25/2018 06:24 AM, Pankaj Gupta wrote: > > This patch adds virtio-pmem Qemu device. > > > > This device presents memory address range > > information to guest which is backed by file > > backend type. It acts like persistent memory > > device for KVM guest. Guest can perform read > >

Re: [Qemu-devel] [RFC v2] qemu: Add virtio pmem device

2018-04-25 Thread Pankaj Gupta
> > Hi, > > > > Compile failures are because Qemu 'Memory-Device changes' are not yet > > in qemu master. As mentioned in Qemu patch message patch is > > dependent on 'Memeory-device' patches by 'David Hildenbrand'. > > > On 04/25/2018 06:24 AM, Pankaj Gupta wrote: > > This PV device code is

Re: [Qemu-devel] [RFC v2] qemu: Add virtio pmem device

2018-04-25 Thread Eric Blake
On 04/25/2018 06:24 AM, Pankaj Gupta wrote: > This patch adds virtio-pmem Qemu device. > > This device presents memory address range > information to guest which is backed by file > backend type. It acts like persistent memory > device for KVM guest. Guest can perform read > and persistent

Re: [Qemu-devel] [RFC v2] qemu: Add virtio pmem device

2018-04-25 Thread Eric Blake
On 04/25/2018 06:58 AM, Pankaj Gupta wrote: > > Hi, > > Compile failures are because Qemu 'Memory-Device changes' are not yet > in qemu master. As mentioned in Qemu patch message patch is > dependent on 'Memeory-device' patches by 'David Hildenbrand'. On 04/25/2018 06:24 AM, Pankaj Gupta

Re: [Qemu-devel] [RFC v2] qemu: Add virtio pmem device

2018-04-25 Thread Pankaj Gupta
t. Please find the details below. > > Type: series > Message-id: 20180425112415.12327-4-pagu...@redhat.com > Subject: [Qemu-devel] [RFC v2] qemu: Add virtio pmem device > > === TEST SCRIPT BEGIN === > #!/bin/bash > # Testing script will be invoked under the git checkout w

[Qemu-devel] [RFC v2] qemu: Add virtio pmem device

2018-04-25 Thread Pankaj Gupta
This patch adds virtio-pmem Qemu device. This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX