[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC] extensions to the -m memory option
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [RFC] extensions to the -m memory option |
Date: |
Mon, 01 Jun 2015 09:19:40 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 |
On 31/05/2015 16:05, Liviu Ionescu wrote:
> I followed your advice and I ended up with the following:
>
> - I added a new type "cortexm-mcu" that I use as parent for all Cortex-M MCU
> objects (like "STM32F103RB")
>
> - I added the following properties to this type:
>
> cortexm-mcu.flash-sizeK=uint32
This should be okay, though more on this below.
> cortexm-mcu.ram-sizeK=uint32
This is the same as "-m", thus probably unnecessary, but I understand
that the megabyte default unit in -m can be a bit annoying for you.
However, there were patches on the list to set a different default for
each machine.
> cortexm-mcu.cpu-model=str
This is the same as "-cpu"
> cortexm-mcu.kernel-filename=str
This is the same as "-kernel" i.e. "-machine kernel=str".
Regarding flash, I'm still curious about some questions I have...
1) who initializes flash contents?
2) can the running program modify flash at run-time? if so, how? and
if so, are the writes supposed to stick around from one QEMU invocation
to the next?
Paolo
Re: [Qemu-devel] [RFC] extensions to the -m memory option, Liviu Ionescu, 2015/06/01