From: "Alex Bennée" <alex.bennee@linaro.org>
To: Damien Hedde <damien.hedde@greensocs.com>
Cc: "Alistair Francis" <alistair@alistair23.me>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] generic-loader: remove the ram_size limit when a loading binary file
Date: Wed, 06 Oct 2021 16:40:32 +0100 [thread overview]
Message-ID: <871r4yf9eh.fsf@linaro.org> (raw)
In-Reply-To: <4fd0ab8a-7edb-a855-09ce-312ab2057325@greensocs.com>
Damien Hedde <damien.hedde@greensocs.com> writes:
> On 10/6/21 13:49, Philippe Mathieu-Daudé wrote:
>> On 10/6/21 13:37, Damien Hedde wrote:
>>> Right now, we cannot load some binary file if it is bigger than the
>>> machine's ram size. This limitation only occurs when loading a
>>> binary file: we can load a corresponding elf file without this
>>> limitation.
>>>
>>> This is an issue for machines that have small ram or do not use the
>>> ram_size feature at all.
>>>
>>> Also get rid of "hw/boards.h" include, since we needed it only
>>> to access `current_machine`.
>>>
>>> Fixes: e481a1f63c9 ("generic-loader: Add a generic loader")
>>> Signed-off-by: Damien Hedde <damien.hedde@greensocs.com>
>>> ---
>>>
>>> Hi Alistair,
>>>
>>> I found this while experimenting with a ram_size=0 machine.
>
>
>
>> Where are you loading your file?
>>
>
> In a rom.
>
> The loader does not check at all that we are loading to the machine's
> ram. It just check the size for the raw binary file format.
It does beg the question of why you don't just construct your ROM file
with the image in place there? Is this just a development convenience?
--
Alex Bennée
next prev parent reply other threads:[~2021-10-06 16:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 11:37 [PATCH] generic-loader: remove the ram_size limit when a loading binary file Damien Hedde
2021-10-06 11:49 ` Philippe Mathieu-Daudé
2021-10-06 11:58 ` Damien Hedde
2021-10-06 15:40 ` Alex Bennée [this message]
2021-10-07 7:54 ` Philippe Mathieu-Daudé
2021-10-07 10:12 ` Damien Hedde
2021-10-07 11:01 ` Philippe Mathieu-Daudé
2021-10-07 6:41 ` Alistair Francis
2021-10-07 7:59 ` Philippe Mathieu-Daudé
2021-10-08 10:38 ` Damien Hedde
2021-10-10 23:06 ` Alistair Francis
2021-10-07 10:12 ` Damien Hedde
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=871r4yf9eh.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=alistair@alistair23.me \
--cc=damien.hedde@greensocs.com \
--cc=philmd@redhat.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).