From: "Ken'ichi Ohmichi" <oomichi@mxs.nes.nec.co.jp>
To: kexec-ml <kexec@lists.infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
Neil Horman <nhorman@redhat.com>, Vivek Goyal <vgoyal@in.ibm.com>,
Bernhard Walle <bwalle@suse.de>, Don Zickus <dzickus@redhat.com>,
Dan Aloni <da-x@monatomic.org>
Subject: Re: [PATCH 0/3] vmcoreinfo support for dump filtering
Date: Mon, 3 Sep 2007 17:15:08 +0900 [thread overview]
Message-ID: <20070903171508oomichi@mail.jp.nec.com> (raw)
In-Reply-To: <20070822210838oomichi@mail.jp.nec.com>
Hi,
2007/08/22 21:08:38 +0900, Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp> wrote:
>
>Hi Andrew,
>
>This patch set frees the restriction that makedumpfile users should
>install a vmlinux file (including the debugging information) into
>each system.
>
>makedumpfile command is the dump filtering feature for kdump.
>It creates a small dumpfile by filtering unnecessary pages for the
>analysis. To distinguish unnecessary pages, it needs a vmlinux file
>including the debugging information. These days, the debugging package
>becomes a huge file, and it is hard to install it into each system.
>
>To solve the problem, kdump developers discussed it at lkml and kexec-ml.
>As the result, we reached the conclusion that necessary information
>for dump filtering (called "vmcoreinfo") should be embedded into the
>first kernel file and it should be accessed through /proc/vmcore
>during the second kernel.
>(http://www.uwsg.iu.edu/hypermail/linux/kernel/0707.0/1806.html)
>
>Dan Aloni created the patch set for the above implementation.
>(http://www.uwsg.iu.edu/hypermail/linux/kernel/0707.1/1053.html)
>
>And I updated it for multi architectures and memory models.
>(http://lists.infradead.org/pipermail/kexec/2007-August/000479.html)
>
>
>PATCH SET:
>[1/3] [linux] Add vmcoreinfo
> The patch is for linux-2.6.22.
> The patch adds the vmcoreinfo data. Its address and size are output
> to /sys/kernel/vmcoreinfo.
The patch for linux (add-vmcoreinfo.patch) is included in 2.6.23-rc4-mm1.
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc4/2.6.23-rc4-mm1/announce.txt
Thank you for your cooperation.
>[2/3] [kexec-tools] Pass vmcoreinfo's address and size
> The patch is for kexec-tools-testing-20070330.
> (http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/)
> kexec command gets the address and size of the vmcoreinfo data from
> /sys/kernel/vmcoreinfo, and passes them to the second kernel through
> ELF header of /proc/vmcore. When the second kernel is booting, the
> kernel gets them from the ELF header and creates vmcoreinfo's PT_NOTE
> segment into /proc/vmcore.
Horms, could you please merge the above patch ?
>[3/3] [makedumpfile] Extract vmcoreinfo from /proc/vmcore
> The patch is for makedumpfile v1.1.6.
> (https://sourceforge.net/projects/makedumpfile/)
> makedumpfile command extracts the vmcoreinfo data from /proc/vmcore
> and uses it for dump filtering.
I will release the next makedumpfile with the above patch.
Thanks
Ken'ichi Ohmichi
next prev parent reply other threads:[~2007-09-03 8:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 12:08 [PATCH 0/3] vmcoreinfo support for dump filtering Ken'ichi Ohmichi
2007-08-22 12:11 ` [PATCH 1/3] [linux] Add vmcoreinfo Ken'ichi Ohmichi
2007-08-22 12:13 ` [PATCH 2/3] [kexec-tools] Pass vmcoreinfo's address and size Ken'ichi Ohmichi
2007-10-17 2:33 ` Simon Horman
2007-10-17 5:16 ` Ken'ichi Ohmichi
2007-10-17 5:27 ` Andrew Morton
2007-10-17 13:37 ` Simon Horman
2007-10-18 5:37 ` Simon Horman
2007-10-18 9:14 ` tachibana
2007-10-19 3:38 ` Simon Horman
2007-08-22 12:16 ` [PATCH 3/3] [makedumpfile] Extract vmcoreinfo from /proc/vmcore Ken'ichi Ohmichi
2007-08-22 22:40 ` [PATCH 0/3] vmcoreinfo support for dump filtering Andrew Morton
2007-08-23 10:20 ` Ken'ichi Ohmichi
2007-08-23 5:47 ` Vivek Goyal
2007-09-03 8:15 ` Ken'ichi Ohmichi [this message]
2007-10-17 17:19 ` Tony Luck
2007-10-17 20:20 ` Andrew Morton
2007-10-17 21:32 ` Luck, Tony
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=20070903171508oomichi@mail.jp.nec.com \
--to=oomichi@mxs.nes.nec.co.jp \
--cc=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=da-x@monatomic.org \
--cc=dzickus@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=vgoyal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox