From: ext-mika.1.westerberg@nokia.com (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] makedumpfile: add support for ARM crashdumps
Date: Tue, 22 Jun 2010 09:59:09 +0300 [thread overview]
Message-ID: <cover.1277188127.git.ext-mika.1.westerberg@nokia.com> (raw)
Hello,
This series adds support for ARM kernel crashdumps to makedumpfile. Although,
kernel support is not yet in mainline, I think that it doesn't hurt to have
necessary userspace tools available when that happens.
If someone wants to try, kernel patches can be found:
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-May/014230.html
and kexec-tools already contain ARM crashdump support.
Regards,
MW
Mika Westerberg (3):
use ARCH_PFN_OFFSET for pfn_to_paddr/paddr_to_pfn translations
page_to_pfn(): use ULONGLONG_MAX to for invalid pfn
add ARM crashdump support
Makefile | 4 +-
arm.c | 200 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
makedumpfile.c | 7 +-
makedumpfile.h | 43 ++++++++++++-
4 files changed, 247 insertions(+), 7 deletions(-)
create mode 100644 arm.c
next reply other threads:[~2010-06-22 6:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 6:59 Mika Westerberg [this message]
2010-06-22 6:59 ` [PATCH 1/3] use ARCH_PFN_OFFSET for pfn_to_paddr/paddr_to_pfn translations Mika Westerberg
2010-06-22 6:59 ` [PATCH 2/3] page_to_pfn(): use ULONGLONG_MAX to for invalid pfn Mika Westerberg
2010-06-22 6:59 ` [PATCH 3/3] add ARM crashdump support Mika Westerberg
2010-06-24 7:33 ` Masayuki Igawa
2010-06-24 8:19 ` Mika Westerberg
2010-06-24 23:31 ` Masayuki Igawa
2010-06-25 7:05 ` Masayuki Igawa
2010-06-28 5:14 ` Mika Westerberg
2010-06-28 5:25 ` Masayuki Igawa
2010-06-22 7:40 ` [PATCH 0/3] makedumpfile: add support for ARM crashdumps Masayuki Igawa
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=cover.1277188127.git.ext-mika.1.westerberg@nokia.com \
--to=ext-mika.1.westerberg@nokia.com \
--cc=linux-arm-kernel@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 NNTP newsgroup(s).