From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Alexander van Heukelum <heukelum@mailshack.com>,
Mike Travis <travis@sgi.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, heukelum@fastmail.fm
Subject: Re: [PATCH 1/2] boot: increase stack size for kernel boot loader decompressor -- payload_length
Date: Thu, 10 Apr 2008 13:37:00 -0700 [thread overview]
Message-ID: <47FE7A6C.1070405@zytor.com> (raw)
In-Reply-To: <86802c440804101334j4b69373dv172ab72b072dc4a0@mail.gmail.com>
Yinghai Lu wrote:
>>
>> FWIIW, i've been booting allyesconfig bzImages for a long time (with
>> only minimal amount of drivers disabled - mostly old ISA ones that
>> assume the presence of the real hardware), and they boot and work fine
>> on both 32-bit and 64-bit typical whitebox PCs. That means huge bzImages
>> that decompresses into a ~41 MB kernel image. I'd expect that to be a
>> rather severe test of the decompressor.
>
> payload_offset and payload_length in arch/x86/boot/head.S
> seems to be used by bootloader to seat the bzImage. or just use size
> of bzImage
>
payload_offset/payload_length are used by loaders for nonstandard
platform loaders which don't actually load a bzImage.
> long term, should add one field after payload_length like
> payload_unzip_length to make bootloader or kexec what buffer size
> needed.
You can look at the payload headers for that.
-hpa
next prev parent reply other threads:[~2008-04-10 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 20:34 [PATCH 1/2] boot: increase stack size for kernel boot loader decompressor -- payload_length Yinghai Lu
2008-04-10 20:37 ` H. Peter Anvin [this message]
2008-04-10 21:15 ` Yinghai Lu
2008-04-10 21:46 ` H. Peter Anvin
2008-04-10 21:48 ` Yinghai Lu
2008-04-10 22:14 ` H. Peter Anvin
2008-04-10 22:55 ` Yinghai Lu
2008-04-10 22:57 ` 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=47FE7A6C.1070405@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=heukelum@fastmail.fm \
--cc=heukelum@mailshack.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=yhlu.kernel@gmail.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 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.