From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Linux RT question - __up_mutex calling pi_setprio
Date: Fri, 25 Feb 2005 22:24:22 -0500 [thread overview]
Message-ID: <1109388262.1452.44.camel@localhost.localdomain> (raw)
Hi Ingo,
I have a couple of questions about __up_mutex in rt.c. I'm still using
RT-V0.7.38-06 and this may have changed. I haven't checked.
1) can old_owner ever not be the same as current. IOW can a process
unlock a lock owned by another process?
2) Is it really necessary to call pi_setprio on the old_owner (I guess
if the previous question is true, then this would be too). If the
process is unlocking a lock, I don't expect it to be also blocked on a
lock so it would not need to iterate the priority list. Wouldn't just
calling mutex_setprio be sufficient?
Thanks,
-- Steve
reply other threads:[~2005-02-26 3:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1109388262.1452.44.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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