linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>,
	Geoff Levand <geoff@infradead.org>,
	James Morse <james.morseatarm.com@hactar>,
	kexec@lists.infradead.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v20 14/14] Documentation: dt: usable-memory and elfcorehdr nodes for arm64 kexec
Date: Tue, 28 Jun 2016 13:59:59 +1000	[thread overview]
Message-ID: <1467086399.32607.5.camel@ellerman.id.au> (raw)
In-Reply-To: <9127562.8x2DzY0I6N@hactar>

On Mon, 2016-06-27 at 15:22 -0300, Thiago Jung Bauermann wrote:
> Am Donnerstag, 23 Juni 2016, 17:54:49 schrieb Geoff Levand:
> > +linux,usable-memory
> > +-------------------
> > +
> > +This property is set on PowerPC and arm64 by kexec-tools during kdump
> > +to tell the crash kernel the base address of its reserved area of memory,
> > and +the size. e.g.
> > +
> > +/ {
> > +	chosen {
> > +		linux,usable-memory = <0x9 0xf0000000 0x0 0x10000000>;
> > +	};
> > +};
> 
> On powerpc, linux,usable-memory isn't in /chosen. It is put by kexec-tools 
> in each /memory node and has the same format as the reg property. During 
> early boot, the kernel goes through the /memory nodes to find usable memory 
> and for each node, if there's a linux,usable-memory property it will use it 
> instead of the reg property to find the ranges of memory it can use (see 
> early_init_dt_scan_memory in drivers/of/fdt.c).

Yep that sounds right to me.

Added in:

ba7594852f4e ("[PATCH] powerpc: Add support for "linux,usable-memory" on memory nodes")

cheers

      reply	other threads:[~2016-06-28  4:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1466702804.git.geoff@infradead.org>
     [not found] ` <e212cd53fdf9d09923408eb906fe0228d22432a9.1466702804.git.geoff@infradead.org>
2016-06-27 18:22   ` [PATCH v20 14/14] Documentation: dt: usable-memory and elfcorehdr nodes for arm64 kexec Thiago Jung Bauermann
2016-06-28  3:59     ` Michael Ellerman [this message]

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=1467086399.32607.5.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=bauerman@linux.vnet.ibm.com \
    --cc=geoff@infradead.org \
    --cc=james.morseatarm.com@hactar \
    --cc=kexec@lists.infradead.org \
    --cc=linuxppc-dev@lists.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).