From: Ingo Molnar <mingo@elte.hu>
To: Paul Jackson <pj@sgi.com>
Cc: ying.huang@intel.com, hpa@zytor.com, andi@firstfloor.org,
mingo@redhat.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 0/4] x86_64 boot: Add linked listof struct setup_data to boot protocol
Date: Thu, 27 Mar 2008 10:46:48 +0100 [thread overview]
Message-ID: <20080327094648.GA5056@elte.hu> (raw)
In-Reply-To: <20080327042147.15f7ce28.pj@sgi.com>
* Paul Jackson <pj@sgi.com> wrote:
> Ingo wrote:
> > stupidly shortsighted limit ...
>
> Eh ... I don't think all that shortsighted ... that 4096 limit has
> probably been around longer than Linux. Linus or hpa or others would
> know the history better than I do.
the limit for boot parameters is 2048 bytes - the BUILD_WARN_ON() checks
for the sum of the two boot parameter areas. We used empty_zero_page for
boot parameter passing for a near eternity - 2K for the command line
(which used to be clipped - recently upped to true 2048), and 2K for the
boot parameters.
As a historic/nostalgic sidenote: the 2048 limit is not as old as Linux,
version 0.11 of Linux had 512 bytes of special area for boot parameters,
at 0x90000-0x901FF.
having fixed-length 2K buffering ABI between two historically rather
inflexible pieces of software (the bootloader and the kernel), at a very
fragile and under-capable junction of our bootstrap (very early during
bootup) _is_ shortsighted. Granted, it's a difficult area to change but
still it's a nasty limit - as you have found it out first-hand ;-)
Ingo
next prev parent reply other threads:[~2008-03-27 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 7:09 [PATCH -mm 0/4] x86_64 boot: Add linked listof struct setup_data to boot protocol Huang, Ying
2008-03-27 8:32 ` Ingo Molnar
2008-03-27 9:02 ` Paul Jackson
2008-03-27 9:09 ` Ingo Molnar
2008-03-27 9:21 ` Paul Jackson
2008-03-27 9:46 ` Ingo Molnar [this message]
2008-03-27 9:25 ` Huang, Ying
2008-03-27 9:47 ` Ingo Molnar
2008-03-27 16:36 ` 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=20080327094648.GA5056@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pj@sgi.com \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.com \
/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