All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Esben Nielsen <simlo@phys.au.dk>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: PI patch against 2.6.16-rt9
Date: Mon, 27 Mar 2006 01:47:22 +0200	[thread overview]
Message-ID: <20060326234722.GA25331@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0603270025020.2708-100000@lifa01.phys.au.dk>


* Esben Nielsen <simlo@phys.au.dk> wrote:

> Hi,
>  I got the patch I mentioned earlier to run. It passes my userspace
> testscripts as well as all the scripts for Thomas's rtmutex-tester on a UP
> machine.
> 
> The idea is to avoid the deadlocks by releasing all locks before going 
> to the next lock in the chain. I use get_/put_task_struct to avoid the 
> task disappearing during the iteration.

but we lose reliable deadlock detection ...

how do you guarantee that some other CPU doesnt send us on some 
goose-chase?

	Ingo

  reply	other threads:[~2006-03-26 23:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 23:42 PI patch against 2.6.16-rt9 Esben Nielsen
2006-03-26 23:47 ` Ingo Molnar [this message]
2006-03-27  0:07   ` Esben Nielsen
2006-03-27  0:11     ` Esben Nielsen
2006-03-27  0:21     ` Ingo Molnar
2006-03-27 15:00       ` Esben Nielsen
2006-03-27 23:05         ` Esben Nielsen
2006-03-28 21:02           ` Ingo Molnar
2006-03-28 20:55         ` Ingo Molnar
2006-03-28 21:17           ` Esben Nielsen
2006-03-28 21:24             ` Ingo Molnar
2006-03-28 22:51               ` Esben Nielsen
2006-03-29  7:14                 ` Ingo Molnar
2006-03-29  7:59                   ` Esben Nielsen
2006-03-29 12:35                     ` Ingo Molnar
2006-03-28 21:36             ` Thomas Gleixner
2006-03-28 22:23               ` Esben Nielsen
2006-03-28 22:42                 ` Thomas Gleixner
2006-03-28 23:34                   ` Esben Nielsen
2006-03-28 23:59                     ` Thomas Gleixner
2006-03-29 12:29                       ` Ingo Molnar

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=20060326234722.GA25331@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 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.