From: Steven Rostedt <rostedt@goodmis.org>
To: Esben Nielsen <simlo@phys.au.dk>
Cc: Ingo Molnar <mingo@elte.hu>,
david singleton <dsingleton@mvista.com>,
linux-kernel@vger.kernel.org
Subject: Re: RT Mutex patch and tester [PREEMPT_RT]
Date: Wed, 11 Jan 2006 12:51:52 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.58.0601111240020.31180@gandalf.stny.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0601111816360.16743-201000@lifa03.phys.au.dk>
On Wed, 11 Jan 2006, Esben Nielsen wrote:
> I have done 2 things which might be of interrest:
>
> I) A rt_mutex unittest suite. It might also be usefull against the generic
> mutexes.
>
> II) I changed the priority inheritance mechanism in rt.c,
> optaining the following goals:
>
Interesting. I'll take a look more at this after I finish dealing with
some deadlocks that I found in posix-timers.
[snip]
>
> What am I missing:
> Testing on SMP. I have no SMP machine. The unittest can mimic the SMP
> somewhat
> but no unittest can catch _all_ errors.
I have a SMP machine that just freed up. It would be interesting to see
how this works on a 8x machine. I'll test it first on my 2x, and when
Ingo gets some time he can test it on his big boxes.
>
> Testing with futexes.
>
> ALL_PI_TASKS are always switched on now. This is for making the code
> simpler.
>
> My machine fails to run with CONFIG_DEBUG_DEADLOCKS and CONFIG_DEBUG_PREEMPT
> on at the same time. I need a serial cabel and on consol over serial to
> debug it. My screen is too small to see enough there.
>
> Figure out more tests to run in my unittester.
>
> So why aren't I doing those things before sending the patch? 1) Well my
> girlfriend comes back tomorrow with our child. I know I will have no time to code anything substential
> then. 2) I want to make sure Ingo sees this approach before he starts
> merging preempt_rt and rt_mutex with his now mainstream mutex.
If I get time, I might be able to finish this up, if the changes look
decent, and don't cause too much overhead.
-- Steve
next prev parent reply other threads:[~2006-01-11 17:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 17:25 RT Mutex patch and tester [PREEMPT_RT] Esben Nielsen
2006-01-11 17:51 ` Steven Rostedt [this message]
2006-01-11 21:45 ` Esben Nielsen
2006-01-12 11:33 ` Bill Huey
2006-01-12 12:54 ` Esben Nielsen
2006-01-13 8:07 ` Bill Huey
2006-01-13 8:47 ` Esben Nielsen
2006-01-13 10:19 ` Bill Huey
2006-01-15 4:24 ` Bill Huey
2006-01-16 8:35 ` Esben Nielsen
2006-01-16 10:22 ` Bill Huey
2006-01-16 10:53 ` Bill Huey
2006-01-16 11:30 ` Esben Nielsen
[not found] ` <Pine.LNX.4.44L0.0601181120100.1993-201000@lifa02.phys.au.dk>
2006-01-18 10:38 ` Ingo Molnar
2006-01-18 12:49 ` Steven Rostedt
2006-01-18 14:18 ` Esben Nielsen
[not found] ` <Pine.LNX.4.44L0.0601230047290.31387-201000@lifa01.phys.au.dk>
2006-01-23 0:38 ` david singleton
2006-01-23 2:04 ` Bill Huey
2006-01-23 9:33 ` Esben Nielsen
2006-01-23 14:23 ` Steven Rostedt
2006-01-23 15:14 ` Esben Nielsen
2006-01-27 15:18 ` Esben Nielsen
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=Pine.LNX.4.58.0601111240020.31180@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=dsingleton@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=simlo@phys.au.dk \
/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;
as well as URLs for NNTP newsgroup(s).