From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: kumagai-atsushi@mxc.nes.nec.co.jp
Cc: kexec@lists.infradead.org, vgoyal@redhat.com
Subject: [PATCH v2 0/2] makedumpfile: write out a whole part of the 1st bitmap before entering cyclic process
Date: Tue, 05 Nov 2013 00:22:37 +0900 [thread overview]
Message-ID: <20131104152202.2556.83382.stgit@localhost6.localdomain6> (raw)
This patch set changes the implementation so that a whole part of the
1st bitmap is written out before entering cyclic process. By this:
- we no longer need to keep buffer for the 1st bitmap during cyclic
process, and
- it's possible for incomplete crash dump, for example, generated in
case of ENOSPC, to avoid the case that we don't know where memory is
present.
Note that this patch only deal with a conversion from ELF to
kdump-compressed format only, not from ELF to ELF.
ChangeLog
v1 => v2)
- Fix a bug of assigning wrong cyclic buffer size from free memory
size.
---
HATAYAMA Daisuke (2):
Use memset() to improve the 1st bitmap initialization performance
Write out a whole part of the 1st bitmap before entering cyclic process
makedumpfile.c | 268 ++++++++++++++++++++++++++++++++++++++++++++++++++------
1 file changed, 241 insertions(+), 27 deletions(-)
--
Thanks.
HATAYAMA, Daisuke
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2013-11-04 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 15:22 HATAYAMA Daisuke [this message]
2013-11-04 15:22 ` [PATCH v2 1/2] Use memset() to improve the 1st bitmap initialization performance HATAYAMA Daisuke
2013-11-04 15:22 ` [PATCH v2 2/2] Write out a whole part of the 1st bitmap before entering cyclic process HATAYAMA Daisuke
2013-11-07 2:52 ` [PATCH v2 0/2] makedumpfile: write " 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=20131104152202.2556.83382.stgit@localhost6.localdomain6 \
--to=d.hatayama@jp.fujitsu.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