From: Peter Maydell <peter.maydell@linaro.org>
To: Aurelio Remonda <aurelio.remonda@tallertechnologies.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Memory on stellaris board
Date: Thu, 11 Feb 2016 13:01:00 +0000 [thread overview]
Message-ID: <CAFEAcA83Aj_eBENbLssko5GKgLzO0tgYOGrMWBcwoU8yruZ5DA@mail.gmail.com> (raw)
In-Reply-To: <CANLsssvtnDNDzFxHah4QqbJpPciNuoP-DgBTbFPr9v+N20=3-Q@mail.gmail.com>
On 11 February 2016 at 12:46, Aurelio Remonda
<aurelio.remonda@tallertechnologies.com> wrote:
> On Fri, Feb 5, 2016 at 2:00 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>> The right way to do this is to set the MachineClass default_ram_size
>> to what you want your default value to be. Then you should calculate
>> the dc0 etc values to expose to the guest based on the ram size
>> (which might be the default or might be user specified).
>
> But stellaris board has a hardcoded dc0 value, when you place the -m flag
> with for example 256M you shouldn't calculate any sram_size from dc0, you
> just assign that as your ram size.
What I am suggesting is that dc0 should not be hardcoded, but
that you should work out what dc0 to use based on the user
provided RAM size.
thanks
-- PMM
next prev parent reply other threads:[~2016-02-11 13:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 13:00 [Qemu-devel] Memory on stellaris board Aurelio Remonda
2016-02-03 13:34 ` Peter Maydell
2016-02-03 13:45 ` Aurelio Remonda
2016-02-05 16:09 ` Aurelio Remonda
2016-02-05 16:23 ` Peter Maydell
2016-02-05 16:55 ` Aurelio Remonda
2016-02-05 17:00 ` Peter Maydell
2016-02-11 12:46 ` Aurelio Remonda
2016-02-11 13:01 ` Peter Maydell [this message]
2016-03-07 19:58 ` Aurelio Remonda
2016-03-07 23:37 ` Peter Maydell
2016-03-09 20:56 ` Aurelio Remonda
2016-03-09 23:24 ` Peter Maydell
2016-03-10 0:23 ` Aurelio Remonda
2016-03-10 1:54 ` Peter Maydell
2016-03-11 14:12 ` Aurelio Remonda
2016-03-11 22:31 ` Peter Maydell
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=CAFEAcA83Aj_eBENbLssko5GKgLzO0tgYOGrMWBcwoU8yruZ5DA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=aurelio.remonda@tallertechnologies.com \
--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).