From: Vivek Goyal <vgoyal@redhat.com>
To: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: Ken'ichi <oomichi@mxs.nes.nec.co.jp>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Onkar N Mahajan <onmahaja@in.ibm.com>,
Kexec-ml <kexec@lists.infradead.org>,
Haren Myneni <hbabu@us.ibm.com>,
Tachibana-san <tachibana@mxm.nes.nec.co.jp>,
Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH v4] makedumpfile: Support to filter dump for kernels that use CONFIG_SPARSEMEM_VMEMMAP
Date: Fri, 22 Nov 2013 08:44:49 -0500 [thread overview]
Message-ID: <20131122134449.GB4046@redhat.com> (raw)
In-Reply-To: <20131122123155.28272.38600.stgit@localhost.localdomain>
On Fri, Nov 22, 2013 at 06:01:55PM +0530, Hari Bathini wrote:
> Makedumpfile fails to filter dump for kernels build with CONFIG_SPARSEMEM_VMEMMAP
> enabled as it fails to do vmemmap translations. So far, makedumpfile on ppc64 never
> had to deal with vmemmap addresses (vmemmap regions) seperately to filter ppc64
> crash dumps as vmemmap regions where mapped in zone normal. But with the inclusion
> of CONFIG_SPARSEMEM_VMEMMAP config option in recent kernels, vmemmap memory regions
> are mapped outside zone normal. There is a need to handle vmemmap to physical address
> translation seperately in this scenario. This patch provides support in makedumpfile
> tool to do vmemmap to physical address translation when vmemmap regions are mapped
> outside zone normal. Some kernel symbols are needed in vmcoreinfo for this changes to
> be effective. The kernel patch that adds the necessary symbols to vmcoreinfo has been
> posted to linuxppc devel mailing list. This patch is influenced by vmemmap to physical
> address translation support code in crash utility. It is has been tested successfully
> at all dump filtering levels on kernel dumps that have CONFIG_SPARSEMEM_VMEMMAP enabled
> and kernel dumps with CONFIG_SPARSEMEM_VMEMMAP disabled as well. Also, successfully
> tested dump filtering on already filtered vmcores (re-filtering).
Please column width smaller (say 70) for changelogs. This looks messy.
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2013-11-22 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 12:31 [PATCH v4] makedumpfile: Support to filter dump for kernels that use CONFIG_SPARSEMEM_VMEMMAP Hari Bathini
2013-11-22 13:44 ` Vivek Goyal [this message]
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=20131122134449.GB4046@redhat.com \
--to=vgoyal@redhat.com \
--cc=ananth@in.ibm.com \
--cc=dyoung@redhat.com \
--cc=hbabu@us.ibm.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=onmahaja@in.ibm.com \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=tachibana@mxm.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 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.