mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Liu Hua <sdu.liu@huawei.com>
To: <linux@arm.linux.org.uk>, <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: <will.deacon@arm.com>, <kexec@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <wangnan0@huawei.com>,
	<peifeiyue@huawei.com>, <sdu.liu@huawei.com>, <liusdu@126.com>
Subject: [RFC PATCH 0/2] transfer sparse memory related values
Date: Wed, 7 May 2014 21:27:12 +0800	[thread overview]
Message-ID: <1399469234-54925-1-git-send-email-sdu.liu@huawei.com> (raw)

Now different platforms may have different SECTION_SIZE_BITS and
MAX_PHYSMEM_BITS. But linux passes nothing related to the 
vmcore.

User space tools such as makedumpfile needs these to deal with 
the vmcore. So we must define these when compiling. So if we 
deal with aother vmcore. We may need to recompile the tools.

These patch series make kernel pass related infomation to
the user space tools, via vmcore. And makedumpfile can
get these when parsing vmcore. So the makdumpfile becomes
more compatible to vmcore with different section size.


Liu Hua (1):
  kdump: add sparse memory related values to vmcore
  makedumpfile: get additional information from vmcore

 kernel/kexec.c | 3 +++
 makedumpfile.c | 17 +++++++++++++++++
 makedumpfile.h |  2 ++
 3 files changed, 22 insertions(+)

-- 
1.9.0


             reply	other threads:[~2014-05-07 13:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 13:27 Liu Hua [this message]
2014-05-07 13:27 ` [RFC PATCH 1/2] kdump: add sparse memory related values to vmcore Liu Hua
2014-05-07 13:27 ` [RFC PATCH 2/2] makedumpfile: get additional information from vmcore Liu Hua
2014-05-13  6:21   ` Atsushi Kumagai
2014-05-13  7:25     ` Liu hua
2014-05-14  7:53       ` Atsushi Kumagai
2014-05-14 12:33         ` Liu hua
2014-05-15  2:12           ` 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=1399469234-54925-1-git-send-email-sdu.liu@huawei.com \
    --to=sdu.liu@huawei.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=liusdu@126.com \
    --cc=peifeiyue@huawei.com \
    --cc=wangnan0@huawei.com \
    --cc=will.deacon@arm.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

all inboxes | Powered by JetHome®