From: Baoquan He <bhe@redhat.com>
To: kexec@lists.infradead.org
Cc: kumagai-atsushi@mxc.nes.nec.co.jp, Baoquan He <bhe@redhat.com>,
vgoyal@redhat.com
Subject: [Patch v3 0/7] add a new interface to show the memory usage of 1st kernel
Date: Mon, 28 Jul 2014 16:19:59 +0800 [thread overview]
Message-ID: <1406535606-16303-1-git-send-email-bhe@redhat.com> (raw)
Recently people complained that they don't know how to decide how
much disk size need be reserved for kdump. E.g there are lots of
machines with different memory size, if the memory usage information
of current system can be shown, that can help them to make an estimate
how much storage space need be reserved.
In this patchset, a new interface is added into makedumpfile. By the
help of this, people can know the page number of memory in different
use. The implementation is analyzing the "System Ram" and "kernel text"
program segment of /proc/kcore excluding the crashkernel range, then
calculating the page number of different kind per vmcoreinfo.
Previouly, patchset v1 was posted. And patch 7/7 has a change in v2.
So several changes are made in this v3 post per comments from Vivek
and Atsushi.
[patch 3/7] preparation functions for parsing vmcoreinfo
v1->v3:
Since get_kernel_version need be called to get page_offset
before initial() in mem_usage code flow, and surely it will be called
inside initial() again. Add a static variable to avoid this duplicate
calling.
[patch 5/7] prepare the dump loads for kcore analysis
v1->v3:
Fix the compiler warnings.
[patch 6/7] implement a function to print the memory usage
v1->v3:
Adjust the printing content and format of dumpable page numbers per Vivek's
comments.
[patch 7/7]
v1->v2:
Set info->dump_level=MAX_DUMP_LEVEL, with MAX_DUMP_LEVEL all kinds of
memory can be calculated.
v2->v3:
Add the description of this feature into help message and man page.
Baoquan He (7):
initialize pfn_memhole in get_num_dumpable_cyclic
functions to get crashkernel memory range
preparation functions for parsing vmcoreinfo
set vmcoreinfo for kcore
prepare the dump loads for kcore analysis
implement a function to print the memory usage
add a new interface to show the memory usage of 1st kernel
elf_info.c | 231 +++++++++++++++++++++++++++++++++++++++++++++++++++++
elf_info.h | 3 +
makedumpfile.8 | 17 ++++
makedumpfile.c | 247 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
makedumpfile.h | 10 +++
print_info.c | 8 ++
6 files changed, 516 insertions(+)
--
1.8.5.3
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2014-07-28 8:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 8:19 Baoquan He [this message]
2014-07-28 8:20 ` [Patch v3 1/7] initialize pfn_memhole in get_num_dumpable_cyclic Baoquan He
2014-07-28 8:20 ` [Patch v3 2/7] functions to get crashkernel memory range Baoquan He
2014-08-01 7:32 ` Atsushi Kumagai
2014-08-12 9:25 ` bhe
2014-07-28 8:20 ` [Patch v3 3/7] preparation functions for parsing vmcoreinfo Baoquan He
2014-08-01 7:12 ` Atsushi Kumagai
2014-08-12 9:46 ` bhe
2014-08-12 10:01 ` bhe
2014-08-14 7:37 ` Atsushi Kumagai
2014-08-14 8:15 ` bhe
2014-07-28 8:20 ` [Patch v3 4/7] set vmcoreinfo for kcore Baoquan He
2014-08-01 7:12 ` Atsushi Kumagai
2014-08-12 10:08 ` bhe
2014-07-28 8:20 ` [Patch v3 5/7] prepare the dump loads for kcore analysis Baoquan He
2014-08-01 7:12 ` Atsushi Kumagai
2014-08-12 10:10 ` bhe
2014-07-28 8:20 ` [Patch v3 6/7] implement a function to print the memory usage Baoquan He
2014-07-28 8:20 ` [Patch v3 7/7] add a new interface to show the memory usage of 1st kernel Baoquan He
2014-07-29 12:43 ` Vivek Goyal
2014-07-31 2:32 ` Baoquan He
2014-08-01 7:12 ` Atsushi Kumagai
2014-08-12 10:14 ` bhe
2014-08-21 10:31 ` bhe
2014-08-26 2:28 ` Atsushi Kumagai
2014-08-26 3:22 ` bhe
2014-08-26 6:25 ` Petr Tesarik
2014-08-26 14:12 ` bhe
2014-09-02 6:20 ` Atsushi Kumagai
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=1406535606-16303-1-git-send-email-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox