From: Michael Ellerman <michael@ellerman.id.au>
To: Chris Friesen <cbf123@mail.usask.ca>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
kexec@lists.infradead.org, Haren Myneni <hbabu@us.ibm.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: visible memory seems wrong in kexec crash dump kernel
Date: Fri, 12 Jul 2013 11:21:43 +1000 [thread overview]
Message-ID: <20130712012142.GA24112@concordia> (raw)
In-Reply-To: <51DF2229.5010604@mail.usask.ca>
On Thu, Jul 11, 2013 at 03:22:49PM -0600, Chris Friesen wrote:
> On 07/11/2013 02:55 PM, Chris Friesen wrote:
> >Hi,
> >
> >I'm running 2.6.34 with kexec 2.0.1 on a Freescale p5020-based system
> >with 8GB of memory. (It's an embedded system and I can't do much
> >about the fact that it's using older software.)
>
> I should probably clarify this...I may be able to update kexec, I
> can't update the kernel but I can backport more recent code if
> necessary.
>
> Looking at the version of kexec that I have, it seems like where x86
> uses "memmap=" to specify the memory map usable by the capture
> kernel, powerpc does something different.
From memory, it's been years, on powerpc we add properties to the memory
nodes in the device tree that specify which memory is usable. The
properties are called "linux,usable-memory", and in modern kernels they
are read in early_init_dt_scan_memory().
cheers
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-07-12 1:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 20:55 visible memory seems wrong in kexec crash dump kernel Chris Friesen
2013-07-11 21:22 ` Chris Friesen
2013-07-11 22:46 ` Chris Friesen
2013-07-12 1:21 ` Michael Ellerman [this message]
2013-07-12 21:08 ` Chris Friesen
2013-07-12 22:59 ` Chris Friesen
2013-07-13 6:30 ` Chris Friesen
2013-07-14 4:36 ` Michael Ellerman
2013-07-14 5:26 ` Benjamin Herrenschmidt
2013-07-14 23:08 ` Chris Friesen
2013-07-14 23:11 ` Benjamin Herrenschmidt
2013-07-29 23:10 ` Scott Wood
2013-07-31 16:40 ` Friesen, Christopher
2013-07-31 16:50 ` Scott Wood
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=20130712012142.GA24112@concordia \
--to=michael@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=cbf123@mail.usask.ca \
--cc=hbabu@us.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=vgoyal@redhat.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