From: "Martin Däumler" <mdae@cs.tu-chemnitz.de>
To: linux-rt-users@vger.kernel.org
Subject: Priority Inheritance per se?
Date: Fri, 10 Sep 2010 08:49:03 +0200 [thread overview]
Message-ID: <4C89D4DF.9060109@cs.tu-chemnitz.de> (raw)
Hello,
our team develops a Linux-based embedded system to
realise a programmable logic controller. So we investigate
several possibilities to augment Linux real-time capabilities.
Naturally, the PREEMPT_RT-patch is interesting. I searched
the wiki, the mailing list archive, listened to Mr. Assmann's
talk at the Chemnitz Linux Days 2010 and read the corresponding
chapter in "Building Embedded Linux Systems" by Karim Yaghmour.
Nevertheless, I have a question to makes thinks clear once and
for all:
Does the priority inheritance mechanism work without using
special (Pthread-) mutexes in userspace? (As far as I understood,
it does not.)
Imagine a hypothetical case: a high RT-priority (60) task triggers
a synchronous/blocking system call which triggers a device driver
whose ISR is a kernel thread with RT-priority 49. So, a medium
RT-priority (55) task may block the high RT-priority task, doesn't
it?
With kind regards,
Martin Daeumler
next reply other threads:[~2010-09-10 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 6:49 Martin Däumler [this message]
2010-09-14 9:56 ` Priority Inheritance per se? Sergio Ruocco
2010-09-14 11:12 ` Martin Däumler
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=4C89D4DF.9060109@cs.tu-chemnitz.de \
--to=mdae@cs.tu-chemnitz.de \
--cc=linux-rt-users@vger.kernel.org \
/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).