From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Rabin Vincent <rabin@rab.in>
Cc: mmarek@suse.cz, linux-kernel@vger.kernel.org, wangcong@zeuux.org,
akpm@linux-foundation.org, arjan@linux.intel.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] scripts: add ARM support to decodecode
Date: Fri, 1 Jan 2010 20:32:42 +0000 [thread overview]
Message-ID: <20100101203242.GF16220@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1262184839-24497-1-git-send-email-rabin@rab.in>
On Wed, Dec 30, 2009 at 08:23:59PM +0530, Rabin Vincent wrote:
> This patch adds support for decoding ARM oopses to scripts/decodecode.
> The following things are handled:
>
> - ARCH and CROSS_COMPILE environment variables are respected.
>
> - The Code: in x86 oopses is in bytes, while it is in either words (4
> bytes) or halfwords for ARM.
>
> - Some versions of ARM objdump refuse to disassemble instructions
> generated by literal constants (".word 0x..."). The workaround is to
> strip the object file first.
>
> - The faulting instruction is marked (liked so) in ARM, but <like so>
> in x86.
I've been debating about changing that so we use () instead of <> to
make things more consistent, but I've been holding off in case there's
still any ksymoops users out there. Opinions?
prev parent reply other threads:[~2010-01-01 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 14:53 Rabin Vincent
2009-12-31 5:18 ` Simon Horman
2010-01-05 14:57 ` [PATCH v2] " Rabin Vincent
2010-01-05 15:06 ` Arjan van de Ven
2010-01-05 15:34 ` Michal Marek
2010-01-05 17:31 ` Russell King - ARM Linux
2010-01-05 19:27 ` Daniel Jacobowitz
2010-01-05 22:14 ` Simon Horman
2010-01-01 20:32 ` Russell King - ARM Linux [this message]
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=20100101203242.GF16220@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rabin@rab.in \
--cc=wangcong@zeuux.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
all inboxes | Powered by JetHome®