From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] scripts: add ARM support to decodecode
Date: Wed, 6 Jan 2010 09:14:37 +1100 [thread overview]
Message-ID: <20100105221437.GF8630@verge.net.au> (raw)
In-Reply-To: <20100105145758.GA2690@debian>
On Tue, Jan 05, 2010 at 08:27:58PM +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.
>
> - ARM mnemonics may include characters such as [] which need to be
> escaped before being passed to sed for the "<- trapping instruction"
> substitution.
>
> Signed-off-by: Rabin Vincent <rabin@rab.in>
> ---
> v2: condensed some sed and grep expressions
Condensation portion Acked-by: Simon Horman <horms@verge.net.au>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: Rabin Vincent <rabin@rab.in>
Cc: mmarek@suse.cz, arjan@linux.intel.com, wangcong@zeuux.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] scripts: add ARM support to decodecode
Date: Wed, 6 Jan 2010 09:14:37 +1100 [thread overview]
Message-ID: <20100105221437.GF8630@verge.net.au> (raw)
In-Reply-To: <20100105145758.GA2690@debian>
On Tue, Jan 05, 2010 at 08:27:58PM +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.
>
> - ARM mnemonics may include characters such as [] which need to be
> escaped before being passed to sed for the "<- trapping instruction"
> substitution.
>
> Signed-off-by: Rabin Vincent <rabin@rab.in>
> ---
> v2: condensed some sed and grep expressions
Condensation portion Acked-by: Simon Horman <horms@verge.net.au>
next prev parent reply other threads:[~2010-01-05 22:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 14:53 [PATCH] scripts: add ARM support to decodecode Rabin Vincent
2009-12-30 14:53 ` Rabin Vincent
2009-12-31 5:18 ` Simon Horman
2009-12-31 5:18 ` Simon Horman
2010-01-05 14:57 ` [PATCH v2] " Rabin Vincent
2010-01-05 14:57 ` Rabin Vincent
2010-01-05 15:06 ` Arjan van de Ven
2010-01-05 15:06 ` Arjan van de Ven
2010-01-05 15:34 ` Michal Marek
2010-01-05 15:34 ` Michal Marek
2010-01-05 17:31 ` Russell King - ARM Linux
2010-01-05 17:31 ` Russell King - ARM Linux
2010-01-05 19:27 ` Daniel Jacobowitz
2010-01-05 19:27 ` Daniel Jacobowitz
2010-01-05 22:14 ` Simon Horman [this message]
2010-01-05 22:14 ` Simon Horman
2010-01-01 20:32 ` [PATCH] " Russell King - ARM Linux
2010-01-01 20:32 ` Russell King - ARM Linux
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=20100105221437.GF8630@verge.net.au \
--to=horms@verge.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.