From: Ingo Molnar <mingo@elte.hu>
To: Esben Nielsen <simlo@phys.au.dk>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.16-rc6-rt1
Date: Tue, 14 Mar 2006 09:12:12 +0100 [thread overview]
Message-ID: <20060314081212.GD13662@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0603140037000.1291-100000@lifa01.phys.au.dk>
* Esben Nielsen <simlo@phys.au.dk> wrote:
> Well, I got my TestRTMutex compiled and it was successfull: It found
> bugs.
great!
I forgot to announce Thomas' great new rt-tester framework, which allows
easy testing of the kernel's PI implementation, via userspace scripts.
You can enable it via CONFIG_RT_MUTEX_TESTER, and the userspace scripts
are at:
http://people.redhat.com/mingo/realtime-preempt/testing/rt-tester.tar.bz2
Thomas' testing method has the advantage that it utilizes the kernel's
PI mechanism directly, hence it is easy to keep it uptodate without
having to port the kernel's PI code to userspace. We should add the
testcases for the bugs you just found.
> 1) Boosting nested locks simply doesn't work:
> This is easily fixed by
thanks, applied. [NOTE: had to apply it by hand because the patch was
whitespace damaged, it had all tabs converted to spaces.]
> 2) There is a spinlock deadlock when doing the following test on SMP:
>
> threads: 1 2
> lock 1 +
> + lock 2
> test: lockcount 1 lockcount 1
>
> lock 2 lock 1 <- spin deadlocks here
> - -
> test: lockcount 1 lockcount 1
>
> This happens because both tasks tries to lock both tasks's pi_lock but
> in opposit order. I don't have fix for that one yet.
well, this is a circular dependency deadlock - which is illegal in the
kernel, and which we detect for futex locks too - so it shouldnt happen.
Or did you see it happen for real?
Ingo
next prev parent reply other threads:[~2006-03-14 8:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 22:02 2.6.16-rc6-rt1 Ingo Molnar
2006-03-12 23:17 ` 2.6.16-rc6-rt1 Michal Piotrowski
2006-03-12 23:36 ` 2.6.16-rc6-rt1 Michal Piotrowski
2006-03-13 6:43 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-13 9:25 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-13 13:49 ` 2.6.16-rc6-rt1 Michal Piotrowski
2006-03-13 6:56 ` [PATCH] 2.6.16-rc6-rt1: Fix redefinition and unknown symbol Jan Altenberg
2006-03-13 9:11 ` Ingo Molnar
2006-03-13 13:21 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-13 14:29 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-13 16:06 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 0:22 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 8:12 ` Ingo Molnar [this message]
2006-03-14 8:33 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-14 10:02 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 10:18 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 22:02 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 22:11 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 22:22 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-15 11:21 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 22:28 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 10:58 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-14 20:40 ` 2.6.16-rc6-rt1 Esben Nielsen
2006-03-14 22:00 ` 2.6.16-rc6-rt1 Thomas Gleixner
2006-03-14 1:54 ` 2.6.16-rc6-rt1 Steven Rostedt
2006-03-14 7:51 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-14 2:22 ` 2.6.16-rc6-rt1 Steven Rostedt
2006-03-14 8:00 ` 2.6.16-rc6-rt1 Ingo Molnar
2006-03-15 16:25 ` 2.6.16-rc6-rt1 John Richard Moser
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=20060314081212.GD13662@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=simlo@phys.au.dk \
--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