From: Steven Rostedt <rostedt@goodmis.org>
To: dwalker@mvista.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
sdietrich@mvista.com, inaky.perez-gonzalez@intel.com
Subject: Re: [PATCH] Abstracted Priority Inheritance for RT
Date: Tue, 31 May 2005 23:35:29 -0400 [thread overview]
Message-ID: <1117596929.4719.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1117594659.3798.18.camel@dhcp153.mvista.com>
Daniel,
I'll start taking a closer look at it tomorrow, but on first working
with it, you might want to change the following config on
PRIORITY_INHERITANCE. At least for me on a "make oldconfig" the default
is usually "No" so I made the following change. It may even be wise to
just force it. I haven't taking a look yet, but would PREEMPT_RT work
without the inheritance?
-- Steve
--- lib/Kconfig.RT.orig 2005-05-31 23:29:41.000000000 -0400
+++ lib/Kconfig.RT 2005-05-31 23:29:56.000000000 -0400
@@ -88,7 +88,7 @@
config PRIORITY_INHERITANCE
bool "Priority Inheritance"
- default n if !PREEMPT_RT
+ default y if PREEMPT_RT
help
This option enables system wide priority inheritance. It will
enable a high priority waiting task to transfer it's priority
next prev parent reply other threads:[~2005-06-01 3:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 2:57 [PATCH] Abstracted Priority Inheritance for RT Daniel Walker
2005-06-01 3:35 ` Steven Rostedt [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 0:10 Perez-Gonzalez, Inaky
2005-06-02 0:25 ` Daniel Walker
2005-06-02 0:52 linux
2005-06-02 1:21 Perez-Gonzalez, Inaky
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
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=1117596929.4719.14.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=dwalker@mvista.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sdietrich@mvista.com \
/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