From: Peter Zijlstra <peterz@infradead.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: Ingo Molnar <mingo@elte.hu>, Remy Bohmer <linux@bohmer.net>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
RT <linux-rt-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dave Chinner <dgc@sgi.com>
Subject: Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
Date: Sun, 18 Nov 2007 13:33:50 +0100 [thread overview]
Message-ID: <1195389230.6747.5.camel@twins> (raw)
In-Reply-To: <1195323177.25393.56.camel@imap.mvista.com>
On Sat, 2007-11-17 at 10:12 -0800, Daniel Walker wrote:
> What specifically is wrong with dev->sem ?
Nothing really, other than that they use semaphores to avoid lockdep :-/
I think I know how to annotate this, after Alan Stern explained all the
use cases, but I haven't come around to implementing it. Hope to do that
soonish.
Another real semaphore user is XFS, they really use the down/up
asymmetry that semaphores allow, last time I spoke with Dave Chinner he
didn't know a way around this.
next prev parent reply other threads:[~2007-11-18 12:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 15:51 Remy Bohmer
2007-11-16 20:20 ` Steven Rostedt
2007-11-16 23:02 ` Remy Bohmer
2007-11-16 23:37 ` Steven Rostedt
2007-11-17 11:44 ` Remy Bohmer
2007-11-17 14:08 ` Steven Rostedt
2007-11-17 15:06 ` Steven Rostedt
2007-11-17 15:36 ` Remy Bohmer
2007-11-19 12:55 ` Remy Bohmer
2007-11-19 13:54 ` Steven Rostedt
2007-11-17 16:22 ` Daniel Walker
2007-11-17 17:09 ` Remy Bohmer
2007-11-17 17:29 ` Daniel Walker
2007-11-17 17:46 ` Ingo Molnar
2007-11-17 17:55 ` Daniel Walker
2007-11-17 18:04 ` Ingo Molnar
2007-11-17 18:12 ` Daniel Walker
2007-11-18 12:33 ` Peter Zijlstra [this message]
2007-11-18 22:26 ` David Chinner
2007-11-17 22:49 ` Remy Bohmer
2007-11-19 7:25 ` Jon Masters
2007-11-19 15:31 ` Daniel Walker
2007-11-19 15:51 ` Remy Bohmer
2007-11-19 16:11 ` Daniel Walker
2007-11-20 16:43 ` Daniel Walker
2007-11-20 20:37 ` Ingo Molnar
2007-11-20 20:54 ` Daniel Walker
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=1195389230.6747.5.camel@twins \
--to=peterz@infradead.org \
--cc=dgc@sgi.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux@bohmer.net \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®