From: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
To: Simon Horman <horms@verge.net.au>, Kexec-ml <kexec@lists.infradead.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Suzuki Poulose <suzuki@in.ibm.com>
Subject: [PATCH 0/2] kexec: Limit the crash memory ranges according to first kernel's memory limit.
Date: Wed, 29 Aug 2012 13:54:35 +0530 [thread overview]
Message-ID: <20120829082201.19391.15191.stgit@mars.in.ibm.com> (raw)
So far powerpc kernel never exported memory limit information which is
reflected by mem= kernel cmdline option. Hence, kexec-tools always use
to build ELF header for entire system RAM generating a dump bigger than
the actual memory used by the first kernel.
The proposed upstream kernel patch at
https://lists.ozlabs.org/pipermail/linuxppc-dev/2012-August/100500.html
now exports memory limit information through /proc/device-tree file.
The above patch is still in discussion.
This patch series now reads the memory limit information from
device-tree file if present and limits the crash memory ranges accordingly.
Tested these patches on ppc32(ppc440) and ppc64 with a kernel patch by Suzuki.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Tested-by: Suzuki K. Poulose <suzuki@in.ibm.com>
---
Mahesh Salgaonkar (2):
kexec: Respect memory limit while building crash memory ranges on ppc32.
kexec: Respect memory limit while building crash memory ranges on ppc64
kexec/arch/ppc/crashdump-powerpc.c | 14 ++++++++---
kexec/arch/ppc/crashdump-powerpc.h | 1 +
kexec/arch/ppc/kexec-ppc.c | 48 ++++++++++++++++++++++++++++++++++++
kexec/arch/ppc64/crashdump-ppc64.c | 11 ++++++++
kexec/arch/ppc64/crashdump-ppc64.h | 1 +
kexec/arch/ppc64/kexec-ppc64.c | 28 +++++++++++++++++++++
6 files changed, 99 insertions(+), 4 deletions(-)
--
-Mahesh
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2012-08-29 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 8:24 Mahesh J Salgaonkar [this message]
2012-08-29 8:24 ` [PATCH 1/2] kexec: Respect memory limit while building crash memory ranges on ppc32 Mahesh J Salgaonkar
2012-08-29 8:24 ` [PATCH 2/2] kexec: Respect memory limit while building crash memory ranges on ppc64 Mahesh J Salgaonkar
2012-10-24 3:18 ` [PATCH 0/2] kexec: Limit the crash memory ranges according to first kernel's memory limit Mahesh Jagannath Salgaonkar
2012-11-13 3:36 ` Baoquan
2012-11-14 9:31 ` Baoquan
2012-11-30 3:08 ` Mahesh Jagannath Salgaonkar
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=20120829082201.19391.15191.stgit@mars.in.ibm.com \
--to=mahesh@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=suzuki@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.