[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100105070658.766317d2@linux.intel.com>
Date: Tue, 5 Jan 2010 07:06:58 -0800
From: Arjan van de Ven <arjan@...ux.intel.com>
To: Rabin Vincent <rabin@....in>
Cc: Simon Horman <horms@...ge.net.au>, mmarek@...e.cz,
wangcong@...ux.org, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] scripts: add ARM support to decodecode
On Tue, 5 Jan 2010 20:27:58 +0530
Rabin Vincent <rabin@....in> 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.
I'm fine with this, but I wonder if ARM could switch to the <>
convention for the faulting instruction, just to keep things
consistent..
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists