From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Dave Jones <davej@redhat.com>
Cc: "Joao Correia" <joaomiguelcorreia@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Américo Wang" <xiyou.wangcong@gmail.com>,
"Frederic Weisbecker" <fweisbec@gmail.com>,
"Arjan van de Ven" <arjan@linux.intel.com>,
"Catalin Marinas" <catalin.marinas@arm.com>
Subject: Re: [PATCH 1/3] Increase lockdep limits: MAX_STACK_TRACE_ENTRIES
Date: Thu, 09 Jul 2009 10:02:36 +0200 [thread overview]
Message-ID: <1247126556.9777.323.camel@twins> (raw)
In-Reply-To: <20090709043931.GA11391@redhat.com>
On Thu, 2009-07-09 at 00:39 -0400, Dave Jones wrote:
> On Wed, Jul 08, 2009 at 08:36:04PM +0200, Peter Zijlstra wrote:
> > Looking at a lockdep dump hch gave me I can see that that is certainly
> > possible, I see tons of very deep callchains.
> >
> > /me wonders if we're getting significantly deeper..
>
> Looking at /proc/lockdep, I'm curious..
> Take a look at http://davej.fedorapeople.org/lockdep
> scroll down to c12c0924
>
> What's up with all those old_style_spin_init's ?
What kernel are you running? Does your lib/dma_debug.c:dma_debug_init()
have spin_lock_init() in that HASH_SIZE loop?
If so, then there's someone else doing silly, if not, you seriously need
to upgrade your kernel because you're running something ancient,
like .30 :-)
next prev parent reply other threads:[~2009-07-09 8:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 15:25 [PATCH 1/3] Increase lockdep limits: MAX_STACK_TRACE_ENTRIES Joao Correia
2009-07-07 15:33 ` Peter Zijlstra
[not found] ` <a5d9929e0907070838q7ed3306du3bb7880e47d7207b@mail.gmail.com>
2009-07-07 15:38 ` Fwd: " Joao Correia
[not found] ` <1246981444.9777.11.camel@twins>
2009-07-07 15:50 ` Joao Correia
2009-07-07 15:55 ` Peter Zijlstra
2009-07-07 15:59 ` Joao Correia
2009-07-08 17:22 ` Dave Jones
2009-07-08 18:36 ` Peter Zijlstra
2009-07-08 18:44 ` Dave Jones
2009-07-08 19:48 ` Joao Correia
2009-07-08 19:56 ` Peter Zijlstra
2009-07-09 4:39 ` Dave Jones
2009-07-09 8:02 ` Peter Zijlstra [this message]
2009-07-09 16:10 ` Dave Jones
2009-07-09 17:07 ` Peter Zijlstra
2009-07-10 15:50 ` Joao Correia
2009-07-09 9:06 ` Catalin Marinas
2009-07-09 9:09 ` Peter Zijlstra
2009-07-20 13:31 ` [PATCH] lockdep: fixup stacktrace wastage Peter Zijlstra
2009-08-02 13:14 ` [tip:core/locking] lockdep: Fix backtraces tip-bot for Peter Zijlstra
2009-08-02 13:51 ` tip-bot for Peter Zijlstra
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=1247126556.9777.323.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=arjan@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=davej@redhat.com \
--cc=fweisbec@gmail.com \
--cc=joaomiguelcorreia@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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.