public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: torvalds@transmeta.com, marcelo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux/i386 boot protocol version 2.03
Date: Sun, 09 Dec 2001 13:53:12 -0800	[thread overview]
Message-ID: <3C13DD48.3070206@zytor.com> (raw)
In-Reply-To: <200112090922.BAA11252@tazenda.transmeta.com> <m17krww8ky.fsf@frodo.biederman.org>

Eric W. Biederman wrote:
> 
> A couple of notes:
> 1) The minimum safe ramdisk address is 8MB (since 2.4.10).  On low
>    mem machines you can get away with placing a ramdisk lower.  But we
>    don't do any checking in our initial 8MB memory map.
> 2) If we use units of kilobytes instead of bytes for this we don't
>    loose any precision and gain the ability to put a ramdisk in high
>    memory without bumping the protocol version.
> 3) If we are going to export the maximum address we should also export
>    the minimum address.
> 

(2) I guess I'm not so concerned with the ramdisk in highmem since it is 
extrememly unlikely any boot loader will be able to take advantage of 
that.  It could be an issue for x86-64, I guess.

(3) Contradicts (1) as well as issues with older kernels.  Keep in mind 
what happens if you violate this limit: the bootloader should be loading 
the initrd as high as possible, so the only difference is if you get the 
error message from the boot loader or from the kernel later.  If you're 
going to export a limit, you better make sure it's right; "8MB except on 
low memory configurations" doesn't cut it.  It's exactly on those low 
memory configurations that this limit matters *at all*.

	-hpa




  reply	other threads:[~2001-12-09 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09  9:22 Linux/i386 boot protocol version 2.03 H. Peter Anvin
2001-12-09 18:29 ` Eric W. Biederman
2001-12-09 21:53   ` H. Peter Anvin [this message]
2001-12-09 22:20     ` Eric W. Biederman
2001-12-09 23:13       ` H. Peter Anvin
2001-12-09 23:18         ` Eric W. Biederman
2001-12-09 21:56   ` H. Peter Anvin

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=3C13DD48.3070206@zytor.com \
    --to=hpa@zytor.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@kernel.org \
    --cc=torvalds@transmeta.com \
    /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