public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andi Kleen <ak@suse.de>, Eric Rannaud <eric.rannaud@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	nagar@watson.ibm.com, Chandra Seetharaman <sekharan@us.ibm.com>,
	Jan Beulich <jbeulich@novell.com>
Subject: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
Date: Sat, 30 Sep 2006 22:49:00 +0200	[thread overview]
Message-ID: <20060930204900.GA576@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0609301344231.3952@g5.osdl.org>


* Linus Torvalds <torvalds@osdl.org> wrote:

> I mean, really: Andi, point me to anything that was a real problem 
> when we had no unwinder at all?

personally, i like perfect stacktraces, alot. x86_64 was a huge pain for 
me without the unwinder. I got so used to perfect backtraces on i686 
(when using %ebp frames) during the years, and i had to look at _many_ 
backtraces with lockdep. On x86_64 it was just constant brain-drain to 
think away bogus stack entries. Yes, i can do it no problem when i have 
to look at only a few stacktraces per day, but if it's hundreds per day 
it's _alot_ of brainpower wasted.

(i'd have been happy with an %rbp based unwinder for x86_64, in fact i 
implemented it for lockdep and used it for some time on x86_64, but Andi 
wanted a dwarf-based, lower-overhead one. Andi also nicely integrated it 
into stacktrace.c.)

	Ingo

  reply	other threads:[~2006-09-30 20:57 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-30 19:20 BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) Eric Rannaud
2006-09-30 19:49 ` Peter Zijlstra
2006-09-30 20:23   ` Linus Torvalds
2006-09-30 20:57   ` Eric Rannaud
2006-09-30 19:54 ` Linus Torvalds
2006-09-30 20:21   ` Al Viro
2006-09-30 20:28     ` Linus Torvalds
2006-09-30 20:30   ` Andi Kleen
2006-09-30 20:47     ` Linus Torvalds
2006-09-30 20:49       ` Ingo Molnar [this message]
2006-09-30 21:11         ` Linus Torvalds
2006-09-30 21:25           ` Ingo Molnar
2006-09-30 21:57           ` Andi Kleen
2006-09-30 22:09             ` BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) II Andi Kleen
2006-09-30 22:19               ` Eric Rannaud
2006-09-30 22:24                 ` Andi Kleen
2006-09-30 22:54             ` BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) Linus Torvalds
2006-10-04  9:21           ` Jan Beulich
2006-10-04 15:12             ` Linus Torvalds
2006-09-30 21:43     ` Eric Rannaud
2006-09-30 22:03       ` Andi Kleen
2006-09-30 21:56     ` Linus Torvalds
2006-09-30 22:02       ` Andi Kleen
2006-09-30 22:10         ` Ingo Molnar
2006-09-30 22:23           ` Andi Kleen
2006-09-30 22:55         ` Linus Torvalds
2006-09-30 22:59           ` Linus Torvalds
2006-09-30 23:56           ` Andi Kleen
2006-10-01  0:25             ` Linus Torvalds
2006-10-01  0:51               ` Linus Torvalds
2006-10-01  9:27                 ` Andi Kleen
2006-10-04  9:25     ` Jan Beulich
2006-10-04 10:52       ` Andi Kleen
2006-10-04 11:58         ` Jan Beulich
2006-10-04 12:03           ` Andi Kleen
2006-10-04 12:10             ` Jan Beulich
2006-09-30 20:43   ` Linus Torvalds
2006-10-04  9:15   ` Jan Beulich
2006-09-30 20:13 ` Andrew Morton
2006-09-30 20:52   ` Eric Rannaud
2006-09-30 21:04     ` Andrew Morton
2006-09-30 22:00       ` Eric Rannaud
2006-09-30 22:05         ` Ingo Molnar
2006-10-01  0:59           ` Eric Rannaud

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=20060930204900.GA576@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=eric.rannaud@gmail.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nagar@watson.ibm.com \
    --cc=sekharan@us.ibm.com \
    --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