mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olivier Galibert <galibert@pobox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Is the x86-64 kernel size limit real?
Date: Fri, 23 Jun 2006 00:00:57 +0200	[thread overview]
Message-ID: <20060622220057.GB52945@dspnet.fr.eu.org> (raw)
In-Reply-To: <e7f2jq$r17$1@terminus.zytor.com>

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.

  OG.


  reply	other threads:[~2006-06-22 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 20:46 Olivier Galibert
2006-06-22 21:38 ` H. Peter Anvin
2006-06-22 22:00   ` Olivier Galibert [this message]
2006-06-22 22:45     ` H. Peter Anvin
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=20060622220057.GB52945@dspnet.fr.eu.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®