From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Manoel <mrabran@linux.vnet.ibm.com>,
Pavel Roskin <proski@gnu.org>,
Carlos Roberto do Nascimento Costa <crncosta@linux.vnet.ibm.com>
Subject: Re: PPC64 mlongcall gcc flag
Date: Thu, 6 Nov 2008 16:12:46 +0100 [thread overview]
Message-ID: <20081106151246.GD24460@thorin> (raw)
In-Reply-To: <1225905915.26835.71.camel@localhost.localdomain>
On Wed, Nov 05, 2008 at 11:25:15AM -0600, Hollis Blanchard wrote:
>
> Module memory is allocated by grub_malloc(), but as you can see at
> http://svn.savannah.gnu.org/viewvc/trunk/grub2/kern/ieee1275/init.c?revision=1806&root=grub&view=markup the GRUB heap capped at 4MB (I don't mean size, I mean the end of the heap).
It's not really capped at 4 MB. It will cap it only when an heuristic tells it
there's still enough room for heap:
/* Avoid claiming anything above HEAP_MAX_ADDR, if possible. */
if ((addr < HEAP_MAX_ADDR) && /* if it's too late, don't bother */
(addr + len > HEAP_MAX_ADDR) && /* if it wasn't available anyway, don't bother */
(total + (HEAP_MAX_ADDR - addr) > HEAP_MIN_SIZE)) /* only limit ourselves when we can afford to */
Argueably, this is not my best piece of code... today I'd have implemented a
payload relocator (like the one used by loader/i386/pc/multiboot.c) just so we
can happily use everything in /memory/available as heap.
And I'd even advice doing the same for powerpc (sharing code with i386 if
possible).
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-11-06 15:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 20:52 PPC64 Hollis Blanchard
2008-10-21 22:04 ` PPC64 Pavel Roskin
2008-10-21 22:40 ` PPC64 Hollis Blanchard
2008-10-23 5:25 ` PPC64 Pavel Roskin
2008-10-23 15:06 ` PPC64 Hollis Blanchard
2008-10-23 16:52 ` PPC64 Pavel Roskin
2008-10-23 18:00 ` PPC64 Manoel
2008-10-23 19:08 ` PPC64 Hollis Blanchard
2008-10-24 12:10 ` PPC64 Manoel
2008-10-24 14:51 ` PPC64 Hollis Blanchard
2008-10-24 21:53 ` PPC64 Manoel
2008-10-27 17:19 ` PPC64 Pavel Roskin
2008-11-04 16:05 ` PPC64 Manoel
2008-11-04 16:12 ` PPC64 Hollis Blanchard
2008-11-04 18:18 ` PPC64 mlongcall gcc flag Manoel
2008-11-04 18:21 ` Manoel
2008-11-04 19:16 ` Robert Millan
2008-11-04 23:48 ` Pavel Roskin
2008-11-05 9:43 ` Robert Millan
2008-11-05 15:35 ` Pavel Roskin
2008-11-05 17:25 ` Hollis Blanchard
2008-11-05 19:27 ` Manoel
2008-11-06 15:12 ` Robert Millan [this message]
2008-11-06 17:42 ` Manoel
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=20081106151246.GD24460@thorin \
--to=rmh@aybabtu.com \
--cc=crncosta@linux.vnet.ibm.com \
--cc=grub-devel@gnu.org \
--cc=mrabran@linux.vnet.ibm.com \
--cc=proski@gnu.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.