Re: [Qemu-devel] [RFC] extensions to the -m memory option

[Paolo Bonzini]

On 01/06/2015 11:23, Liviu Ionescu wrote:
> however, the desired behaviour is
> 
> - the -pflash specifies a file path, no need for size
> - when emulation starts, if -pflash is used and the file exists, its content 
> is loaded as initial flash content
> - when emulation ends, if -pflash is used, the flash content is saved to this 
> file
> - if the gdb server is used, it must allow for some parts of the flash to be 
> overwritten by GDB, for example the bootloader is located either in low or 
> high memory, and the rest of the flash is reprogrammed by the debugger with 
> each session, the bootloader (and the rest of the flash) remaining persistent 
> between sessions.
> 
> does the existing -pflash implementation matches this expected use case? 

Yes, entirely.  Saving flash content can be avoided by using "-drive
if=pflash,snapshot=on,file=...".

So it looks like you have a use for both -kernel (ELF) and -pflash (raw
image).

Paolo