kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "HAGIO KAZUHITO(萩尾 一仁)" <k-hagio-ab@nec.com>
To: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: [ANNOUNCE] makedumpfile 1.7.5
Date: Fri, 12 Apr 2024 05:43:48 +0000	[thread overview]
Message-ID: <2caf15f0-dff1-4097-b980-77d8aae4d213@nec.com> (raw)

Hi,

I'm pleased to announce the release of makedumpfile 1.7.5.
Thank you everyone for your help to maintain the tool.

Download:
The latest makedumpfile can be downloaded from the following URL.
    https://github.com/makedumpfile/makedumpfile/releases

New features:
- Support for kernels up to v6.8 (x86_64)
- Support for printk caller_id by --dump-dmesg option

Commits since 1.7.4:
c266469 [v1.7.5] Update version (Kazuhito Hagio)
94241fd [PATCH] ppc64: get vmalloc start address from vmcoreinfo (Aditya Gupta)
71ac00c [PATCH] ppc64: read cur_mmu_type from vmcoreinfo (Aditya Gupta)
48bb1e0 [PATCH] add PRINTK_CALLER id support to --dump-dmesg option (Edward Chron)
6f8325d [PATCH v2 2/2] s390x: uncouple virtual and physical address spaces (Alexander Gordeev)
7bb90b7 [PATCH 1/2] s390x: fix virtual vs physical address confusion (Alexander Gordeev)

Description of makedumpfile:
The makedumpfile is a tool for creating a dumpfile from /proc/vmcore
with filtering out unnecessary pages for analysis and compressing the
remaining pages, in order to shorten the size of the dumpfile and the
time of creating it.
https://github.com/makedumpfile/makedumpfile

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

                 reply	other threads:[~2024-04-12  5:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2caf15f0-dff1-4097-b980-77d8aae4d213@nec.com \
    --to=k-hagio-ab@nec.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).