From: "H. Peter Anvin" <hpa@zytor.com>
To: Olivier Galibert <galibert@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Is the x86-64 kernel size limit real?
Date: Thu, 22 Jun 2006 15:45:41 -0700 [thread overview]
Message-ID: <449B1D95.4090705@zytor.com> (raw)
In-Reply-To: <20060622220057.GB52945@dspnet.fr.eu.org>
Olivier Galibert wrote:
> On Thu, Jun 22, 2006 at 02:38:02PM -0700, H. Peter Anvin wrote:
>> It turns out x86-64, unlike i386, does still have a hardcoded limit,
>> but the limit in build.c is wrong:
>>
>> kernel/head.S:
>> /* 40MB kernel mapping. The kernel code cannot be bigger than that.
>> When you change this change KERNEL_TEXT_SIZE in page.h too. */
>> /* (2^48-(2*1024*1024*1024)-((2^39)*511)-((2^30)*510)) = 0 */
>>
>> So this should be replaced by KERNEL_TEXT_SIZE in page.h, or better,
>> this should be done dynamically in x86-64 too.
>
> Interesting. KERNEL_TEXT_SIZE wouldn't work though, since that's the
> decompressed size while the 4Mb limit is on the compressed size. As a
> datapoint, though, the uncompressed image is 15.7Mb, for a 4.5Mb
> compressed image.
>
Oh, right. In fact, the 4 MB "limit" for i386 was actually an 8 MB uncompressed limit,
with a 2:1 ratio assumed... not very accurate.
The limit should be removed from the boot tools; since we're talking uncompressed limits
those should be tested in the linker script if anywhere.
-hpa
next prev parent reply other threads:[~2006-06-22 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 20:46 Is the x86-64 kernel size limit real? Olivier Galibert
2006-06-22 21:38 ` H. Peter Anvin
2006-06-22 22:00 ` Olivier Galibert
2006-06-22 22:45 ` H. Peter Anvin [this message]
2006-06-22 23:02 ` Olivier Galibert
2006-06-23 0:27 ` Eduard-Gabriel Munteanu
2006-06-22 21:39 ` H. Peter Anvin
2006-06-22 21:52 ` Olivier Galibert
2006-06-23 1:18 ` Eduard-Gabriel Munteanu
2006-06-23 12:49 ` Andi Kleen
2006-06-25 17:19 ` 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=449B1D95.4090705@zytor.com \
--to=hpa@zytor.com \
--cc=galibert@pobox.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.