* Linux RT question - __up_mutex calling pi_setprio
@ 2005-02-26 3:24 Steven Rostedt
0 siblings, 0 replies; only message in thread
From: Steven Rostedt @ 2005-02-26 3:24 UTC (permalink / raw)
To: Ingo Molnar; +Cc: LKML
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-02-26 3:26 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-02-26 3:24 Linux RT question - __up_mutex calling pi_setprio Steven Rostedt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox