mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov@yahoo.com>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	rdunlap@xenotime.net, torvalds@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-64: improve the format of stack dumps
Date: Tue, 7 Feb 2006 11:17:17 -0800 (PST)	[thread overview]
Message-ID: <20060207191717.25539.qmail@web31804.mail.mud.yahoo.com> (raw)
In-Reply-To: <200602071020.47999.ak@suse.de>

--- Andi Kleen <ak@suse.de> wrote:
> On Tuesday 07 February 2006 06:13, Luben Tuikov wrote:
> > Improve the format of stack dumps for x86-64.
> > * Single column of stack entries. (similar to other arches)
> 
> I don't like that part as I wrote earlier.It's a waste of precious
> screen space, no matter how often you retransmit the patch.  The old
> format had a chance to even fit on a 80x25 screen, with your new one
> it is extremly unlikely.
> 
> Overall you're making less information available in a common case
> for cosmetics.

And as I wrote earlier, this patch doesn't only improve output,
it also _reuses_ code, i.e. __print_symbol() which your code recreates
in printk_address().  Now printk_address() reuses the common __print_symbol().

One very important thing this patch also does is that it prints the offsets
in hexadecimal, as opposed to decimal.  I.e. from

0xNNNNNNNN+DDD to 0xNNNNNNNNN+0xTTT/0xWWW

As to "less space", this patch prints _identical_ information as the code
before it, as I'm sure you can see by reading the patch itself.

Thanks,
     Luben



  reply	other threads:[~2006-02-07 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200602032213.55058.ak@suse.de>
2006-02-07  5:13 ` Luben Tuikov
2006-02-07  9:20   ` Andi Kleen
2006-02-07 19:17     ` Luben Tuikov [this message]
2006-02-07 19:39       ` Andi Kleen

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=20060207191717.25539.qmail@web31804.mail.mud.yahoo.com \
    --to=ltuikov@yahoo.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®