From: Michal Marek <mmarek@suse.cz>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Rabin Vincent <rabin@rab.in>, Simon Horman <horms@verge.net.au>,
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: Tue, 05 Jan 2010 16:34:23 +0100 [thread overview]
Message-ID: <4B435BFF.10304@suse.cz> (raw)
In-Reply-To: <20100105070658.766317d2@linux.intel.com>
On 5.1.2010 16:06, Arjan van de Ven wrote:
> On Tue, 5 Jan 2010 20:27:58 +0530
> Rabin Vincent <rabin@rab.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,
Was this an Acked-by? :)
> but I wonder if ARM could switch to the <>
> convention for the faulting instruction, just to keep things
> consistent..
I added the patch to the kbuild tree. () won't appear in the x86 Code:
line, so there should be no problem.
Michal
next prev parent reply other threads:[~2010-01-05 15:34 UTC|newest]
Thread overview: 9+ 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-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 [this message]
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 ` [PATCH] " 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=4B435BFF.10304@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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