From: Daniel Walker <dwalker@mvista.com>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: Esben Nielsen <simlo@phys.au.dk>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, sdietrich@mvista.com,
rostedt@goodmis.org
Subject: RE: [PATCH] Abstracted Priority Inheritance for RT
Date: Wed, 01 Jun 2005 17:25:53 -0700 [thread overview]
Message-ID: <1117671953.7646.14.camel@dhcp153.mvista.com> (raw)
In-Reply-To: <F989B1573A3A644BAB3920FBECA4D25A03667149@orsmsx407>
On Wed, 2005-06-01 at 17:10 -0700, Perez-Gonzalez, Inaky wrote:
> Maybe he is referring to the case?
>
> A owns M
> B owns N and is waiting for M
> A is trying to wait for N
>
> These deadlocking cases can be tricky during PI.
The bulk of the code is from the current RT mutex, so I'm assuming it
handles this case correctly. However, the rt mutex isn't in userspace ,
so task A or B was a user space task , then the problem would need to be
explored.. How does PI change if A or B are user space tasks?
Daniel
next prev parent reply other threads:[~2005-06-02 0:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 0:10 Perez-Gonzalez, Inaky
2005-06-02 0:25 ` Daniel Walker [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 1:22 Perez-Gonzalez, Inaky
2005-06-02 5:43 ` john cooper
2005-06-03 0:54 ` Bill Huey
2005-06-03 1:10 ` Sven Dietrich
2005-06-02 1:21 Perez-Gonzalez, Inaky
2005-06-02 0:52 linux
2005-06-01 2:57 Daniel Walker
2005-06-01 3:35 ` Steven Rostedt
2005-06-01 7:54 ` Ingo Molnar
2005-06-01 12:57 ` Daniel Walker
2005-06-01 14:07 ` Esben Nielsen
2005-06-01 23:58 ` Daniel Walker
2005-06-02 8:25 ` Esben Nielsen
2005-06-02 15:11 ` Daniel Walker
2005-06-02 15:18 ` Esben Nielsen
2005-06-02 17:31 ` Daniel Walker
2005-06-02 20:27 ` Esben Nielsen
2005-06-02 21:50 ` Daniel Walker
2005-06-03 9:08 ` 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=1117671953.7646.14.camel@dhcp153.mvista.com \
--to=dwalker@mvista.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=sdietrich@mvista.com \
--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
all inboxes | Powered by JetHome®