From: Paolo Bonzini <pbonzini@redhat.com>
To: Liviu Ionescu <ilg@livius.net>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [RFC] extensions to the -m memory option
Date: Mon, 01 Jun 2015 09:19:40 +0200 [thread overview]
Message-ID: <556C078C.1070709@redhat.com> (raw)
In-Reply-To: <B0DDE4EF-980D-4D20-9612-C8F0D374B417@livius.net>
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
next prev parent reply other threads:[~2015-06-01 7:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 22:11 [Qemu-devel] [RFC] extensions to the -m memory option Liviu Ionescu
2015-05-29 9:11 ` Igor Mammedov
2015-05-29 19:22 ` Liviu Ionescu
2015-05-29 19:32 ` Peter Maydell
2015-05-29 20:26 ` Liviu Ionescu
2015-05-29 21:40 ` Peter Maydell
2015-05-29 21:49 ` Liviu Ionescu
2015-05-30 9:39 ` Peter Crosthwaite
2015-05-31 14:05 ` Liviu Ionescu
2015-05-31 18:45 ` Peter Crosthwaite
2015-05-31 20:59 ` Liviu Ionescu
2015-05-31 22:10 ` Peter Crosthwaite
2015-05-31 22:24 ` Liviu Ionescu
2015-05-31 22:27 ` Peter Crosthwaite
2015-05-31 22:36 ` Liviu Ionescu
2015-05-31 22:59 ` Liviu Ionescu
2015-05-31 23:44 ` Peter Crosthwaite
2015-06-01 0:14 ` Liviu Ionescu
2015-06-01 2:26 ` Peter Crosthwaite
2015-06-01 7:08 ` Liviu Ionescu
2015-06-01 20:36 ` Liviu Ionescu
2015-06-03 12:31 ` Liviu Ionescu
2015-06-03 17:48 ` Peter Crosthwaite
2015-06-08 7:12 ` Markus Armbruster
2015-06-02 10:15 ` Liviu Ionescu
2015-06-02 10:32 ` Peter Crosthwaite
2015-06-02 10:42 ` Peter Maydell
2015-06-02 11:01 ` Liviu Ionescu
2015-06-02 20:23 ` Peter Crosthwaite
2015-06-01 7:19 ` Paolo Bonzini [this message]
2015-06-01 8:30 ` Liviu Ionescu
2015-06-01 8:53 ` Paolo Bonzini
2015-06-01 9:16 ` Peter Crosthwaite
2015-06-01 9:21 ` Peter Maydell
2015-06-01 9:45 ` Liviu Ionescu
2015-06-01 9:23 ` Liviu Ionescu
2015-06-01 9:41 ` Paolo Bonzini
2015-05-29 11:08 ` Paolo Bonzini
2015-05-29 19:27 ` Liviu Ionescu
2015-05-29 19:33 ` Paolo Bonzini
2015-05-29 20:13 ` Liviu Ionescu
2015-05-29 20:15 ` Paolo Bonzini
2015-05-29 20:38 ` Liviu Ionescu
2015-05-30 9:55 ` Peter Crosthwaite
2015-05-30 10:32 ` Paolo Bonzini
2015-05-30 20:20 ` Peter Crosthwaite
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=556C078C.1070709@redhat.com \
--to=pbonzini@redhat.com \
--cc=ilg@livius.net \
--cc=imammedo@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.