[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 4/5] memory: Add 'persistent' parameter to memor
From: |
Eduardo Habkost |
Subject: |
Re: [Qemu-devel] [PATCH 4/5] memory: Add 'persistent' parameter to memory_region_init_ram_from_file() |
Date: |
Thu, 22 Jun 2017 09:41:48 -0300 |
User-agent: |
Mutt/1.8.0 (2017-02-23) |
On Thu, Jun 22, 2017 at 01:26:49PM +0100, Dr. David Alan Gilbert wrote:
> * Eduardo Habkost (address@hidden) wrote:
> > Make it possible to set the RAM_NONPERSISTENT flag on the RAMBlock when
> > mapping a file.
> >
> > Signed-off-by: Eduardo Habkost <address@hidden>
>
> Reviewed-by: Dr. David Alan Gilbert <address@hidden>
>
> A little confusing having a persistent flag passed in but setting a
> NONPERSISTENT flag.
>
> One thing to watch out for is the other effect, for example I think
> doing an MADV_REMOVE will zero the file; if that's a ROM file that
> would probably be bad; but your description of persistent=false
> might make sense for a ROM file since it wont be changed.
Good point. Sounds like a good idea to reword the documentation to
mentiuon that in addition to making data not written back, contents
might be destroyed.
--
Eduardo
- [Qemu-devel] [PATCH 0/5] hostmem-file: Add "persistent" option, Eduardo Habkost, 2017/06/14
- [Qemu-devel] [PATCH 1/5] vl: Clean up user-creatable objects when exiting, Eduardo Habkost, 2017/06/14
- [Qemu-devel] [PATCH 2/5] memory: Allow RAM up to block->max_length to be discarded, Eduardo Habkost, 2017/06/14
- [Qemu-devel] [PATCH 3/5] memory: Add RAM_NONPERSISTENT flag, Eduardo Habkost, 2017/06/14
- [Qemu-devel] [PATCH 4/5] memory: Add 'persistent' parameter to memory_region_init_ram_from_file(), Eduardo Habkost, 2017/06/14
- [Qemu-devel] [PATCH 5/5] hostmem-file: Add "persistent" option, Eduardo Habkost, 2017/06/14
- Re: [Qemu-devel] [PATCH 0/5] hostmem-file: Add "persistent" option, no-reply, 2017/06/14