From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] target/xtensa: xtfpga: provide default memory sizes
Date: Wed, 21 Nov 2018 19:25:49 +0100 [thread overview]
Message-ID: <d8733646-4ee4-df53-24c1-b89f1d8a1569@redhat.com> (raw)
In-Reply-To: <CAMo8Bf+oCDyOmpj9mNZF1nL3X7JgZU5fidDd-LZNGEG9dOPHew@mail.gmail.com>
On 21/11/18 13:21, Max Filippov wrote:
> Hi Philippe,
>
> thanks for your review.
>
> On Wed, Nov 21, 2018 at 4:00 AM Philippe Mathieu-Daudé
> <philmd@redhat.com> wrote:
>> On 20/11/18 21:38, Max Filippov wrote:
>>> static const TypeInfo xtfpga_lx200_nommu_type = {
>>> @@ -632,6 +636,7 @@ static void xtfpga_ml605_class_init(ObjectClass *oc, void *data)
>>> mc->init = xtfpga_ml605_init;
>>> mc->max_cpus = 4;
>>> mc->default_cpu_type = XTENSA_DEFAULT_CPU_TYPE;
>>> + mc->default_ram_size = 256 * MiB;
>>
>> Isn't it 512 MB for the ML605?
>
> There's 512MB on the board, but the Tensilica prototyping
> user's guide for the ML605 only documents 256MB in the memory
> map section. But now that you've mentioned it I recall that in reality
> both ML605 and KC705 had all onboard memory minus 128MB
> mapped for cores with MMU.
>
>>> }
>>>
>>> static const TypeInfo xtfpga_ml605_type = {
>>> @@ -648,6 +653,7 @@ static void xtfpga_ml605_nommu_class_init(ObjectClass *oc, void *data)
>>> mc->init = xtfpga_ml605_nommu_init;
>>> mc->max_cpus = 4;
>>> mc->default_cpu_type = XTENSA_DEFAULT_CPU_NOMMU_TYPE;
>>> + mc->default_ram_size = 256 * MiB;
>>
>> Ditto.
>
> For noMMU cores there's only 256MB window available for
> the system memory, so it's capped at 256MB.
This totally makes sense.
>
> I'll send an updated v2.
Thanks!
Phil.
prev parent reply other threads:[~2018-11-21 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 20:38 [Qemu-devel] [PATCH] target/xtensa: xtfpga: provide default memory sizes Max Filippov
2018-11-21 12:00 ` Philippe Mathieu-Daudé
2018-11-21 12:21 ` Max Filippov
2018-11-21 18:25 ` Philippe Mathieu-Daudé [this message]
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=d8733646-4ee4-df53-24c1-b89f1d8a1569@redhat.com \
--to=philmd@redhat.com \
--cc=jcmvbkbc@gmail.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).