From: Olivier Galibert <galibert@pobox.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is the x86-64 kernel size limit real?
Date: Fri, 23 Jun 2006 01:02:19 +0200 [thread overview]
Message-ID: <20060622230219.GA61221@dspnet.fr.eu.org> (raw)
In-Reply-To: <449B1D95.4090705@zytor.com>
On Thu, Jun 22, 2006 at 03:45:41PM -0700, H. Peter Anvin wrote:
> 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.
Probably yeah. And the two build.c files should become one too.
There is version drift already. I'm not a x86-64 maintainer though :-)
OG.
next prev parent reply other threads:[~2006-06-22 23:02 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
2006-06-22 22:45 ` H. Peter Anvin
2006-06-22 23:02 ` Olivier Galibert [this message]
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=20060622230219.GA61221@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=hpa@zytor.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®