From: Paolo Bonzini <pbonzini@redhat.com>
To: Liviu Ionescu <ilg@livius.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] extensions to the -m memory option
Date: Fri, 29 May 2015 13:08:19 +0200 [thread overview]
Message-ID: <556848A3.6010905@redhat.com> (raw)
In-Reply-To: <2816EEF2-0256-4B49-8811-74EFB3016CD4@livius.net>
On 29/05/2015 00:11, Liviu Ionescu wrote:
> for more flexibility, in the new Cortex-M implementation I'm working on, I can overwrite the vendor defined MCU internal SRAM size by using:
>
> -m sizeK
>
> I'm trying to find a way to also overwrite the internal flash size and the first idea I had was to extend the "-m" command like:
>
> -m sizeK,flash=sizeK
>
> would this be ok?
>
> for more readability I would prefer something like:
>
> --memory ram=sizeK,flash=sizeK
>
> any other suggestions?
If the flash is persistent, it should be tied to either "-pflash" (NOR)
or "-mtd" (NAND). Just using a different image then results in resizing
the flash.
Paolo
next prev parent reply other threads:[~2015-05-29 11:08 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
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 [this message]
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=556848A3.6010905@redhat.com \
--to=pbonzini@redhat.com \
--cc=ilg@livius.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).