From: Andi Kleen <ak@suse.de>
To: Akinobu Mita <mita@miraclelinux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] changes about Call Trace:
Date: Mon, 16 Jan 2006 23:22:36 +0100 [thread overview]
Message-ID: <200601162322.36979.ak@suse.de> (raw)
In-Reply-To: <20060116134109.GA6707@miraclelinux.com>
On Monday 16 January 2006 14:41, Akinobu Mita wrote:
> On Mon, Jan 16, 2006 at 01:22:11PM +0100, Andi Kleen wrote:
> > On Monday 16 January 2006 13:16, Akinobu Mita wrote:
> > > If I'm missing something, please let me know.
> > >
> > > a) On x86-64 we get different Call Trace format than other architectures
> > > when we get oops or press SysRq-t:
> > >
> > > <ffffffffa008ef6c>{:jbd:kjournald+1030}
> > >
> > > There is a architecture independent function print_symbol().
> > > How about using it on x86-64? But it changes to:
> > >
> > > [<ffffffffa008ef6c>] kjournald+0x406/0x578 [jbd]
> >
> > The x86-64 format is more compact.
>
> How about this update?
>
> 1/3: change from "[<...>]" to "<...>".
> 2/3: change the format of offset from hexadecimal to decimal in.
Can you please repost it in a fresh thread? I lost track of what was
the latest patch.
In general if you can make the call trace more compact without
losing information it's ok for me. Better wrapping sounds like
a promising approach.
-Andi
next prev parent reply other threads:[~2006-01-16 22:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 12:16 [PATCH 0/3] changes about Call Trace: Akinobu Mita
2006-01-16 12:17 ` [PATCH 1/3] makes print_symbol() return int Akinobu Mita
2006-01-16 14:16 ` Jesper Juhl
2006-01-16 14:24 ` Akinobu Mita
2006-01-16 15:18 ` Jesper Juhl
2006-01-16 12:18 ` [PATCH 2/3] use usual call trace format on x86-64 Akinobu Mita
2006-01-16 12:22 ` Andi Kleen
2006-01-16 12:32 ` Christoph Hellwig
2006-01-16 12:46 ` Andi Kleen
2006-01-16 12:18 ` [PATCH 3/3] omit symbol size field in print_symbol() Akinobu Mita
2006-01-16 12:22 ` Andi Kleen
2006-01-16 14:37 ` Arjan van de Ven
2006-01-16 15:51 ` Akinobu Mita
2006-01-17 7:06 ` Akinobu Mita
2006-01-16 12:22 ` [PATCH 0/3] changes about Call Trace: Andi Kleen
2006-01-16 13:41 ` Akinobu Mita
2006-01-16 13:41 ` Akinobu Mita
2006-01-16 13:42 ` Akinobu Mita
2006-01-16 22:22 ` Andi Kleen [this message]
2006-01-17 16:53 ` Jan Engelhardt
2006-01-17 7:05 ` Akinobu Mita
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=200601162322.36979.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mita@miraclelinux.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 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.