From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: d.hatayama@jp.fujitsu.com, kexec@lists.infradead.org
Subject: [PATCH 0/2] makdumpfile: Add "mem=" handling for physical memory dumps
Date: Tue, 25 Mar 2014 17:12:31 +0100 [thread overview]
Message-ID: <20140325171231.6cbaa2e5@holzheu> (raw)
There are dump mechansims like s390 stand-alone dump or KVM virsh dump
that write the physical memory of a machine and that are not aware of the
dumped operating system. If for the Linux kernel of the dumped system the
"mem=" kernel parameter has been specified, the "max_mapnr" that
makedumpfile gets from the ELF header can be bigger than the maximum page
frame number used by the dumped Linux kernel. This can lead to makedumpfile
errors on s390x and can also lead to extended dump times and sizes.
The following two patches for version 1.5.5 fix these issues:
Michael Holzheu (2):
makedumpfile: Fix zero checking of get_mm_sparsemem()
makedumpfile: Use max_pfn from mem_map array
makedumpfile.c | 36 ++++++++++++++++++++++++++++++------
1 file changed, 30 insertions(+), 6 deletions(-)
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2014-03-25 16:12 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=20140325171231.6cbaa2e5@holzheu \
--to=holzheu@linux.vnet.ibm.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
/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