From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>,
Andrew Strauss <astrauss11@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2] semihosting/arm-compat: remove heuristic softmmu SYS_HEAPINFO
Date: Sun, 13 Jun 2021 15:58:56 +0100 [thread overview]
Message-ID: <CAFEAcA_NPtRT1YdcyuRYpa8bDuWTt53a0-QyJz8CEb4FnAXsgg@mail.gmail.com> (raw)
In-Reply-To: <87y2bggwqd.fsf@linaro.org>
On Fri, 11 Jun 2021 at 18:03, Alex Bennée <alex.bennee@linaro.org> wrote:
>
>
> Peter Maydell <peter.maydell@linaro.org> writes:
>
> > On Thu, 10 Jun 2021 at 15:16, Alex Bennée <alex.bennee@linaro.org> wrote:
> >>
> >>
> >> Peter Maydell <peter.maydell@linaro.org> writes:
> >> > (2) find the largest contiguous extent of that RAM which
> >> > is not covered by a ROM blob, by iterating through the
> >> > ROM blob data. (This sounds like one of those slightly
> >> > irritating but entirely tractable algorithms questions :-))
> >>
> >> Does that assume that any rom blob (so anything from -kernel, -pflash or
> >> -generic-loader?) will have also included space for guest data and bss?
> >
> > Yes; the elf loader code creates rom blobs whose rom->romsize
> > covers both initialized data from the ELF file and space to
> > be zeroed.
>
> Hmm I'm not seeing the RAM get bifurcated by the loader. The flatview
> only has one RAM block in my test case and it covers the whole of RAM.
I dunno what you're tracing here, but rom blobs do not affect
the MemoryRegion setup (which can be rom, ram,the romd "writes
go to callbacks, reads are host memory" hybrid, or whatever).
ROM blobs are just a list of "write this data into memory at
this address", which gets iterated through on reset to write
the data into the RAM/ROM/whatever.
-- PMM
prev parent reply other threads:[~2021-06-13 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 10:26 [PATCH v2] semihosting/arm-compat: remove heuristic softmmu SYS_HEAPINFO Alex Bennée
2021-06-10 10:57 ` Peter Maydell
2021-06-10 13:55 ` Alex Bennée
2021-06-10 12:32 ` Peter Maydell
2021-06-10 14:12 ` Alex Bennée
2021-06-10 14:25 ` Peter Maydell
2021-06-11 17:01 ` Alex Bennée
2021-06-13 14:58 ` Peter Maydell [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=CAFEAcA_NPtRT1YdcyuRYpa8bDuWTt53a0-QyJz8CEb4FnAXsgg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=astrauss11@gmail.com \
--cc=qemu-arm@nongnu.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.