Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Thierry <jthierry@redhat.com>
To: kexec@lists.infradead.org
Cc: bhsharma@redhat.com, Julien Thierry <jthierry@redhat.com>,
	k-hagio-ab@nec.com, lijiang@redhat.com
Subject: [MAKDUMPFILE PATCH 0/2] Get stats without writing dumpfile
Date: Tue, 24 Nov 2020 10:45:23 +0000	[thread overview]
Message-ID: <20201124104525.1070885-1-jthierry@redhat.com> (raw)

Hi,

This series is a follow up to the --vmcore-size proposal[1].

The goal is to be able to obtain informations about the dumpfile without
actually generating it. Instead of the --vmcore-size approach, we add
two different options, one allowing to run makedumpfil without writting
the dumpfile, and another to explicitly enable stat displaying.

[1] https://www.spinics.net/lists/kexec/msg26058.html

Cheers,

Julien

-->

Julien Thierry (2):
  Add option to prevent writing the dumpfile
  Add shorthand option to show report stats

 makedumpfile.8 | 10 ++++++++++
 makedumpfile.c | 45 ++++++++++++++++++++++++++++++++++++++++++---
 makedumpfile.h |  3 +++
 print_info.c   |  6 ++++++
 4 files changed, 61 insertions(+), 3 deletions(-)

--
2.25.4


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

             reply	other threads:[~2020-11-24 10:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 10:45 Julien Thierry [this message]
2020-11-24 10:45 ` [MAKEDUMPFILE PATCH 1/2] Add option to prevent writing the dumpfile Julien Thierry
2021-01-18  6:43   ` HAGIO KAZUHITO(萩尾　一仁)
2021-01-28  9:00     ` HAGIO KAZUHITO(萩尾　一仁)
2021-02-04  8:21       ` HAGIO KAZUHITO(萩尾　一仁)
2020-11-24 10:45 ` [MAKEDUMPFILE PATCH 2/2] Add shorthand option to show report stats Julien Thierry
2021-01-18  7:19   ` HAGIO KAZUHITO(萩尾　一仁)

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=20201124104525.1070885-1-jthierry@redhat.com \
    --to=jthierry@redhat.com \
    --cc=bhsharma@redhat.com \
    --cc=k-hagio-ab@nec.com \
    --cc=kexec@lists.infradead.org \
    --cc=lijiang@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