From: Hui Zhu <teawater@gmail.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Hui Zhu <hui.zhu@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Sam Ravnborg <sam@ravnborg.org>,
ozan@pardus.org.tr, Matthew Wilcox <willy@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] markup_oops.pl: add options to improve cross-sompilation environments
Date: Tue, 26 Jan 2010 17:21:08 +0800 [thread overview]
Message-ID: <daef60381001260121q675ecb30r2099c085c40d7964@mail.gmail.com> (raw)
In-Reply-To: <2375c9f91001260115q3fe86964l7ea1c8f9c69cb5e9@mail.gmail.com>
Hi Américo,
On Tue, Jan 26, 2010 at 17:15, Américo Wang <xiyou.wangcong@gmail.com> wrote:
> On Tue, Jan 26, 2010 at 5:13 PM, Hui Zhu <hui.zhu@windriver.com> wrote:
>>
>> What do you think about it?
>>
>> And I changed the other part according to your mail.
>
>
> It looks fine for me now, I assume you already tested it.
It was tested. :)
>
>
>>
>> Best regards,
>> Hui
>>
>> The markup_oops.pl have 3 troubles to support cross-compiler environment:
>> 1. It use objdump directly.
>> 2. It use modinfo to get the message of module.
>> 3. It use hex function that cannot support 64-bit number in 32-bit arch.
>>
>> This patch add 3 options to markup_oops.pl:
>> 1. -c CROSS_COMPILE Specify the prefix used for toolchain.
>> 2. -m MODULE_DIRNAME Specify the module directory name.
>> 3. Change hex function to Math::BigInt->from_hex.
>>
>> After this patch, parse the x8664 oops in x86, we can:
>> cat amd64m | perl ~/kernel/tmp/m.pl -c /home/teawater/kernel/bin/x8664- -m
>> ./e.ko vmlinux
>>
>> Thanks,
>> Hui
>>
>> Signed-off-by: Hui Zhu <teawater@gmail.com>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Arjan van de Ven <arjan@linux.intel.com>
>> Cc: Sam Ravnborg <sam@ravnborg.org>
>> Cc: ozan@pardus.org.tr
>> Cc: Matthew Wilcox <willy@linux.intel.com>
>>
>
> Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
>
Thanks,
Hui
next prev parent reply other threads:[~2010-01-26 9:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 3:11 Hui Zhu
2010-01-26 3:05 ` Américo Wang
2010-01-26 7:38 ` Hui Zhu
2010-01-26 7:53 ` Américo Wang
2010-01-26 9:13 ` Hui Zhu
2010-01-26 9:15 ` Américo Wang
2010-01-26 9:21 ` Hui Zhu [this message]
2010-01-29 20:27 ` Michal Marek
2010-02-01 5:41 ` Hui Zhu
2010-02-05 21:38 ` Michal Marek
2010-02-08 2:55 ` Hui Zhu
2010-02-17 13:08 ` Michal Marek
2010-02-20 2:16 ` Hui Zhu
-- strict thread matches above, loose matches on Subject: below --
2010-01-25 14:36 Hui Zhu
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=daef60381001260121q675ecb30r2099c085c40d7964@mail.gmail.com \
--to=teawater@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=hui.zhu@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
--cc=sam@ravnborg.org \
--cc=willy@linux.intel.com \
--cc=xiyou.wangcong@gmail.com \
/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®