public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduard-Gabriel Munteanu <maxdamage@aladin.ro>
To: Olivier Galibert <galibert@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is the x86-64 kernel size limit real?
Date: Fri, 23 Jun 2006 01:18:57 +0000	[thread overview]
Message-ID: <449B4181.9060907@aladin.ro> (raw)
In-Reply-To: <20060622215205.GA52945@dspnet.fr.eu.org>

*This message was transferred with a trial version of CommuniGate(r) Pro*
Olivier Galibert wrote:
> *This message was transferred with a trial version of CommuniGate(r) Pro*
> *This message was transferred with a trial version of CommuniGate(r) Pro*
> On Fri, Jun 23, 2006 at 12:27:08AM +0000, Eduard-Gabriel Munteanu wrote:
> 
>>*This message was transferred with a trial version of CommuniGate(r) Pro*
>>Olivier Galibert wrote:
>>
>>
>>>which shows two things:
>>>1- a8f5034540195307362d071a8b387226b410469f should have a x86-64 version
>>>2- the limit looks entirely artificial
>>>
>>>So, is removing the limit prone to bite me?
>>>
>>> OG.
>>
>>The build system merely tries to warn you it's not going to fit on a 
>>floppy disk. "bzImage" means "Big zImage", not "bz2-compressed Image", 
>>so unless you're building a floppy disk, don't use zImage.
> 
> 
> You failed to notice the "is_big_kernel ? 0x40000 : ..." part, which
> means the 4Mb limit is for bzImage.  And the "die(...)" part, which
> means it's not a warning but an error.
> 

Sorry, I thought it was you who made that patch.

  reply	other threads:[~2006-06-22 22:15 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
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 [this message]
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=449B4181.9060907@aladin.ro \
    --to=maxdamage@aladin.ro \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox