From: Michael Ellerman <michael@ellerman.id.au>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Clean up some linker and symbol usage
Date: Fri, 28 Mar 2008 11:45:38 +1100 [thread overview]
Message-ID: <1206665138.8173.3.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <18412.10838.984230.869068@cargo.ozlabs.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Fri, 2008-03-28 at 10:14 +1100, Paul Mackerras wrote:
> Kumar Gala writes:
>
> > @@ -1124,7 +1124,7 @@ void __init early_init_devtree(void *params)
> > parse_early_param();
> >
> > /* Reserve LMB regions used by kernel, initrd, dt, etc... */
> > - lmb_reserve(PHYSICAL_START, __pa(klimit) - PHYSICAL_START);
> > + lmb_reserve(__pa(_stext), _end - _stext);
>
> In the kdump case where the kernel starts at the 32MB point
> (physical), wouldn't we want to reserve the first 32MB of RAM so that
> it can't get allocated and used for random things? Doesn't that first
> 32MB contain the old kernel that we want to write out?
For kdump there is nMB of memory reserved at 32MB for the 2nd kernel,
and that's all it gets, all of the other memory is the old kernel text
or the old kernel's data.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-28 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 19:53 [PATCH] [POWERPC] Clean up some linker and symbol usage Kumar Gala
2008-03-27 23:14 ` Paul Mackerras
2008-03-28 0:45 ` Michael Ellerman [this message]
2008-03-28 1:52 ` Kumar Gala
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=1206665138.8173.3.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--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).