From: Paul Mackerras <paulus@samba.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Clean up some linker and symbol usage
Date: Fri, 28 Mar 2008 10:14:30 +1100 [thread overview]
Message-ID: <18412.10838.984230.869068@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803271452540.12382@blarg.am.freescale.net>
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?
Or do we only have the 32MB starting at the 32MB point in the lmb
system in that case?
Paul.
next prev parent reply other threads:[~2008-03-27 23:14 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 [this message]
2008-03-28 0:45 ` Michael Ellerman
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=18412.10838.984230.869068@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).