From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Early memory patch, revised
Date: Wed, 25 Feb 2004 10:38:29 -0800 [thread overview]
Message-ID: <403CEBA5.5020008@zytor.com> (raw)
In-Reply-To: <m1r7wjf22s.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman wrote:
>
> Thanks. :)
>
> Two little tweaks I can think of.
> 1) Can we reserve space between __bss_stop and _end for the page
> tables and the bitmap of memory?
>
> This should make it obvious that the early boot code is touching
> that memory.
>
The bitmap of memory, perhaps, I'll let wli speak to that one. The page
tables shouldn't need to be fixed-sized like what you're proposing;
although the current patch doesn't make use of it, I'd like to in the
future, and this would make it impossible.
> 2) Can we export _end in setup.S so a bootloader can verify the
> kernel + bss will fit in memory?
For what good? Seriously... you're just pushing further into the kernel
the point where you will run completely out of memory during
initialization -- this case dynamic.
There is absolutely no use in trying to pointf*ck this. Really.
-hpa
next prev parent reply other threads:[~2004-02-25 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 5:10 Early memory patch, revised H. Peter Anvin
2004-02-25 18:26 ` Eric W. Biederman
2004-02-25 18:38 ` H. Peter Anvin [this message]
2004-02-25 18:49 ` H. Peter Anvin
2004-02-26 14:56 ` [PATCH] Early memory patch, +accounting Eric W. Biederman
2004-02-26 18:02 ` H. Peter Anvin
2004-03-01 7:06 ` Eric W. Biederman
2004-02-26 6:16 ` Early memory patch, revised Eric W. Biederman
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=403CEBA5.5020008@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.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.