public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Bernd Schubert <bs@q-leap.de>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, jbeulich@novell.com
Subject: Re: frame unwinder patches
Date: Fri, 5 Sep 2008 11:43:16 +0200	[thread overview]
Message-ID: <20080905094316.GS18288@one.firstfloor.org> (raw)
In-Reply-To: <200809051124.17194.bs@q-leap.de>

On Fri, Sep 05, 2008 at 11:24:16AM +0200, Bernd Schubert wrote:
> On Thursday 04 September 2008 21:13:58 Andi Kleen wrote:
> > Bernd Schubert <bs@q-leap.de> writes:
> > > Hello,
> > >
> > > up to 2.6.22 the -mm series had these nice frame unwinder patches,
> > > which gave beautiful stack traces. Unfortunately these frame unwinder
> > > patches seem to have been dropped :(
> > >
> > > Anyone still maintaining updated patches?
> >
> > The SUSE kernel rpm should have an uptodate set
> >
> > (ftp.suse.com/pub/projects/kernel/HEAD )
> >
> 
> Thanks Andi, found it! If someone else needs it, the correct path is 
> ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD. 

Thanks for the correction.

> > I agree that they were much better than the current unwinder,
> > also they didn't require slowing down the kernel with
> > frame pointers.
> 
> What it the reason this patch isn't mainline? It provides better traces, 
> doesn't slow down the kernel (which is important in our HPC envirement), so 
> what is the disadvantage?

The initial version that was merged had a few teething problems because
it ran into tool chain bugs (which were quickly resolved). Unfortunately 
it lead to a few people developing irrational fears of dwarf2 in the 
process and it was reverted, annoying the original contributor.
Right now someone would just need to retry the submission I guess.

-Andi

-- 
ak@linux.intel.com

      reply	other threads:[~2008-09-05  9:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 16:46 frame unwinder patches Bernd Schubert
2008-09-04 17:29 ` Arjan van de Ven
2008-09-05  9:19   ` Bernd Schubert
2008-09-05 13:33     ` Arjan van de Ven
2008-09-05 13:52       ` Bernd Schubert
2008-09-05 14:13         ` Arjan van de Ven
2008-09-05 14:48           ` Bernd Schubert
2008-09-05 14:57             ` Arjan van de Ven
2008-09-05 15:08               ` Andi Kleen
2008-09-04 19:13 ` Andi Kleen
2008-09-05  9:24   ` Bernd Schubert
2008-09-05  9:43     ` Andi Kleen [this message]

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=20080905094316.GS18288@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=bs@q-leap.de \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.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