All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] make the generic Linux loader usable on i386-pc again
Date: Sat, 07 Mar 2009 12:26:34 +0100	[thread overview]
Message-ID: <49B259EA.1050307@gmail.com> (raw)
In-Reply-To: <20090307104856.GC20604@thorin>

Small word about xnu. It needs for norma booting just a quite big amount 
of contiguos memory anywhere below 4GiB. This is typically 64 MiB 
depending on the amount of loaded modules but can be much larger (e.g. 
if using ramdisk)
In the case of resuming from hibernation it needs small amount at 
0x100000 (around 64 kib probably) and a space for compressed hibernation 
image. Depending on system usage prior to hibernation it could be as big 
as the whole memory minus few MiB.
Robert Millan wrote:
> On Fri, Mar 06, 2009 at 10:02:28PM +0200, Vesa Jääskeläinen wrote:
>> Robert Millan wrote:
>>> This patch makes the generic Linux loader usable on i386-pc again.  It
>>> doesn't seem like it's badly needed to spend a bit of time and a bit of
>>> code in adding low memory to the heap, and Vesa's work on the new memory
>>> manager should give a proper solution to this problem.
>>>
>>> I think in the meantime we could just not allocate low mem, assuming
>>> nobody has a problem with that.
>> If this really blocks it I have nothing against it. But could you share
>> a bit insight what kind of memories are required to be where for Linux?
> 
> Sure.  Note that my experience is merely derived from our existing code
> (which I had to in order to produce the initial loader/i386/linux.c).  Linux
> developers reading this (hi Dave ;-)) probably know better.
> 
> There's an area between 0x10000 and 0x90000 which is where
> struct linux_kernel_params needs to be stored.  This includes a statically
> allocated memory map.
> 
> There's an area between 0x100000 and min(0x37FFFFFF,(grub_os_area_addr + grub_os_area_size))
> where the actual Linux image is loaded, as well as the initrd (inmediately after
> it, with some alignment).
> 
> I think that's all.
> 


-- 

Regards
Vladimir 'phcoder' Serbinenko



  reply	other threads:[~2009-03-07 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06 19:19 [PATCH] make the generic Linux loader usable on i386-pc again Robert Millan
2009-03-06 20:02 ` Vesa Jääskeläinen
2009-03-07 10:48   ` Robert Millan
2009-03-07 11:26     ` phcoder [this message]
2009-03-08 12:46   ` Robert Millan

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=49B259EA.1050307@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@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.