linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Chandru <chandru@in.ibm.com>
To: kexec@lists.infradead.org, linuxppc-dev@ozlabs.org
Subject: [PATCH 0/4] kdump : add support for ibm, dynamic-reconfiguration-memory for kexec/kdump
Date: Tue, 8 Jul 2008 00:14:15 +0530	[thread overview]
Message-ID: <200807080014.15648.chandru@in.ibm.com> (raw)

Following is a patch series that contains changes for kexec/kdump on Power6 
machines. Power6 machines have most of their memory represented 
in /proc/device-tree/ibm,dynamic-reconfiguration-memory node. kexec-tools 
currently read only memory@ nodes of device-tree.  Patch 1/4 contains changes 
in the kernel. Patch {2,3,4}/4 are changes for kexec-tools.  The kernel 
changes are similar to what was earlier present for memory@ nodes 
for 'linux,usable-memory' property.  Unlike memory@ nodes, since now there is 
one node under which most of the memory ranges are represented ( 
ibm,dynamic-memory) , I have appended the lmb entry number to 
the 'linux,usable-memory' string so as to identify usable-memory ranges in 
the device-tree. 

Signed-off-by: Chandru Siddalingappa <chandru@in.ibm.com>

                 reply	other threads:[~2008-07-07 18:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200807080014.15648.chandru@in.ibm.com \
    --to=chandru@in.ibm.com \
    --cc=kexec@lists.infradead.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).