From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: Simon Horman <horms@verge.net.au>
Cc: Chandru <chandru@in.ibm.com>, kexec@lists.infradead.org
Subject: Re: [PATCH 0/3] kdump: add support for ibm, dynamic-reconfiguration-memory for kexec/kdump
Date: Tue, 30 Sep 2008 16:08:13 +0530 [thread overview]
Message-ID: <48E20195.9090306@in.ibm.com> (raw)
In-Reply-To: <200809241718.59719.chandru@in.ibm.com>
Chandru wrote:
> /proc/device-tree on power6 machines has ibm,dynamic-reconfiguration-memory
> node which stores in it the memory representation for most part of the system
> memory. This memory was earlier represented in 'memory@' nodes of the device
> tree. Following patch series makes kexec-tools aware of this dynamic
> reconfiguration memory node. These patches were sent earlier for RFC. In
> addition to this, a change in the kernel was also required. The kernel change
> has been accepted in powerpc git tree.
> http://git.kernel.org/?p=linux/kernel/git/paulus/powerpc.git;a=commit;h=cf00085d8045cddd80a8aabad97de96fa8131793
> Some part of the patch here is re-organization of the existing code to
> accommodate dynamic reconf memory.
>
>
I tested this patch series on a ppc64 box and they work fine.
Without these patches i get a zero size vmcore on a power(power6)
box which has support for dynamic-reconfiguration-memory.
Horms could you please consider this patch series and merge them
if found suitable.
Regards
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-09-30 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 11:48 [PATCH 0/3] kdump: add support for ibm, dynamic-reconfiguration-memory for kexec/kdump Chandru
2008-09-30 10:38 ` Sachin P. Sant [this message]
2008-10-08 1:59 ` Simon Horman
2008-10-08 22:29 ` Simon Horman
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=48E20195.9090306@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=chandru@in.ibm.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.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