From: Olaf Hering <olaf@aepfle.de>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH v2] Change the default link address for pSeries zImage kernels.
Date: Wed, 2 Jul 2008 17:04:32 +0200 [thread overview]
Message-ID: <20080702150432.GA5910@aepfle.de> (raw)
In-Reply-To: <4ca08ab3df251d90440c962ef15ead1a72d75f05.1214276944.git.tony@bakeyournoodle.com>
On Tue, Jun 24, Tony Breeds wrote:
> Currently we set the start of the .text section to be 4Mb for pSeries.
> In situations where the zImage is > 8Mb we'll fail to boot (due to
> overlapping with OF). Move .text in a zImage from 4MB to 64MB (well past OF).
>
> We still will not be able to load large zImage unless we also move OF,
> to that end, add a note to the zImage ELF to move OF to 32Mb. If this
> is the very first kernel booted then we'll need to move OF manually by
> setting real-base.
Setting real-base to what?
What currently happens with a large boot file is:
Firmware loads the zImage at load-base, finds that the ELF file is too
large to fit into the memory window and stops.
With your patch, firmware loads 12566528 bytes, and starts the zImage.
The result is a truncated file, the initrd will be corrupted, kernel
panic in populate_rootfs().
The only system where firmware relocates itself from 12MB to 32MB is a
p640 with firmware version NAN04194.
All other systems seem to ignore the NOTE section, real-base remains at
0xc00000
So I do not think your patch is a real improvement,
clear error vs. silent corruption.
Do you happen to know how to automate the changing the value of
real-base? The addnote change has appearently no effect on recent
systems.
Olaf
next prev parent reply other threads:[~2008-07-02 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 8:13 [PATCH 1/1] Change the default link address for pSeries zImage kernels Tony Breeds
2008-06-23 8:16 ` Tony Breeds
2008-06-23 9:30 ` Adrian Reber
2008-06-23 9:57 ` Benjamin Herrenschmidt
2008-06-23 12:20 ` Michael Ellerman
2008-06-24 4:20 ` [PATCH v2] " Tony Breeds
2008-07-02 15:04 ` Olaf Hering [this message]
2008-07-04 3:14 ` Tony Breeds
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=20080702150432.GA5910@aepfle.de \
--to=olaf@aepfle.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=tony@bakeyournoodle.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;
as well as URLs for NNTP newsgroup(s).