linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ext-mika.1.westerberg@nokia.com (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] crash utility: add ARM crashdump support
Date: Wed, 30 Jun 2010 13:09:08 +0300	[thread overview]
Message-ID: <cover.1277891104.git.ext-mika.1.westerberg@nokia.com> (raw)

Hello Dave,

First of all, thanks for the great tool! It is the best post-mortem analysis
tool I've ever used.

This series implements ARM support for the crash utility. Current implementation
provides following:

	o Virtual to physical address translation through page tables
	o Stack unwinding support using ARM unwind tables
	o And some more to get minimal support for ARM architecture

There are limitations, however:

	o Only one CPU is supported (I don't have access to ARM SMP hardware)
	o No support for stack unwinding with CONFIG_FRAMEPOINTER
	o Only diskdump format is supported (generated by makedumpfile)

These apply on top of crash 5.0.5 sources. Please let me know, if there is
something that needs to be changed. It would be great if you would consider
taking these in upstream crash.

With these patches, the crash utility can analyze ARM crashdumps pretty well (at
least in my testing environment). What is missing, can be implemented later on
when we have kernel[1] support and users.

After this, all necessary userspace components should be ready for ARM
architecture (kexec-tools, makedumpfile and crash utility).

I've tested this on OMAP3 based platforms with 2.6.32 and latest mainline
kernels (with the kdump patches).

Regards,
MW

[1]
Note that kernel crashdump support is not yet in mainline but I'm hoping that it
will be merged eventually (patches are in RMK's patch tracker already).

Mika Westerberg (4):
  configure: add support for ARM targets
  crash: add support for ARM kernel image
  crash: add ARM diskdump support
  crash: add ARM crashdump support

 Makefile            |   12 +-
 arm.c               | 1188 +++++++++++++++++++++++++++++++++++++++++++++++++++
 configure.c         |   14 +
 defs.h              |  131 ++++++
 diskdump.c          |   50 ++-
 kernel.c            |    2 +-
 lkcd_vmdump_v2_v3.h |    4 +-
 symbols.c           |    8 +-
 unwind_arm.c        |  702 ++++++++++++++++++++++++++++++
 9 files changed, 2102 insertions(+), 9 deletions(-)
 create mode 100644 arm.c
 create mode 100644 unwind_arm.c

             reply	other threads:[~2010-06-30 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 10:09 Mika Westerberg [this message]
2010-06-30 10:09 ` [PATCH 1/4] configure: add support for ARM targets Mika Westerberg
2010-06-30 10:09 ` [PATCH 2/4] crash: add support for ARM kernel image Mika Westerberg
2010-06-30 10:09 ` [PATCH 3/4] crash: add ARM diskdump support Mika Westerberg
2010-06-30 10:09 ` [PATCH 4/4] crash: add ARM crashdump support Mika Westerberg
     [not found] <1093965077.507331277902686384.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2010-06-30 13:10 ` [PATCH 0/4] crash utility: " Dave Anderson
2010-07-01  6:42   ` Mika Westerberg

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.1277891104.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).