From: Hollis Blanchard <hollisb@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/5] uImage: return base load address
Date: Thu, 20 Nov 2008 16:13:15 -0600 [thread overview]
Message-ID: <1227219195.16341.7.camel@localhost.localdomain> (raw)
In-Reply-To: <4925DF47.3060102@codemonkey.ws>
On Thu, 2008-11-20 at 16:05 -0600, Anthony Liguori wrote:
> Hollis Blanchard wrote:
> > Return the base address at which the image was loaded so that
> callers may keep
> > track of currently occupied guest memory.
> >
>
> Why is it that you need this information if no other callers have needed
> it before?
As far as I can see, other users are making assumptions about maximum
kernel size and simply hardcoding some addresses.
For example arm_load_kernel() seems to always load the initrd at 8MB,
regardless of where the ELF or uImage kernel was loaded. (In the case of
a "flat" kernel, that's loaded at 0x1000, and probably isn't bigger than
8MB...)
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-11-20 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 19:34 [Qemu-devel] [v2] improvements in uImage loading Hollis Blanchard
2008-11-20 19:34 ` [Qemu-devel] [PATCH 1/5] uImage: don't leak file data or file descriptor Hollis Blanchard
2008-11-20 19:34 ` [Qemu-devel] [PATCH 2/5] uImage: implement gzip support Hollis Blanchard
2008-11-20 19:34 ` [Qemu-devel] [PATCH 3/5] uImage: return base load address Hollis Blanchard
2008-11-20 22:05 ` Anthony Liguori
2008-11-20 22:13 ` Hollis Blanchard [this message]
2008-11-20 19:34 ` [Qemu-devel] [PATCH 4/5] uImage: rename load_uboot() to load_uimage() Hollis Blanchard
2008-11-20 19:34 ` [Qemu-devel] [PATCH 5/5] uImage: only try to load 'kernel' images Hollis Blanchard
2008-11-20 20:27 ` [Qemu-devel] [v2] improvements in uImage loading Jean-Christophe PLAGNIOL-VILLARD
2008-11-20 22:15 ` Anthony Liguori
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=1227219195.16341.7.camel@localhost.localdomain \
--to=hollisb@us.ibm.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).