From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: torvalds@transmeta.com, marcelo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux/i386 boot protocol version 2.03
Date: 09 Dec 2001 11:29:33 -0700 [thread overview]
Message-ID: <m17krww8ky.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200112090922.BAA11252@tazenda.transmeta.com>
In-Reply-To: <200112090922.BAA11252@tazenda.transmeta.com>
"H. Peter Anvin" <hpa@zytor.com> writes:
> The following patch is a fairly small and fully backwards compatible
> change to the i386 boot protocol. It makes the maximum legal initrd
> address explicitly available to the boot loader, so it doesn't have to
> guess. To make matters worse, the current documentation specifies
> 0x3C000000 as the top address (exclusive), but the real address is
> 0x38000000.
>
> This patch:
>
> a) Bumps the boot protocol version number to 2.03;
> b) Adds a field to the boot header which contains the maximum legal
> initrd address;
> c) Slightly reorganizes a couple of macros to make (b) possible;
> d) Documents this change and the actual behaviour for previous
> protocol versions.
This looks reasonable.
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.
Eric
next prev parent reply other threads:[~2001-12-09 18:49 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 [this message]
2001-12-09 21:53 ` H. Peter Anvin
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=m17krww8ky.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=hpa@zytor.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