From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: hrtimers and lockdep (was: Re: 2.6.24-rc6: possible recursive locking detected)
Date: Wed, 30 Jan 2008 11:34:32 +0100 [thread overview]
Message-ID: <1201689272.28547.204.camel@lappy> (raw)
In-Reply-To: <20080114212741.GA2263@tv-sign.ru>
( trimmed CC list )
Sorry for the delay, this message seems to have gotten lost in my
inbox :-/
On Tue, 2008-01-15 at 00:27 +0300, Oleg Nesterov wrote:
> On 01/13, Peter Zijlstra wrote:
> Offtopic question. Why do we have so many lockdep stuff in timer.c and hrtimer.c ?
> We never lock 2 bases at the same time, except in migrate_timers(). We can kill
> double_spin_lock() and base_lock_keys[] and just use spin_lock_nested in
> migrate_timers(), no?
Lets ask Thomas.. :-)
next prev parent reply other threads:[~2008-01-30 10:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 22:58 2.6.24-rc6: possible recursive locking detected Christian Kujau
2008-01-03 23:06 ` Rafael J. Wysocki
2008-01-04 8:30 ` Ingo Molnar
2008-01-05 7:12 ` Herbert Xu
2008-01-05 16:53 ` Peter Zijlstra
2008-01-05 17:01 ` Peter Zijlstra
2008-01-05 21:35 ` Davide Libenzi
2008-01-06 0:20 ` Christian Kujau
2008-01-07 21:35 ` Davide Libenzi
2008-01-06 21:44 ` Cyrill Gorcunov
2008-01-06 21:53 ` Cyrill Gorcunov
2008-01-07 17:22 ` Oleg Nesterov
2008-01-07 17:49 ` Oleg Nesterov
2008-01-13 16:32 ` Peter Zijlstra
2008-01-14 21:27 ` Oleg Nesterov
2008-01-30 10:34 ` Peter Zijlstra [this message]
2008-01-30 17:36 ` hrtimers and lockdep (was: Re: 2.6.24-rc6: possible recursive locking detected) Thomas Gleixner
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=1201689272.28547.204.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=tglx@linutronix.de \
/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.