From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Adrian Reber <adrian@lisas.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/1] Change the default link address for pSeries zImage kernels.
Date: Mon, 23 Jun 2008 19:57:26 +1000 [thread overview]
Message-ID: <1214215046.8011.254.camel@pasglop> (raw)
In-Reply-To: <20080623093024.GA9377@lisas.de>
On Mon, 2008-06-23 at 11:30 +0200, Adrian Reber wrote:
> On Mon, Jun 23, 2008 at 06:13:23PM +1000, 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 moev OF manually by
> > setting real-base.
>
> Does this change also affect kernels for SLOF based systems (JS20, JS21,
> Bimini/Powerstation, QS21, QS22)?
Yes, they use the same zImage.
> To avoid exactly that problem SLOF moved to a bit below 256MB on all
> those platforms (about 220MB). There should be still enough space
> between 64MB and 220MB to boot large kernels. It is, however, decreased
> by 60MB.
That should leave plenty of space...
Cheers,
Ben.
next prev parent reply other threads:[~2008-06-23 9:57 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 [this message]
2008-06-23 12:20 ` Michael Ellerman
2008-06-24 4:20 ` [PATCH v2] " Tony Breeds
2008-07-02 15:04 ` Olaf Hering
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=1214215046.8011.254.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=adrian@lisas.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).