public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bs@q-leap.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: frame unwinder patches
Date: Fri, 5 Sep 2008 16:48:52 +0200	[thread overview]
Message-ID: <200809051648.52767.bs@q-leap.de> (raw)
In-Reply-To: <20080905071337.3373ab86@infradead.org>

On Friday 05 September 2008 16:13:37 Arjan van de Ven wrote:
> On Fri, 5 Sep 2008 15:52:47 +0200
>
> Bernd Schubert <bs@q-leap.de> wrote:
> > > (and if you really care it's 1 line of code to turn it off)
> >
> > It is not only this, I think the dwarf2 stack unwinder patches
> > provide by far better traces than the in-kernel unwinder. At least
> > ever since I applied these patches to our kernels, I was able to read
> > the stack dumps...
>
> they really wouldn't be different than the ones you get if you remove
> the "?" lines.

Well may be, but then there is still the performace degrading, so I don't want 
to have it enabled on our production kernels. I admit I never measured what 
is the difference between of CONFIG_FRAME_POINTER=y and =n, but the fact the 
help text says there is a difference already makes me want to disable it 
(especially, since we have to provide benchmarks before we can sell a 
system).


Cheers,
Bernd

-- 
Bernd Schubert
Q-Leap Networks GmbH

  reply	other threads:[~2008-09-05 14:49 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 [this message]
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

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=200809051648.52767.bs@q-leap.de \
    --to=bs@q-leap.de \
    --cc=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --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