From: Dave Anderson <anderson@redhat.com>
To: kexec@lists.infradead.org
Subject: Re: [PATCH V5] makedumpfile: exclude page structures of non-dumped pages
Date: Tue, 13 Oct 2015 13:57:36 -0400 (EDT) [thread overview]
Message-ID: <919387907.71013933.1444759056336.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <mailman.7843.1444755674.1751.kexec@lists.infradead.org>
----- Original Message -----
>
> Applies to the development branch as of 10/13/2015.
>
> This patch adds a -e option to makedumpfile.
> The -e option excludes kernel pages that contain nothing but kernel page
> structures for pages that are not being included in the dump.
... [ cut ] ...
>
> The only disadvantage is that various options of the crash 'kmem' command (that
> walk lists of page structures) will not work.
> Version 7.0.9 of crash is already patched to issue a warning about such commands
> when the dump is flagged DUMP_DH_EXCLUDED_VMEMMAP.
Just to clarify -- crash-7.0.9 added support for printing warnings if DUMP_DH_COMPRESSED_INCOMPLETE
is set in compressed kdump dumpfile headers, (and DUMP_ELF_INCOMPLETE flags in kdump ELF headers).
But it will not issue any warnings w/respect to missing page strucures.
You're going to file an associated DUMP_DH_EXCLUDED_VMEMMAP patch to the crash-utility
mailing list if/when this makedumpfile patch gets accepted, correct?
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next parent reply other threads:[~2015-10-13 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7843.1444755674.1751.kexec@lists.infradead.org>
2015-10-13 17:57 ` Dave Anderson [this message]
2015-10-13 17:00 [PATCH V5] makedumpfile: exclude page structures of non-dumped pages Cliff Wickman
2015-10-22 7:35 ` 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=919387907.71013933.1444759056336.JavaMail.zimbra@redhat.com \
--to=anderson@redhat.com \
--cc=kexec@lists.infradead.org \
/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