Re: [Qemu-devel] [PATCH 3/5] memory: Add RAM_NONPERSISTENT flag

2017-06-22 Thread Dr. David Alan Gilbert
* Eduardo Habkost (ehabk...@redhat.com) wrote: > On Thu, Jun 22, 2017 at 01:14:58PM +0100, Dr. David Alan Gilbert wrote: > > * Eduardo Habkost (ehabk...@redhat.com) wrote: > > > The new flag will make qemu_ram_free() discard the contents of the > > > block. It will be used to let QEMU be configure

Re: [Qemu-devel] [PATCH 3/5] memory: Add RAM_NONPERSISTENT flag

2017-06-22 Thread Eduardo Habkost
On Thu, Jun 22, 2017 at 01:14:58PM +0100, Dr. David Alan Gilbert wrote: > * Eduardo Habkost (ehabk...@redhat.com) wrote: > > The new flag will make qemu_ram_free() discard the contents of the > > block. It will be used to let QEMU be configured to avoid flushing file > > contents to disk when exit

Re: [Qemu-devel] [PATCH 3/5] memory: Add RAM_NONPERSISTENT flag

2017-06-22 Thread Dr. David Alan Gilbert
* Eduardo Habkost (ehabk...@redhat.com) wrote: > The new flag will make qemu_ram_free() discard the contents of the > block. It will be used to let QEMU be configured to avoid flushing file > contents to disk when exiting. As MADV_REMOVE is not always supported, > the new code will try MADV_NOTNE

[Qemu-devel] [PATCH 3/5] memory: Add RAM_NONPERSISTENT flag

2017-06-14 Thread Eduardo Habkost
The new flag will make qemu_ram_free() discard the contents of the block. It will be used to let QEMU be configured to avoid flushing file contents to disk when exiting. As MADV_REMOVE is not always supported, the new code will try MADV_NOTNEEDED in case MADV_REMOVE fails. The new flag will also